[Prev][Next][Index][Thread]
Re: Having problems getting 1.99q to run...
>>>>> "Clay" == Clay Helberg <helberg@maddog.fammed.wisc.edu> writes:
In article <4drkfj$25ig@news.doit.wisc.edu> helberg@maddog.fammed.wisc.edu (Clay Helberg) writes:
StarMan (StarMan@Galaxy.com) wrote: I can't seem to run 1.99q,
StarMan> even from dos. The system just stops. Tried using the
StarMan> switch to disable my drive d, since it's compressed with
StarMan> Drivespace 3, and got a message asking for disk b, then
StarMan> it stops. No startup screen, have to warm boot. Any
StarMan> suggestions? (Tried the VESA drive on the ARDI site, but
StarMan> I have an ATI Pro Turbo, so VESA 2 is not the problem).
Clay> You might try letting the system sit for a couple of
Clay> minutes--my machine sits "dead" for about 2 minutes (!),
Clay> then it starts Executor and everything seems to work fine.
Both Clay and StarMan should try
executor -macdrives "" -dosdrives ""
and see if that prevents Executor from spending large amount of times
starting up. Executor jumps through a lot of hoops trying to figure
out what disk drives are on your system (including network drives and
CDs) and it is possible that it is hitting a drive or multiple drives
that may not even be there that cause Executor to wait until some
built-in timer expires.
The above combination of switches tells Executor that you have no Mac
drives or DOS drives and to not bother looking (beyond the DOS drive
that you ran Executor from). If you know that you want to access
drive G as a Mac drive and drives A, C, D and E as DOS drives you can
say:
executor -macdrives g -dosdrives ac-e
and then all the other potential drives will be ignored. In general
users *shouldn't* have to do this, but PCs just have too many
configurations for Executor/DOS to do the right thing. Linux users
have less trouble.
--Cliff
ctm@ardi.com
References: