30min lockup on boot-up

[Valheru]

Can anyone help pleeeaasse.... Some time ago I ugpraded my old Digital Venturis 486DX2 machine from Win3.1 to Win 95. In doing so I got a lock up problem. After it has performed all cache, bios, mouse initialisation and testing of floppy and hard drives it displays the message "Intel plug&play BIOS Extensions - Release 1.1u NJS ID:99J-123-208. Copyright (c) 1993 Intel Corporation all rights reserved" at which point my PC hangs for exactly 30mins..yes minutes not seconds, then continues to load all OK as if nothing has happened ?. A friend of a friend did resolve this for me by "REMing" out a line in a .INI file but I cannot remember which one it was. I have stupidly now upgraded the machine to Win98 and hadn't written the fix down and low and behold the machine is now hanging again. Can anybody help me pleease?

[BFlurie]

Sounds like something in either Autoexec.bat, Config.sys, or System.ini. Run Sysedit.exe from the run line, copy & paste the contents of each to a text file, post back here & copy that to yer message so's we can see 'em.

[Valheru]

Thanks very much for replying so soon. Here are the files you requested. I hope this is what you meant about posting them back as I couldn't actually find a way to attach them as if it where in an e-mail.

Autoexec.bat

SET SOUND=C:\PROGRA~1\CREATIVE\CTSND
SET MIDI=SYNTH:1 MAP:E
SET BLASTER=A220 I5 D1 H5 T6
mode con codepage prepare=((850) C:\WINDOWS\COMMAND\ega.cpi)
mode con codepage select=850
keyb uk,,C:\WINDOWS\COMMAND\keyboard.sys

Config.sys

DEVICE=C:\WINDOWS\COMMAND\display.sys con=(ega,,1)
Country=044,850,C:\WINDOWS\COMMAND\country.sys

System.ini

[boot]
oemfonts.fon=vga850.fon
system.drv=system.drv
drivers=mmsystem.dll power.drv ctpnpscn.drv
shell=Explorer.exe
user.exe=user.exe
gdi.exe=gdi.exe
sound.drv=mmsound.drv
dibeng.drv=dibeng.dll
comm.drv=comm.drv
mouse.drv=mouse.drv
keyboard.drv=keyboard.drv
fixedfon.fon=vgafix.fon
fonts.fon=vgasys.fon
386Grabber=vgafull.3gr
display.drv=pnpdrvr.drv
DisplayFallback=0
SCRNSAVE.EXE=C:\WINDOWS\SYSTEM\SPACE.SCR
*DisplayFallback=0

[keyboard]
keyboard.dll=
oemansi.bin=xlat850.bin
subtype=
type=4

[boot.description]
system.drv=Standard PC
keyboard.typ=Standard 101/102-Key or Microsoft Natural Keyboard
mouse.drv=Standard mouse
aspect=100,96,96
display.drv=S3 Trio32 PCI (732)

[386enh]
ebios=*ebios
woafont=app850.fon
mouse=*vmouse,msmouse.vxd
device=*dynapage
device=*vcd
device=*vpd
device=*int13
device=*enable
keyboard=*vkd
display=*vdd,*vflatd

[NonWindowsApp]
TTinitialSizes=4 5 6 7 8 9 10 11 12 13 14 15 16 18 20 22

[power.drv]

[drivers]
wavemapper=*.drv
MSACM.imaadpcm=*.acm
MSACM.msadpcm=*.acm
VIDS.DRAW=UDH.DLL
wave=mmsystem.dll
midi=mmsystem.dll

[iccvid.drv]

[mciseq.drv]

[mci]
cdaudio=mcicda.drv
sequencer=mciseq.drv
waveaudio=mciwave.drv
avivideo=mciavi.drv
videodisc=mcipionr.drv
vcr=mcivisca.drv
MPEGVideo=mciqtz.drv

[vcache]

