A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows ME » General
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

Hide A: drive?



 
 
Thread Tools Display Modes
  #11  
Old August 19th 04, 05:11 AM
Menno Hershberger
external usenet poster
 
Posts: n/a
Default

"Bill Leary" wrote in
:

"Menno Hershberger" wrote in message
...
Are you sure that you do mean the BIOS and not Device Manager?

In BIOS it shows up... wait, I'll go hook it up again.... :-)
OK, actually in BIOS it calls it an IOMEGA ZIP 100. My guess is
IOMEGA probably made it, or has a chip in there or something that
makes it identify that way.


AH, now THIS I've seen before.

Some BIOS will accept the IOMega Zip 100 as a bootable drive and it
overrides the floppy. I've got a machine a work that does this. When
I hook up the IDE Zip-100 the floppy disappears and the Zip appears as
A:. When I take it off, the floppy comes back.

There are a couple of possible ways around this. The best one, if
it's there (and works) is to find an option something like "Boot
additional removable devices" and turn it off. Drawback is this may
disable booting CD-ROMs as well.

If this doesn't work, you can try switching the IDE interface for the
channel you're attaching it to (for example Secondary Slave) and
taking it out of AUTO mode and selecting something else. You can also
try changing the device IDE from ZIP 100 to some other designation.
In the case above, I actually set it to NONE. The drive didn't appear
in BIOS or when booted to DOS but *did* get detected by Windows and
worked correctly (as E under Windows.


YOU ARE MY HERO! :-)
I couldn't stop BIOS from detecting the Iomega drive, but there's an
option to change drive TYPE which was set to AUTO. I changed it to NONE as
you suggested. I booted into Windows and it reads it and the floppy just
fine. I even rebooted to make sure the floppy didn't go away on me. It
didn't.
Thank you so much!
And thanks to Mart for hanging in there with me so long.
Now I'm off to eBay to see if the guy will let me retract my bid on a
Actiontec PC 750 AD75000 PCMCIA Card Reader (PCI)... :-)

--
-- What happens if you get scared half to death twice? --
  #12  
Old August 19th 04, 09:37 AM
Mart
external usenet poster
 
Posts: n/a
Default

Well spotted Bill - I've never worked with a Dell MoBo, but guessed that it
had to be a 'feature' of the BIOS somehow - there was nothing else left g

Good luck Menno, and as you may already know, you learn something new on
these pages every day.

Mart



"Menno Hershberger" wrote in message
...
"Bill Leary" wrote in
:

"Menno Hershberger" wrote in message
...
Are you sure that you do mean the BIOS and not Device Manager?
In BIOS it shows up... wait, I'll go hook it up again.... :-)
OK, actually in BIOS it calls it an IOMEGA ZIP 100. My guess is
IOMEGA probably made it, or has a chip in there or something that
makes it identify that way.


AH, now THIS I've seen before.

Some BIOS will accept the IOMega Zip 100 as a bootable drive and it
overrides the floppy. I've got a machine a work that does this. When
I hook up the IDE Zip-100 the floppy disappears and the Zip appears as
A:. When I take it off, the floppy comes back.

There are a couple of possible ways around this. The best one, if
it's there (and works) is to find an option something like "Boot
additional removable devices" and turn it off. Drawback is this may
disable booting CD-ROMs as well.

If this doesn't work, you can try switching the IDE interface for the
channel you're attaching it to (for example Secondary Slave) and
taking it out of AUTO mode and selecting something else. You can also
try changing the device IDE from ZIP 100 to some other designation.
In the case above, I actually set it to NONE. The drive didn't appear
in BIOS or when booted to DOS but *did* get detected by Windows and
worked correctly (as E under Windows.


YOU ARE MY HERO! :-)
I couldn't stop BIOS from detecting the Iomega drive, but there's an
option to change drive TYPE which was set to AUTO. I changed it to NONE as
you suggested. I booted into Windows and it reads it and the floppy just
fine. I even rebooted to make sure the floppy didn't go away on me. It
didn't.
Thank you so much!
And thanks to Mart for hanging in there with me so long.
Now I'm off to eBay to see if the guy will let me retract my bid on a
Actiontec PC 750 AD75000 PCMCIA Card Reader (PCI)... :-)

--
-- What happens if you get scared half to death twice? --



  #13  
Old August 19th 04, 02:38 PM
Bill Leary
external usenet poster
 
Posts: n/a
Default

"Menno Hershberger" wrote in message
...
If this doesn't work, you can try switching the IDE interface for the
channel you're attaching it to (for example Secondary Slave) and
taking it out of AUTO mode and selecting something else. You can also
try changing the device IDE from ZIP 100 to some other designation.
In the case above, I actually set it to NONE. The drive didn't appear
in BIOS or when booted to DOS but *did* get detected by Windows and
worked correctly (as E under Windows.


YOU ARE MY HERO! :-)


A success for the week. Good to have at least one.

I couldn't stop BIOS from detecting the Iomega drive, but there's an
option to change drive TYPE which was set to AUTO. I changed it to NONE as
you suggested. I booted into Windows and it reads it and the floppy just
fine. I even rebooted to make sure the floppy didn't go away on me. It
didn't.
Thank you so much!


You're welcome.

- Bill


  #14  
Old August 19th 04, 02:46 PM
Bill Leary
external usenet poster
 
Posts: n/a
Default

"Mart" wrote in message
...
Well spotted Bill - I've never worked with a Dell MoBo, but guessed that

it
had to be a 'feature' of the BIOS somehow - there was nothing else left

g

That's how it was sounding. It sounded vaguely familiar, but it was when he
mentioned that the BIOS thought it was an ZIP-100 that the lights went on
for me. In my day job I dealt with BIOS vendors and a couple of years back
a number of them were convinced that Zips were going to be the next floppy
so they were adding features to let them be such. As one might expect, some
problems resulted and I was involved with sorting them out for my company.
The "bump the real floppy" issue was one of them.

Good luck Menno, and as you may already know, you learn something new on
these pages every day.


Quite so. I've had more than a few cases where someone has solved a problem
different from one I'm having, but their solution has given me the clue I
needed to solve mine. Very interesting.

- Bill


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Error - "CD Rom drive is not accessible; the device is not ready." J Eklund J.D. Multimedia 0 July 14th 04 07:21 AM
Error - "CD Rom drive is not accessible; the device is not ready." J Eklund J.D. Multimedia 0 July 14th 04 07:21 AM
deleted explorer.exe Anida Software & Applications 20 June 16th 04 06:21 AM
Zero-byte D: drive should not show, C: missing from Device Manager *Vanguard* General 8 June 12th 04 04:19 AM
Large Hard Drive & BIOS upgrade problems Lago Jardin General 17 June 11th 04 07:27 PM


All times are GMT +1. The time now is 11:55 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.