Gunilla
Sun Dec 14 12:12:37 CST 2003
Hi again and thanks.
I have been messing around in DOS and found out that I could run scandisk if
I typed C:\Windows\Command and ran it from there. The other option to run it
from C:\Windows did not work as the fault in .EXE file showed up. Have not
tried to rename to .COM yet because I wanted to show you something that
might be of importance. BTW..scandisk corrected TVDebug.log as it was wrong
size and some cluster-fault that it saved as a file0001.chk in the root but
I don't know how to read it as Type didn't open it.
Today I tried to do another bootscan with Trend Micros Rescue Set and it all
went out well until the last diskette had been running for a while. It
couldn't continue as it was a error (exception...general protection fault).
I could not save it to a file as I dont know how to do it in DOS but I wrote
it down.
DOS/4GW error (2001): exception 0DH (general protection fault) at
1D0:002F43FF
TSF32:prev_tsf32 5380
ss 1D8 DS 1D8 1D8 FS
0 GS 20
EAX FFFFFFFF EBX 344D38 ECX 0 EDX 7FFF
ESI 7FFF EDI C35D EBP D7E8126 ESP 344C38
CS:IP 100:002F43FF ID 00 COD 0 FLG 10212
CS= 1D0, USE32, page granular, limilt FFFFFFFF, base
0, acc CF9B
SS= 1D8, USE32, page granular, limit FFFFFFFF, base
0, acc CF93
DS= 1D8, USE32, page granular, limit FFFFFFFF, base
0, acc CF93
ES= 1D8, USE32, page granular, limit FFFFFFFF, base
0, acc CF93
FS= 0, USE16, byte granular, limit 0, base
14, acc 0
GS= 20, USE16, byte granular, limit FFFF, base
31140, acc 93
CR0: PG:0 ET:1 TS:0 EM:0 MP:0 PE:1 CR2:0 CR3:0
crash address (unrecolated) = 1:000833FF
Okay, I send this now and hope you or someone else know how to interpret
this. BTW..those errors I have refeer to Explorer.exe exceptions in
c06d007eH in module SENS.DLL on address 015f:6010857f. and also EXPLORER
caused an invalid page fault in module KERNEL32.DLL on address 015f:bff7b9e6
and MSIMN caused an invalid page fault in
module MSHTMLED.DLL on address 015f:70f72931. This happens every time I
connect to internet, even if it is 10 times each day!! I though it might be
to help if I provide this info.
Ohhh, one more thing...have just attached more RAM (128 MB now). Did run two
memory tests, Windows Test utility and MemTest and yes, even DocMem and I
seems to be clear, or fine.
BTW..have already scanned for Win95.Matrix virus and tried all things from
reinstallation of IE and OE, running SFC, removed my Network applications in
both the Control Panel and in the registry to rebuild it again and nothing
worked.
Sorry for the huge post! ;-))
"cquirke (MVP Win9x)" <name.goes.here@nospam.iafrica.com> wrote in message
news:oduotvcnau3m2u7g1kb1ndsu68vbm6jj79@4ax.com...
> On Sun, 14 Dec 2003 01:02:49 +0100, "Gunilla" <Gun@yahoo.com> wrote:
>
> >Have to ask...when I try to run an .EXE-file in MS-DOS it says that there
is
> >a fault in the .EXE-file! I can't run anything from there but if I try a
> >DOS- window in Windows I can do it. For example..I tried to run scandisk
in
> >safe mode, after correcting dates of some .DBX-folders it started to run
and
> >went up to 10% and then started over and over again, so I rebooted and
tried
> >to run in MS-DOS Prompt Only and then I got the fault in .EXE-file.
>
> Any particular .exe file, or all?
> Do genuine .com files work OK?
> Does renaming to .com help?
> Is Windows running in DOS Compatibility Mode?
>
> .COM files are 64k images that are just splatted into RAM and run -
> whereas .EXE files contain "fixup" values that DOS uses to allocate
> separate code, data and stack segments to program before entering it.
>
> If something goes wring with DOS's ability to do that (say, virus
> patched into the process, or virus-damaged .EXE having invalid values,
> or file system / geometry errors causung garbage fixup data) then etc.
>
> DOS 7 looks for header info to distinguish .EXE from .COM when running
> programs, disregarding the file name extension; that's why you can
> rename an .EXE to .COM or vice versa, and it works, whereas in older
> MS-DOS you'd expect ".COM" to crash and ".EXE" to give an error about
> invalid pointers, program too big (bad fixup values) or crash.
>
> If renaming a .COM to .EXE stops the .COM from working, and renaming
> an .EXE to .COM causes it to stop failing and work, then there's
> something specifically wrong with .EXE handling per se. In Windows,
> that would suggest file association issues (malware patch in) but that
> doesn't apply in DOS mode - in fact, I can't think of what would,
> other than a handful of bytes within Command.com, or perhaps s virus
> that has patched into the "what to do with this file" logic.
>
> If OTOH .EXE files always crash whether the extension is .EXE or .COM,
> and .COM always work even if renamed .EXE, then it's something to do
> with the memory management of .EXE code. The distiction is
> interesting, but not really helpful; either way you'd want to do a
> formal virus check, and version-check and FC-check IO.SYS,
> Command.com, and perhaps the memory and file system managers
> HiMem.sys, Emm386.exe and IFSHlp.sys
>
> You can also try renaming away Config.sys and Autoexec.bat, and
> checking RAM for errors (tho I'd expect Windows to have become a pain
> in the butt if RAM was bad)
>
> >I have checked the .EXE in shell/open/command and it is ="%1" %* and that
I
> >presume is right?
>
> It's right, but irrelevant in pure DOS mode (one of the advantages of
> DOS mode when it comes to manual malware cleanup)
>
> >I did something in Folder Options > File Types and that was to check the
> >Enable Quick View and Always Show Extension for the MS-DOS
> >commando-file. I hope I didn't do something wrong when doing that?
>
> Sounds OK
>
>
>
> >-------------------- ----- ---- --- -- - - - -
> Trsut me, I won't make a mistake!
> >-------------------- ----- ---- --- -- - - - -
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (
http://www.grisoft.com).
Version: 6.0.551 / Virus Database: 343 - Release Date: 2003-12-11