win98 hangs with "while" at start of windows gui

Status
Not open for further replies.
Mysys: runs dual boot win 98 and Linux FC5 using GRUB as the loader.

Problem:
I have had a system that ran perfectly for "years" until last week In the middle of a download it lockedup - no response from kb or mouse. The download was running fine until I selected an online folder at the download site purporting to contain pdf files.
what i did:
- Full cold reboot. Boot runs through the bootloader to select windows and then hangs.
- try booting to safemode menu
- the menu appears and I can select any option but there is no activity
- it hangs
- tried F8 for step by step.
- bootlog=y
- device himem.sys /testmem : on=y
- device dblbuff.sys /D+=y
- device high ifshlp.sys=y
- win GUI=y
the screen then shows "while" and nothing else. it hangs.
==========
Rebooting into Linux I can mount and look at the windows files. They appear to be OK. there are no recent changes (lastmod date) to the main system (that i can see).
==========
I do have another machine running 98 if I need any files etc,
==========
The fact that I can get to the point where it should start the windows gui implies to me that something passed the firewall / antivirus and changed something. . . ? Question:
Can someone please list the actions / files that windows is accessing at the point of the hang. Any help on finding where the file is that contains the "while" command would be appreciated.

Ever hopeful
Myk
 
I have just had the thought that perhaps it is trying to say
"While initializing device XX Windows Protection Error" ???
But if this is the case how do I find the cure

Myk
 
Sounds and looks to me like you have corrupted 98's system files. Unless you know for sure what files are waisted you could just do a 98 reinstall on top of itself, you will have to reinstall your apps.

If you know what files are busted you could boot to Linux and copy the files back over.


I loved 98 when it was the new OS all you had to do to move your os over to a new HD was do a xcopy /e/s and the sys the new drive ...... boom.... bang.... thank u ........ up and running.
 
I agree with you but if there is a way round it i would prefer to try 1st !

Reinstall means loosing access to the Linux side until the bootloader is reset. I've done it years ago but I'd rather avoid it if poss.

Do you think that if i copied the main directories from the working machine (mc1) to the faulty one (mc2) it would help ?? They are the same standards.

Myk
 
copy them from a working machine to the non working one? As long as they are both the same yes it would work. Anyhow how you have everything to gain and nothing to lose by trying


Let us know what happend

GL
 
solved

yes, all is now ok - as follows:-

Copied all the drivers and many important system files from mc1 to mc2 - no effect.
Decided to reload the registry (from boot to dos prompt).
Found that scanreg (all switches) & regedit had no effect - they started and then just hung.

Used a batch file called cabrest by Bob Sturtevant (many thanks) to extract a backup from the ms sysbckup cab files and replace the current registry files.

Reboot - all ok.
====================
 
Status
Not open for further replies.
Back