[Date Prev][Date Next][Subject Prev][Subject Next][
Date Index][
Subject Index]
Re: Table SPEEDOS and Func WZ
- Subject: Re: Table SPEEDOS and Func WZ
- From: "Robert Holmgren" holmgren@xxxxxxxx
- Date: Sat, 15 Feb 2003 11:08:52 -0500
** Reply to message from Patricia M Godfrey on Fri, 14 Feb
2003 15:59:45 -0500
> it seems that the /E4000
> switch only works in Win2K and XP, no?
No. It works in DOS -- any DOS, as long as a memory manager is set up (which
ought to be the case by default in W98), and as long as the memory area which
EMS uses as its swapping space isn't already in use. If you "shell to DOS"
(using DOS/NV) and command MEM /C, you ought to get a report that EMS is set
aside by the OpSys, also showing how much EMS is in use -- and that number
should change when you start using the /e4000 switch.
> Fast ROM emulation, and
> dynamic memory allocation all checked
Most likely the cause is a video problem, or secondarily maybe memory.
Something is getting "stepped on", i.e. an area of memory already in use is
trying to be reallocated to a different purpose, and the OpSys won't let it
happen. I get func WZ crashes occasionally too. Is the crash repeatable --
does it _always_ happen? If there's no other solution, I'd see whether playing
with those two variables (above) makes any difference. Does func WZ work with
other documents (without complaint)? -- because some monitors choke on that
non-standard display mode (what kind of monitor or screen are you using?). I'd
also try launching func WZ when you're already in full screen VGA display mode.
Are other graphical apps, apart from the desktop GUI, also running? Is it
really the Speedo table that's crashing your system, or is it the INF file
(possibly it's sheer size, possibly other difficult-to-display things in it)?
What happens if you CoPy the Speedo table out of XyWWWeb.INF and put it into a
separate file, then WZ? Have you been able to display this table in the past?
Lots and lots of things to investigate...
> There is no file called cmd.exe
> anywhere on a Win9x system.
True. The 9x command processor (reported by and as the "ComSpec") is
COMMAND.COM. The primary NT comspec is CMD.EXE. What command are you trying
to execute here?
Look, a big weakness of 9x is memory management. It's one of the main reasons
I eradicated 9x on all my machines. Truly terrible.
-----------------------------
Robert Holmgren
holmgren@xxxxxxxx
-----------------------------