| From: | Simon Preston |
| Date: | 7 May 2000 at 20:24:25 |
| Subject: | Re: slight IDEFix Prob |
> nope, all in a Eyetech EZ-Tower. (4.3Gb HD, 54xCD, 24xCD, Zip100) Like I
> say though, it does not happen very often, so it is not a big problem
> (more annoying than anything). I have tried opening the Pixel64 screen
> before the drives are mounted, but it does not good. The error can not
> mount drive is still put out on to a PAL screen : (
Yeah. Thats because there is a line in your Startup-Sequence that reads
something similair to this...
; $VER: Startup-Sequence_HardDrive 40.2 (25.2.93)
; Startup-Sequence for hard drive systems
C:SetPatch QUIET
*C:IDEfix*
C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
C:Addbuffers >NIL: HD0: 300
FailAt 21
As you can see, IDEfix is executed before anything else (besides Setpatch).
This wouldn't give any time for the monitor to kick in. I'm not sure about
this but try putting the C:IDEfix line later in your startup, after the
monitor driver has been loaded.
Like I said, I'm not sure what this would do. It may work it may not. Try
but use caution. </disclaimer>
However, I did get a similair command a while back after I installed my
CD-R and had to use a power connector to power the CD-R which I borrowed
from my CD-ROM. With me so far?
Anyway, my CD ROM had no power and so couldn't be started up, causing the
Can't open atapi.device Unit 3 or something like that.
IIRC this requester opened up on my monitor and for the life of me I can't
remember what made it do that.
Try changing FailAt 21 (in the startup) to something like FailAt 100. This
may help.
Hope this *does *actually help.
Regards
http://www.music-laboratory.co.uk/
This tagline was reclaimed and is not yet stolen.
------------------------------------------------------------------------
You have a voice mail message waiting for you at iHello.com:
http://click.egroups.com/1/3555/3/_/468125/_/957727604/
------------------------------------------------------------------------
Quote carefully and read all ADMIN:README mails