[drivers32]
MSACM.imaadpcm=imaadp32.acm
MSACM.msadpcm=msadp32.acm
MSACM.msgsm610=msgsm32.acm
MSACM.msg711=msg711.acm
MSACM.trspch=tssoft32.acm
vidc.CVID=iccvid.dll
VIDC.IV31=ir32_32.dll
VIDC.IV32=ir32_32.dll
vidc.MSVC=msvidc32.dll
VIDC.MRLE=msrle32.dll
VIDC.IV50=ir50_32.DLL
msacm.iac2=C:\WINDOWS\SYSTEM\IAC25_32.AX
MSACM.ctadp32=ctadp32.acm
MSACM.ctfs32=ctfs32.acm

[MSNP32]

[Password Lists]

[display]
dac-type=nbt
aperture-base
polygon-support=on
ellipse-support=on
font-caching
scache=on
textrmw=0
fastmmio=on
screen-size=1024
color-format=16
dpi-20
virtualize-vga=

[Valheru]

Hi again. It's taken a little while to perform the tasks, 1/2 hr delay between each reset etc....

In answer to your queries,
1) The guy who helped me out before has left my brother-in-laws company and moved up north so I can't trace him.

2) I don't want my "REMing" comment to mislead, I have it feeling it was actually adding or removing a "*" to a line instead, it was me who translated this into a similar function to "REMing".

3) I know network cards can slow things down but 30mins ???? not that long even for a 486 !

4) Tried the rename of Auto and Config. Didn't work. It caused the system to lock up even earlier, before it had even tested the system RAM. It did however display a new line at the bottom left hand side of " 220:SHADOW ROM's ?? It also displayed "Press <F2> to enter setup" but it wouldn't let me actually do it ???

5) Did the logged boot-up using Bootlog.txt (put a sellotape dispenser on the CTRL Key to weight it down!). This produced a rather large file. I'm not sure you want me to post it all onto the site ?

For starters here are the first and last batch of 20-30 lines with the fails inbetween :-

[00160FE2] Loading Device = C:\WINDOWS\COMMAND\DISPLAY.SYS
[00160FE6] LoadSuccess = C:\WINDOWS\COMMAND\DISPLAY.SYS
[00160FE8] Loading Device = C:\WINDOWS\HIMEM.SYS
[00160FEA] LoadSuccess = C:\WINDOWS\HIMEM.SYS
[00160FEB] Loading Device = C:\WINDOWS\DBLBUFF.SYS
[00160FED] LoadSuccess = C:\WINDOWS\DBLBUFF.SYS
[00160FEE] Loading Device = C:\WINDOWS\IFSHLP.SYS
[00160FEF] LoadSuccess = C:\WINDOWS\IFSHLP.SYS
[00161003] C:\WINDOWS\COMMAND\MODE.COM[00161004] starting
[0016100A] C:\WINDOWS\COMMAND\MODE.COM[0016100B] starting
[00161010] C:\WINDOWS\COMMAND\KEYB.COM(Logo disabled)
[00161012] starting
[00161049] Loading Vxd = VMM
[0016104E] LoadSuccess = VMM
[0016104F] Loading Vxd = C:\WINDOWS\SMARTDRV.EXE
[00161050] LoadSuccess = C:\WINDOWS\SMARTDRV.EXE
[00161051] Loading Vxd = vnetsup.vxd
[00161053] LoadSuccess = vnetsup.vxd
[00161054] Loading Vxd = ndis.vxd
[00161059] LoadSuccess = ndis.vxd

[0016105A] Loading Vxd = ndis2sup.vxd
[0016105C] LoadFailed = ndis2sup.vxd

[00161125] DEVICEINIT = MTRR
[00161126] DEVICEINITFAILED = MTRR

[001615AD] INITCOMPLETE = SDVXD
[001615AE] INITCOMPLETEFAILED = SDVXD

[0016162B] Dynamic load device naapi.vxd
[0016162D] Dynamic load failed naapi.vxd : [0016162F] File not found

