[Sending to HJ Tech Support and the JFW mailing list]
I have a 486 running Windows 95 (original release) which was upgraded to
that from Windows 3.1 some time ago (before I started working here). In
Windows 3.1, it used AZMEMORY.DRV, per advice of HJ tech support; however,
this driver remained installed via SYSTEM.INI when the machine was
upgraded to Win95. The machine complains of having legacy driver(s)
installed which hamper performance, and it is slow (well, it's a 486, but
still...), so I thought I'd uninstall it. Accordingly, I clipped
AZMEMORY.DRV out of the "driver=" line of SYSTEM.INI and rebooted.
The resulting mess boggles my mind! My sound card won't work, JAWS can't
run (it either causees a general protection fault in module MMSYSTEM.DLL
at address 0A:32, or says out my Accent-compatible Artic Transport synth,
"JFW Hidden ... can't install system wide hooks ... unknown function
SayFocusedWindow."), an emergency copy of the WinVision demo can run only
sometimes, and I occasionally get a Windows error 0D (or 0E--my memory may
be off here). The machine even crashed once with one of these last 0D/0E
errors in safe mode! Reinstalling AZMEMORY.DRV in the "drivers=" line did
not change a thing. Oh yes... it is also possible that the video is a
mess now: I'm told it moves at a self-changing velocity horizontally
across the screen and is thus unreadable. (This last problem is probably
due to the AZMEMORY.DRV thing, but the cable to the only monitor near this
machine looks a bit frayed, so there is a possibility that this is an
unrelated problem; however, the screen is perfectly stable in DOS and in
Windows safe mode.)
Does anyone have any idea what might have happened to me, or how to
restore sanity in here? I really did think I was pulling out a driver,
not the pin to a hand grenade! :-)
One other note: After the bomb went off, I did find and comment out a
line in SYSTEMINI that says, "AzMemory=azmemory.drv" in the [drivers]
section. I'm sure I should have done that at the same time I took
AZMEMORY.DRV out of the "drivers=" line, but I didn't see it then.
Still, I wouldn't expect that to cause THIS mess. In any case,
commenting that out has not helped; and as I said already, neither does
putting everything back the way I found it. Win98's ScanReg says my
registry is not damaged. No ScanDisk errors. No one has used this
machine but me since I unwittingly created this mess. Ok, more than one
note. :-)
Any help most welcome.
--
Doug Lee, Computer Instructor
BLIND, Inc. (Blindness: Learning In New Dimensions)
-
Visit the jfw ml web page: http://jfw.cjb.net
