Memmaker causes my Computer to Crash
Christopher Welsh
the machine so as to restore my previous config &
Autoexec.bat. The results are unsatisfactory. The machine
now hangs.
My question is, does memmaker alter any other
files. I've noticed my autoexec.bat & config.sys files
have been changed back to their original format, but
some of the TSRs will not load into memory anymore
because supposedly "not enought memory". And it hangs
when I load PC-NFS40a. Why did the TSRs work ok before
and why does NFS hang?
This has happened on both a 486DX and 386SX, 4meg & 8meg
of memory respectively. They both use PC-NFS40a windows
etc.
And yes I've appeneded *NET to the memmaker.inf file as
the readme suggests.
regards
Christopher
--
Deakin University Christopher Welsh
School of Computing and Maths cr...@Deakin.Edu.Au
--------------------------------- Disclaimer: I give no guarantees :)
Everybody has enormous potential........ if only you could see what I can see.
Joe Morris
> [had problems with memmaker; restored config.sys and autoexec.bat but...]
>My question is, does memmaker alter any other
>files. I've noticed my autoexec.bat & config.sys files
>have been changed back to their original format, but
>some of the TSRs will not load into memory anymore
>because supposedly "not enought memory". And it hangs
>when I load PC-NFS40a. Why did the TSRs work ok before
>and why does NFS hang?
You may have a corrupted disk. There were several places where the 6.0
memmaker would step where it shouldn't, both in the files it had reason
to change and elsewhere in places it shouldn't be even looking at. The
symptoms stink of a blown segment register.
My CONFIG.SYS is liberally dosed with remark lines which read "BAIT FOR
MEMMAKER LINE EATER."
On my testbed, running MEMMAKER after setting the PATH to *not* include
the C:\ root directory resulted in a trashed HD FAT. It's also known
to get upset if you point the PATH to the DOS directory using lower-case
letters.
I would suggest (for peace of mind if nothing else) restoring the files
which are used to get you to the point where things no longer work like
they used to. Try reloading DOS directly from the distribution disks
as a starting point, then rebuild the TSRs a few at a time to see what
broke.
Also, it's not impossible that a screwup in memory could have messed up
the CMOS configuration on either the system board or on an adapter card.
Rerun all your hardware setup programs to ensure that their configuration
hasn't changed. (You *do* have notes somewhere about the configurations,
right?) I had a case (not involving DOS 6) where a Windows crash on
a Compaq system appeared to be a hardware problem: after the crash the
video system failed, sounding the error beeps during POST. We swapped
out the system board but the problem happened again; I finally discovered
that the Windows crash had messed up the Cabletron Ethernet configuration
to the point that it was stepping on the video memory...
Joe Morris / MITRE
Matthew I Ralph
Memmaker seems to fiddle with some parts of system.ini in windows. It also uses a file called monoumb.386 which has given me some problems in the past. It seems that it could be a clash with the network card.