Mail Archives: djgpp/1997/12/30/10:47:32
Eli Zaretskii wrote:
>
> > I get the same thing happening with my cdrom and it's not in my path.
> > Why does that happen?
>
> Do you also use Windows 95, or was it in plain DOS?
I accidentally realized the problem exists. Once I was compiling some
programs and with each linking I had exactly the same problem:
controller LED was on and I had to wait for something about 10 seconds
(!!!). HDD was not heard and eventually after a few seconds normal
linking procces started. Virus? hdd damge ? ????
After some tests I realized that it's because of CD-ROM. There was no CD
in. Usually such things happens with the first CD access, afterwards
CD-ROM is cached by smartdrive and you cannot realize anything happens.
That is why I had never seen such thing before.
I think it does not depend on OS (I never use W95), it's always plain
DOS 6.22
> Please read the questions in my other message and see if any of them
> rings a bell. `ld' has no business randomly accessing your drives.
But it is searching some linux's paths:
/usr/lib
/usr/local/lib
......
So maybe it makes DOS to check all drives???
> The interesting question is why does it access the zip drive but not
> the floppies?
Floppy is not connected to IDE interface.
Maybe recompiling ld without those linux's paths would help (?).
> Could it be that the zip disk device driver is the one that somehow
> decides to spin the disk when something happens on your system?
Maybe everything that is connected to IDE (my CD-ROM is on 2nd channel
and hdd on first ??) is searched by the ld. Try to cache your zip-disk
(put it in first). Has anyone tried to recompile ld without those paths:
/usr/lib /usr/local/lib ...etc. ??
Mirek
e-mail: mpry AT fuw DOT edu DOT pl
- Raw text -