s3.drv: VDD call ok
s3.drv: CheckCursorTimer call ok
s3.drv: GSV zero path taken
s3.drv: bMMIO=01
s3.drv: bScanlineFlag=01
s3.drv: bPolygonFlag=00
s3.drv: bPolylineFlag=01
s3.drv: bEllipseFlag=00
s3.drv: bRectangleFlag=00
s3.drv: bBitbltSupportFlag=01
s3.drv: bOutputSupportFlag=01
s3.drv: bTextOutSupportFlag=01
s3.drv: bBlockedMode=00
s3.drv: b8BitDAC=01
s3.drv: bNeedPatTransPatch=00
s3.drv: wBpp=0008
s3.drv: wChipId=00E0
s3.drv: wChipRev=0001
s3.drv: wDeviceId=1088
s3.drv: wCursorType=0001
s3.drv: wDACType=0008
s3.drv: wBusType=0002
s3.drv: SWCursor=0000
s3.drv: wCurrentMode=0103
s3.drv: wScreenWidth=0320
s3.drv: wScreenHeight=0258
s3.drv: wMaxWidth=0320
s3.drv: wMaxHeight=051E
s3.drv: wScreenWidthBytes=0320
s3.drv: dwVideoMemorySize=00100000
Init = Display Resources
InitDone = Display Resources

If you feel you need them all then I can post the rest if you need something to send you sleep at night and don't mind ploughing through them all.

[BFlurie]

I'm not sure how renaming Config and Autoexec would have affected anything before the "Starting W98" message appears since they're not used before then.

You don't happen to have too many files in the root of C drive? A couple dozen may reach the standard 512-space limit, which causes problems for W9X.

If you DO have a network card, remove it & see it that helps.

Your bootlog has the usual, normal (harmless) "failures", except the naapi.vxd one. Here's what I found on another BB:

naapi.vxd is a driver for the Japanese version of windows (for the SB sound card). You will get the error if your Windows is any other language. Don't worry about it - it won't hurt anything.

Anywho, use Sysedit.exe, look at System.ini for any reference to naapi.vxd and put a ; (semicolon) in front of that line to disable it. Reboot, & see what happens.

If still no joy, I'm running outta suggestions. Someone else might know, so don't give up! You might also bring up your BIOS setup screen, then simply "save" it to make sure a corrupted BIOS isn't doing it.

[This message has been edited by BFlurie (edited 07-26-2001).]

[BFlurie]

You did it just right.

First glance, I can't see anything for sure that might be causing such a "lockup". Can you find out how it was "fixed" before? 'Cause your reference to "REMing out" would apply to Config or Autoexec.

Sometimes a network card can hold up initialization for a long time.

First, you can rename C:\Config.sys and C:\Autoexec.bat to Config.old & Autoexec.old. Then reboot. Help? If not, rename them back.

Second, some hardware or hardware-driver is not initializing. Hold down & keep holding the Ctrl key just before "Starting W98" appears during a reboot (in your case you may need to tape it down), to get you to a boot menu. Select "Log Startup", or similiar, & continue. When it finally comes up, there should be a new file, C:\Bootlog.txt. View it w/Notepad, & using the "Find" feature, search for the word "Fail". Post back w/what you find (copy & paste the lines containing "Fail"). In fact, tho it'll be long, it may be better to copy & paste the whole file.

[This message has been edited by BFlurie (edited 07-26-2001).]

[Valheru]

I don't know why it affects the system earlier either. It's done it when I tried to REM one of the lines in the system .ini aswell ?

I have a few files in the root directory (approx 20) but their not large and don't reach anywhere near a 512 limit.

I've tried removing the network card....no change.

Thanks for the info on the naapi.vxd. I'll alter that when it re-boots in 1/2 hr.

Thanks for all your efforts. It's much appreciated to get someone willing to spend some time trying to help out. I'll find the answer one day !

[BFlurie]

Concerning the network card, you may first need to remove ALL references to it in Device manager and Control Panel/ Network, then physically remove it, because that info might still be causing your box to "search" for it even tho you had removed it.

[BFlurie]

Before you try the above, d/l and run Boot Log Analyzer (http://www.vision4.dial.pipex.com/) . Follow instructions. This logs the times that major boot-up processes take during bootup. It may be hard to interpret the results, but we can figure it out.

[Valheru]

Thanks for this. I've downloaded the bootlog file and I'll try using it tomorrow if I can sneak away from the wife & children. I'm supposed to be cooking a meal with some friends on the BBQ tomorrow !