First I have to say, that I am from Austria (Europe) and so my English maybe isnt perfect.
All program output is translated from German.
Because I had an increase of system crashes in the last few weeks, I decided to first make a scan and safe w/ scanreg in dos-mode and after this use scanreg /fix to fix the registry.
When I checked the registry w/ scanreg, it found no errors. So I satrted scanreg /fix. The check of the registry also worked w/o problem, but when the program tried to restore the registry, it crashed alread at the first file (system.dat). the first point (searching for valid registry keys) worked, but at the second point (checking structure of the registry) it always crashed, when it is at 0%. One of these things happened:
1. the pc just did a reboot
2. strange chars and colored rectangles appeared on the screen (see pic, the dark blue chars should be black) and the system didnt react anymore, only the reset button helped.
3. The same kind of chars appeared, but only very short, than the system rebooted.
4. strange colored chars appeared (see video), and after this the system rebooted
5. the picture just froze at 0%. again only the reset button helped.
The registry wasnt damaged by this, windows is running as good (or as bad) as before.
I only want to know, if this could be a sign for a damaged registry.
Thanks in advance.
Here is the pic of the strange chars (2.,3.; dark blue chars should be black):
I also have a few other videos, where you maybe dont see the colored chars of 4., or you dont see the reboot, but you can see other things better. So if someone has a problem w/ the quality of the video, just post where you have this problem and I will upload this video to my webspace an post a link. The other videos are between 2.25MB and 2.65MB big (yes, I uploaded the biggest one, but it is also the longest one w/ 20 sec.).
@everyone, who says I should upgrade to WinXP: I already have WinXP in dual boot. I cannot get rid of Win98 completely, because I need to use some programs, which run in Win98, but not in WinXP.
I also have tried a few things, that some people in other forums suggested:
I renamed all c:\windows\sysbckup\rb*.cab files in rb*.old. The only difference was, that I got a new version of the crash, but I think that this new version occured the first time when I disabled autoexec.bat and config.sys.
First the screen output looked normal, but than it became this:
<A HREF="http://members.chello.at/edith.matuskovics/Scanreg1_unkomprimiert.jpg" target="_new">uncompressed version, original size (792kB)</A>
After this again only the reset button helped.
Also scandisk in DOS + Windows (including surface tests) didnt help. It only found one error. This error was, that the free memory of the partittion is wrong. In Win9x you get this error nearly every time you run scandisk. When I started scanreg /fix after this the same happened as after I renamed the .cab files (I renamed them back in .cab before I ran scandisk).
I also tried to start DOS w/o autoexec.bat and config.sys. However it didnt work w/o confg.sys, because scanreg needs himem.sys. So I only renamed autoexec.bat and in config.sys I wrote a rem at the beginning of each line except the himem.sys line.
The only difference this time was, that it didnt alwqays crash at 0%. On the 3 tries I made, it crashed one time at 3%, one time at 1% and one time at 0%.
Something else, I forgot to mention: When I go to DOS from windows, the floppy-LED is alway until I return to windows or reboot. But the floppy drive only makes a short sound when I exit windows, after this you dont hear it anymore. So it semms, like the LED is on all the time even when the drive isnt active.
When I strat dos by pressing f8 at boot and selecting command prompt only, the floppy-LED works normal.
When I had renamed my .cab files in .old I also ran scanreg /backup and scanreg /restore, bit both worked normal.
I also made a few virus checks:
Before you read my logfiles, you should know, that on my system Win98 is on C: and WinXP is on D: (dual boot).
about one week ago I found a few viruses w/ avg 6.0 free edition. <A HREF="http://members.chello.at/edith.matuskovics/avg.log.txt" target="_new">logfile</A>.
A few days ago I made a few scans again. I always tested all 3 partitions (also in the test I made one week ago).
First I ran the DOS-VErsion of Norton Anti Virus 2004 in DOS-mode, but I used a very old virus database form 11/2003 (because this was when my trial licence expired). NAV didnt find any viruses.
After this I made a scan w/the freeware program AntiVir in WinXP. The program only found viruses in backup files and in a uninstall program, but i think the virus in the uninstall program was a wrong alert, because the program is from a reliable vendor and also I had a wrong alert w/ this program once in the past (at this time the reason for the wrong alert was a defective ram). <A HREF="http://members.chello.at/edith.matuskovics/AVWIN.LOG.txt" target="_new">logfile</A>
After this I made a scan w/ avg in Win98 (the setup program for avg doesnt work in XP). This time the program didnt find anything.
<A HREF="http://www.nethands.de/pys/show.php4?user=MrBurns" target="_new">My System</A><P ID="edit"><FONT SIZE=-1><EM>Edited by MrBurns on 07/23/04 02:54 AM.</EM></FONT></P>
If I was in your situation I would just backup my important files and reinstall the Operating systems, the video corruption could possibly either be a failing video card or corrupted video drivers, a reinstall should free you of the virus's you may have, and clear up for a reinstallation of the video card, and if the corruption returns its probably the video card failing. This is just a suggestion.
My system still works, so i will not reinstall it, because i would have to reionstall all the progarms too, which would be too much work.
About the corrupted video driver: scanreg /fix only runs in real mode DOS. the only video driver there is the DOS vga driver, which must be integrated in io.sys or command.com (because this are the only files you really need for real mode dos). do you think, that this driver is corrupted? I could restore the original io.sys and command.com, it shouldnt be a problem.
My system still works, so i will not reinstall it, because i would have to reionstall all the progarms too, which would be too much work.
Oh you have programs on there, silly me, to suggest such a thing as reinstallation of an OP/SYS that actually has programs on it, like everyone elses OP/SYS in the entire world does. That suggestion was to alleviate all the other possibilities that could be affecting your system, and was because Win98SE seems to clutter itself up with garbage and slows to a performance crawl and usually a fresh install will pep it up and have it running like new, but so much for that suggestion.
Quote :
About the corrupted video driver: scanreg /fix only runs in real mode DOS. the only video driver there is the DOS vga driver, which must be integrated in io.sys or command.com (because this are the only files you really need for real mode dos). do you think, that this driver is corrupted? I could restore the original io.sys and command.com, it shouldnt be a problem.
I think I said possibility of a corrupted video driver I'll have to look back and see but, just uninstall and reinstall the video driver to resolve that issue, it also could be some other corrupted program or just poorly written drivers of another program. Could be premature hardware failure, and if you only have a DOS video driver how are you running WinXP on another partition, maybe you need to install the video drivers in the first place Mr. Burns.
@4ryan6: As I said, DOS doesnt have a real video driver. it is included in one of the two system files (io.sys or command.com, but from what i know about dos it should be io.sys). I will restore the original io.sys and command.com.
9 Meg seems kind of bloated but that's just my opinion.
Don't know why the /fix option doesn't work for your but you could try SCARNREG /BACKUP followed by SCANREG /RESTORE and restore a one the backup copies of the registry. Remember the most recent would now be the one you just backed up. The other three copies would for most recent succesful Windows starts.
Regarding DOS video drivers, DOS doesn't have any. DOS has driver for text based devices, CON: for keyboard/display input/output device. For graphics each DOS application controlled the display directly, ie no graphics driver.
<b>56K, slow and steady does not win the race on internet!</b>
About the con-driver: it isnt needed for textbased i/o, it is only needed for some special features (like changing the country settings). you can boot dos only w/ io.sys and command.com. the textbased i/o is already inntegrated in one of these files.
I also restored scanreg.exe, command.com and io.sys (scanreg.exe and command.com from the win98-cd and io.sys form the win98 boot floppy, because i couldnt find io.sys on the win98-cd, not evenin the.cab-files).
I also already did the scanreg /backup followed by scanreg /restore, to test these functions. i already poted this somewhere in this thread.
I also tried scanreg /opt. It didnt change the behavior of scanreg /fix, but it reduced the size of the SYSTEM.DAT from 9.16MB to 9.08MB.
I also tried RegClean from microsoft and the program RegSupreme Pro, but this also didnt help.
Einzige möglichkeit ist FORMATIEREN um sicher zu sein wie der 4ryan6 empfohlen hat. Wie ich verstehe haben Sie alles probiert in DOS und auch in Windows. Wahrscheinlich ist die Registrierung beschädigt. Das werde mich ärgern.
I now ran memtest86. First I hd my FSB oced, but after about 10 min. it reportet an error in the first pass at test 4.
So I clocked my FSB back to 166MHz, whihc is the default for my CPU (my RAM is PC3200, so it can do 200MHz). I also raised the timings to optimal.
After this the default test ran nearly 4 hours (over 8 times), but it idint find an error.
After this I ran scanreg /fix again, but it still crashed.
Very strange, in the old times my RAM made 12 hours memtest86 and 12hours GoldMemory w/o problems and I ran my RAM always only at 179MHz, only the timings were a little bit lower (2-2-2-7, optimnal=3-3-3-8, turbo=3-2-2-7).
I also tried but the same test w/ 2.5-2-3-7, but there was also the same error.
w/ optimal timings the test ran for 6 hours w/o a problem.
So I decided to make a test w/ the fastest setting (ccording to benchmark) that was left, which as 13.5x175@2-2-2-6. I made the full test for 10 hours, which is more than one complete pass and it didnt find an error. I will make a few other tests w/ GoldMemory and other programs to find out, if I can really use this settings.
In the mean time I also had the quick test of GoldMemory running for 1 1/1 hours, which is 1 1/2 passes. GM also didnt find an error. I will make the complete test of GoldMemory and also tests w/ other programs to find out, if my system is really 100% stable at this settings.
I also tried the following vbs-scrip to check the .cab-files for errors:
Code :
Set fs=WScript.CreateObject("Scripting.FileSystemObject" )
Set WshShell = Wscript.CreateObject("Wscript.Shell" )
Set WshSysEnv = WshShell.Environment("PROCESS" )
WinFolder = WshSysEnv("windir" )
BackupFolder = WinFolder + "\SYSBCkUP"
CheckFiles BackupFolder
Sub CheckFiles(folderspec)
Set f = fs.GetFolder(folderspec)
Set fc = f.Files
For Each f1 in fc
if (UCASE(fs.GetExtensionName(f1.name))=UCASE("CAB" )) and (UCASE(left(f1.name,2))="RB" ) then
Set datei = fs.OpenTextFile(f1.path)
lies = datei.Read(48)
lies = datei.Read(1)
datei.close
if Asc(lies)=0 then
s = f1.name + " ist defekt." + vbCrLf + "Soll diese Datei gelöscht werden?"
s = "Solange die Datei " + f1.name + " existiert, funktioniert SCANREG /RESTORE nicht." + vbCrLf
s = s + "Benennen Sie die Datei um, wenn Sie sie behalten wollen, oder löschen Sie sie!"
MsgBox s
end if
end if
end if
next
end sub
The program found errors in all of my 21 .cab files (rb000.cab-rb019.cab, rbbad.cab) except rb001.cab.
After this I renamed all .cab files in .old, so that a new rb000.cab was created at reboot. after the reboot, there was a new rb000.cab and a new rbbad.cab. the scrip only found errors in rbbad.cab. after this I ran scanreg /fix again, but it crashed again.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.