Iomega 80GB USB

[E_Net_Rider]

Two days of trying to deal with the problem and Iomega and I can tell you I
O them nothing.

They are blaming MS and the OS and that is why I dropped into the site.
Drive installs with USB drivers, then plugging in, followed with backup
software. Note, the box says Ghost is in the box, but it is not. They say
they've discontinued it, but still put the sticker on the box. They offer a
free alternative, but only compatible with 2K & XP.
But what happens is that all looks OK initially. Drive hooks itself to the
USB and assigns itself the next open drive letter. All seems to be good,
until I reboot. Then it grabs the D partition and shifts all partitions up
and also the next available letter. That right, the single one partition of
the USB drive claims to drive letters. From either the D or the K you can
see the same contents of the drive.
I changed it to removable in the device manager and assigned it letter X.
So now it will claim D and X after a reboot. Same thing in safe mode.
What am I missing that I can't seem to figure this out?
And are there any good search engines that don't bring you every ad or sale
in the world when searching the net for a solution?
Thanks in advance. BTW, I'm running SE. And I don't know if this is related.
Running thorough scandisk on that drive after running format. It has been
running for an hour and isn't half done. The standard seemed to run OK.

HELP!!!!
thanks Norman

[Jeff Richards]

If drive letter D is getting assigned then that sounds like you have DOS
drivers for the IOMEGA drive. Since DOS does not usually support USB, then
that in turn implies something in BIOS setup is enabling DOS to see a USB
drive. Look in BIOS setup and make sure any support for USB drives or
external drives is disabled.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"E_Net_Rider" > wrote in message
...
> Two days of trying to deal with the problem and Iomega and I can tell you
> I
> O them nothing.
>
> They are blaming MS and the OS and that is why I dropped into the site.
> Drive installs with USB drivers, then plugging in, followed with backup
> software. Note, the box says Ghost is in the box, but it is not. They say
> they've discontinued it, but still put the sticker on the box. They offer
> a
> free alternative, but only compatible with 2K & XP.
> But what happens is that all looks OK initially. Drive hooks itself to the
> USB and assigns itself the next open drive letter. All seems to be good,
> until I reboot. Then it grabs the D partition and shifts all partitions up
> and also the next available letter. That right, the single one partition
> of
> the USB drive claims to drive letters. From either the D or the K you can
> see the same contents of the drive.
> I changed it to removable in the device manager and assigned it letter X.
> So now it will claim D and X after a reboot. Same thing in safe mode.
> What am I missing that I can't seem to figure this out?
> And are there any good search engines that don't bring you every ad or
> sale
> in the world when searching the net for a solution?
> Thanks in advance. BTW, I'm running SE. And I don't know if this is
> related.
> Running thorough scandisk on that drive after running format. It has been
> running for an hour and isn't half done. The standard seemed to run OK.
>
> HELP!!!!
> thanks Norman
>
>

[E_Net_Rider]

Thanks for any intervention to break me from this harrowing experience of
trying to chase this down.
DAY3
Since we will look in that direction, I did notice on the screen where it
shows some of the devices during the boot that the HDD was listed by model
as a mass storage device, I think.
As to support specifically for USB drives or external drives, I haven't seen
anything that relates to that, in the BIOS. This is a Nforce 2 ultra400 +
MCPS MOBO. It does have some strange setting in the BIOS I haven't seen
before.
The only drivers I know are being loaded for the interface are for Prolific
2507 chip. A .sys &.pdr.
Comparitive note, but it may mean nothing.
I have a compact flash reader. it also installs itself under the hdd
controller and as a disk drive. I'm able to assign a letter with it also.
Both hooked up through the same hub, the reader gives me no trouble. So on
the surface, it would make me think Iomega has lousy drivers or the
interface they used is grunge.

Norman

"Jeff Richards" > wrote in message
...
> If drive letter D is getting assigned then that sounds like you have DOS
> drivers for the IOMEGA drive. Since DOS does not usually support USB,
then
> that in turn implies something in BIOS setup is enabling DOS to see a USB
> drive. Look in BIOS setup and make sure any support for USB drives or
> external drives is disabled.
> --
> Jeff Richards
> MS MVP (Windows - Shell/User)
> "E_Net_Rider" > wrote in message
> ...
> > Two days of trying to deal with the problem and Iomega and I can tell
you
> > I
> > O them nothing.
> >
> > They are blaming MS and the OS and that is why I dropped into the site.
> > Drive installs with USB drivers, then plugging in, followed with backup
> > software. Note, the box says Ghost is in the box, but it is not. They
say
> > they've discontinued it, but still put the sticker on the box. They
offer
> > a
> > free alternative, but only compatible with 2K & XP.
> > But what happens is that all looks OK initially. Drive hooks itself to
the
> > USB and assigns itself the next open drive letter. All seems to be good,
> > until I reboot. Then it grabs the D partition and shifts all partitions
up
> > and also the next available letter. That right, the single one
partition
> > of
> > the USB drive claims to drive letters. From either the D or the K you
can
> > see the same contents of the drive.
> > I changed it to removable in the device manager and assigned it letter
X.
> > So now it will claim D and X after a reboot. Same thing in safe mode.
> > What am I missing that I can't seem to figure this out?
> > And are there any good search engines that don't bring you every ad or
> > sale
> > in the world when searching the net for a solution?
> > Thanks in advance. BTW, I'm running SE. And I don't know if this is
> > related.
> > Running thorough scandisk on that drive after running format. It has
been
> > running for an hour and isn't half done. The standard seemed to run OK.
> >
> > HELP!!!!
> > thanks Norman
> >
> >
>
>

[Jeff Richards]

If you are seeing it listed in the BIOS hardware list then DOS will see it
and default drivers will be installed, and that is where the drive letter D
is coming from for sure. There should be a way to disable it in BIOS setup.

If you can't find an item in BIOS setup that could be enabling DOS access to
the drive, do Start / Run / MSConfig and look in CONFIG.SYS and AUTOEXEC.BAT
for entries that could be enabling it, and de-select them.

If you can't change the D drive letter to something else then the problem is
not with the Windows drivers for the device (although that doesn't mean that
the IOMEGA Windows drivers aren't lousy!)
--
Jeff Richards
MS MVP (Windows - Shell/User)
"E_Net_Rider" > wrote in message
...
> Thanks for any intervention to break me from this harrowing experience of
> trying to chase this down.
> DAY3
> Since we will look in that direction, I did notice on the screen where it
> shows some of the devices during the boot that the HDD was listed by model
> as a mass storage device, I think.
> As to support specifically for USB drives or external drives, I haven't
> seen
> anything that relates to that, in the BIOS. This is a Nforce 2 ultra400 +
> MCPS MOBO. It does have some strange setting in the BIOS I haven't seen
> before.
> The only drivers I know are being loaded for the interface are for
> Prolific
> 2507 chip. A .sys &.pdr.
> Comparitive note, but it may mean nothing.
> I have a compact flash reader. it also installs itself under the hdd
> controller and as a disk drive. I'm able to assign a letter with it also.
> Both hooked up through the same hub, the reader gives me no trouble. So on
> the surface, it would make me think Iomega has lousy drivers or the
> interface they used is grunge.

[Bill Blanton]

Also check config.sys and autoexec.bat for iomega drivers. Imomega runs
a guest.exe in autoexec.bat to give DOS support to its zip drives.


"E_Net_Rider" > wrote in message ...
> Thanks for any intervention to break me from this harrowing experience of
> trying to chase this down.
> DAY3
> Since we will look in that direction, I did notice on the screen where it
> shows some of the devices during the boot that the HDD was listed by model
> as a mass storage device, I think.
> As to support specifically for USB drives or external drives, I haven't seen
> anything that relates to that, in the BIOS. This is a Nforce 2 ultra400 +
> MCPS MOBO. It does have some strange setting in the BIOS I haven't seen
> before.
> The only drivers I know are being loaded for the interface are for Prolific
> 2507 chip. A .sys &.pdr.
> Comparitive note, but it may mean nothing.
> I have a compact flash reader. it also installs itself under the hdd
> controller and as a disk drive. I'm able to assign a letter with it also.
> Both hooked up through the same hub, the reader gives me no trouble. So on
> the surface, it would make me think Iomega has lousy drivers or the
> interface they used is grunge.
>
> Norman
>
> "Jeff Richards" > wrote in message
> ...
>> If drive letter D is getting assigned then that sounds like you have DOS
>> drivers for the IOMEGA drive. Since DOS does not usually support USB,
> then
>> that in turn implies something in BIOS setup is enabling DOS to see a USB
>> drive. Look in BIOS setup and make sure any support for USB drives or
>> external drives is disabled.
>> --
>> Jeff Richards
>> MS MVP (Windows - Shell/User)
>> "E_Net_Rider" > wrote in message
>> ...
>> > Two days of trying to deal with the problem and Iomega and I can tell
> you
>> > I
>> > O them nothing.
>> >
>> > They are blaming MS and the OS and that is why I dropped into the site.
>> > Drive installs with USB drivers, then plugging in, followed with backup
>> > software. Note, the box says Ghost is in the box, but it is not. They
> say
>> > they've discontinued it, but still put the sticker on the box. They
> offer
>> > a
>> > free alternative, but only compatible with 2K & XP.
>> > But what happens is that all looks OK initially. Drive hooks itself to
> the
>> > USB and assigns itself the next open drive letter. All seems to be good,
>> > until I reboot. Then it grabs the D partition and shifts all partitions
> up
>> > and also the next available letter. That right, the single one
> partition
>> > of
>> > the USB drive claims to drive letters. From either the D or the K you
> can
>> > see the same contents of the drive.
>> > I changed it to removable in the device manager and assigned it letter
> X.
>> > So now it will claim D and X after a reboot. Same thing in safe mode.
>> > What am I missing that I can't seem to figure this out?
>> > And are there any good search engines that don't bring you every ad or
>> > sale
>> > in the world when searching the net for a solution?
>> > Thanks in advance. BTW, I'm running SE. And I don't know if this is
>> > related.
>> > Running thorough scandisk on that drive after running format. It has
> been
>> > running for an hour and isn't half done. The standard seemed to run OK.
>> >
>> > HELP!!!!
>> > thanks Norman
>> >
>> >
>>
>>
>
>

[E_Net_Rider]

There was a listing for USB keyboard and storage. I tried that and all I
gained was not being able to use the keyboard until in windows regular mode.
After killing power and several attempts, I did get it to recognize the
delete key so I could get in BIOS and turn it back on.
I've looked through the config.sys and autoexec.bat and see nothing that
relates to this drive.
Norman

"Jeff Richards" > wrote in message
...
> If you are seeing it listed in the BIOS hardware list then DOS will see it
> and default drivers will be installed, and that is where the drive letter
D
> is coming from for sure. There should be a way to disable it in BIOS
setup.
>
> If you can't find an item in BIOS setup that could be enabling DOS access
to
> the drive, do Start / Run / MSConfig and look in CONFIG.SYS and
AUTOEXEC.BAT
> for entries that could be enabling it, and de-select them.
>
> If you can't change the D drive letter to something else then the problem
is
> not with the Windows drivers for the device (although that doesn't mean
that
> the IOMEGA Windows drivers aren't lousy!)
> --
> Jeff Richards
> MS MVP (Windows - Shell/User)
> "E_Net_Rider" > wrote in message
> ...
> > Thanks for any intervention to break me from this harrowing experience
of
> > trying to chase this down.
> > DAY3
> > Since we will look in that direction, I did notice on the screen where
it
> > shows some of the devices during the boot that the HDD was listed by
model
> > as a mass storage device, I think.
> > As to support specifically for USB drives or external drives, I haven't
> > seen
> > anything that relates to that, in the BIOS. This is a Nforce 2 ultra400
+
> > MCPS MOBO. It does have some strange setting in the BIOS I haven't seen
> > before.
> > The only drivers I know are being loaded for the interface are for
> > Prolific
> > 2507 chip. A .sys &.pdr.
> > Comparitive note, but it may mean nothing.
> > I have a compact flash reader. it also installs itself under the hdd
> > controller and as a disk drive. I'm able to assign a letter with it
also.
> > Both hooked up through the same hub, the reader gives me no trouble. So
on
> > the surface, it would make me think Iomega has lousy drivers or the
> > interface they used is grunge.
>
>

[E_Net_Rider]

No such file on my system.
Norman

"Bill Blanton" > wrote in message
...
> Also check config.sys and autoexec.bat for iomega drivers. Imomega runs
> a guest.exe in autoexec.bat to give DOS support to its zip drives.
>
>
> "E_Net_Rider" > wrote in message
...
> > Thanks for any intervention to break me from this harrowing experience
of
> > trying to chase this down.
> > DAY3
> > Since we will look in that direction, I did notice on the screen where
it
> > shows some of the devices during the boot that the HDD was listed by
model
> > as a mass storage device, I think.
> > As to support specifically for USB drives or external drives, I haven't
seen
> > anything that relates to that, in the BIOS. This is a Nforce 2 ultra400
+
> > MCPS MOBO. It does have some strange setting in the BIOS I haven't seen
> > before.
> > The only drivers I know are being loaded for the interface are for
Prolific
> > 2507 chip. A .sys &.pdr.
> > Comparitive note, but it may mean nothing.
> > I have a compact flash reader. it also installs itself under the hdd
> > controller and as a disk drive. I'm able to assign a letter with it
also.
> > Both hooked up through the same hub, the reader gives me no trouble. So
on
> > the surface, it would make me think Iomega has lousy drivers or the
> > interface they used is grunge.
> >
> > Norman
> >
> > "Jeff Richards" > wrote in message
> > ...
> >> If drive letter D is getting assigned then that sounds like you have
DOS
> >> drivers for the IOMEGA drive. Since DOS does not usually support USB,
> > then
> >> that in turn implies something in BIOS setup is enabling DOS to see a
USB
> >> drive. Look in BIOS setup and make sure any support for USB drives or
> >> external drives is disabled.
> >> --
> >> Jeff Richards
> >> MS MVP (Windows - Shell/User)
> >> "E_Net_Rider" > wrote in message
> >> ...
> >> > Two days of trying to deal with the problem and Iomega and I can tell
> > you
> >> > I
> >> > O them nothing.
> >> >
> >> > They are blaming MS and the OS and that is why I dropped into the
site.
> >> > Drive installs with USB drivers, then plugging in, followed with
backup
> >> > software. Note, the box says Ghost is in the box, but it is not. They
> > say
> >> > they've discontinued it, but still put the sticker on the box. They
> > offer
> >> > a
> >> > free alternative, but only compatible with 2K & XP.
> >> > But what happens is that all looks OK initially. Drive hooks itself
to
> > the
> >> > USB and assigns itself the next open drive letter. All seems to be
good,
> >> > until I reboot. Then it grabs the D partition and shifts all
partitions
> > up
> >> > and also the next available letter. That right, the single one
> > partition
> >> > of
> >> > the USB drive claims to drive letters. From either the D or the K you
> > can
> >> > see the same contents of the drive.
> >> > I changed it to removable in the device manager and assigned it
letter
> > X.
> >> > So now it will claim D and X after a reboot. Same thing in safe mode.
> >> > What am I missing that I can't seem to figure this out?
> >> > And are there any good search engines that don't bring you every ad
or
> >> > sale
> >> > in the world when searching the net for a solution?
> >> > Thanks in advance. BTW, I'm running SE. And I don't know if this is
> >> > related.
> >> > Running thorough scandisk on that drive after running format. It has
> > been
> >> > running for an hour and isn't half done. The standard seemed to run
OK.
> >> >
> >> > HELP!!!!
> >> > thanks Norman
> >> >
> >> >
> >>
> >>
> >
> >
>
>

[E_Net_Rider]

Don't know if this might be related some way, but the speed seems terrible.
Tests at pcpitstop put it at about 10MB/s. Copying a 200MB file puts it
around 8MB. Pitstop puts my regular drive, same manufacturer, same drive,
except 8M cache, ahead of the rest of the pack. Sure USB2 is slower, but not
that much. When time allows, I guess I'll scan a file and see how long it
takes to transfer to the PC. What ever that is, the HDD should be able to
exceed easily.
Norman
"Bill Blanton" > wrote in message
...
> Also check config.sys and autoexec.bat for iomega drivers. Imomega runs
> a guest.exe in autoexec.bat to give DOS support to its zip drives.
>
>
> "E_Net_Rider" > wrote in message
...
> > Thanks for any intervention to break me from this harrowing experience
of
> > trying to chase this down.
> > DAY3
> > Since we will look in that direction, I did notice on the screen where
it
> > shows some of the devices during the boot that the HDD was listed by
model
> > as a mass storage device, I think.
> > As to support specifically for USB drives or external drives, I haven't
seen
> > anything that relates to that, in the BIOS. This is a Nforce 2 ultra400
+
> > MCPS MOBO. It does have some strange setting in the BIOS I haven't seen
> > before.
> > The only drivers I know are being loaded for the interface are for
Prolific
> > 2507 chip. A .sys &.pdr.
> > Comparitive note, but it may mean nothing.
> > I have a compact flash reader. it also installs itself under the hdd
> > controller and as a disk drive. I'm able to assign a letter with it
also.
> > Both hooked up through the same hub, the reader gives me no trouble. So
on
> > the surface, it would make me think Iomega has lousy drivers or the
> > interface they used is grunge.
> >
> > Norman
> >
> > "Jeff Richards" > wrote in message
> > ...
> >> If drive letter D is getting assigned then that sounds like you have
DOS
> >> drivers for the IOMEGA drive. Since DOS does not usually support USB,
> > then
> >> that in turn implies something in BIOS setup is enabling DOS to see a
USB
> >> drive. Look in BIOS setup and make sure any support for USB drives or
> >> external drives is disabled.
> >> --
> >> Jeff Richards
> >> MS MVP (Windows - Shell/User)
> >> "E_Net_Rider" > wrote in message
> >> ...
> >> > Two days of trying to deal with the problem and Iomega and I can tell
> > you
> >> > I
> >> > O them nothing.
> >> >
> >> > They are blaming MS and the OS and that is why I dropped into the
site.
> >> > Drive installs with USB drivers, then plugging in, followed with
backup
> >> > software. Note, the box says Ghost is in the box, but it is not. They
> > say
> >> > they've discontinued it, but still put the sticker on the box. They
> > offer
> >> > a
> >> > free alternative, but only compatible with 2K & XP.
> >> > But what happens is that all looks OK initially. Drive hooks itself
to
> > the
> >> > USB and assigns itself the next open drive letter. All seems to be
good,
> >> > until I reboot. Then it grabs the D partition and shifts all
partitions
> > up
> >> > and also the next available letter. That right, the single one
> > partition
> >> > of
> >> > the USB drive claims to drive letters. From either the D or the K you
> > can
> >> > see the same contents of the drive.
> >> > I changed it to removable in the device manager and assigned it
letter
> > X.
> >> > So now it will claim D and X after a reboot. Same thing in safe mode.
> >> > What am I missing that I can't seem to figure this out?
> >> > And are there any good search engines that don't bring you every ad
or
> >> > sale
> >> > in the world when searching the net for a solution?
> >> > Thanks in advance. BTW, I'm running SE. And I don't know if this is
> >> > related.
> >> > Running thorough scandisk on that drive after running format. It has
> > been
> >> > running for an hour and isn't half done. The standard seemed to run
OK.
> >> >
> >> > HELP!!!!
> >> > thanks Norman
> >> >
> >> >
> >>
> >>
> >
> >
>
>

[E_Net_Rider]

Oops! The soup has thickened.
I previously had not been watching for the card reader to flash on the
screen during the boot as the HDD would. I disabled config.sys and
autoexec.bat. Hooked up the HDD and reader and this time I put a chip in it
as I needed to transfer some pictures anyway. All looked OK. Reboot. Error
message about last cluster concerning scandisk, but don't know why it tried
to run. dismissing it and seeing the usual messages about not finding
programs, I finished the boot. I did see both devices flash on the screen.
And in windows, in addition to the w & x assigned the ext. HDD and flash
reader I now had D & E hijacked. I certainly used this reader on another
system(ME) without this difficulty.
Looks like definitely a system problem.
Norman

"Bill Blanton" > wrote in message
...
> Also check config.sys and autoexec.bat for iomega drivers. Imomega runs
> a guest.exe in autoexec.bat to give DOS support to its zip drives.
>
>
> "E_Net_Rider" > wrote in message
...
> > Thanks for any intervention to break me from this harrowing experience
of
> > trying to chase this down.
> > DAY3
> > Since we will look in that direction, I did notice on the screen where
it
> > shows some of the devices during the boot that the HDD was listed by
model
> > as a mass storage device, I think.
> > As to support specifically for USB drives or external drives, I haven't
seen
> > anything that relates to that, in the BIOS. This is a Nforce 2 ultra400
+
> > MCPS MOBO. It does have some strange setting in the BIOS I haven't seen
> > before.
> > The only drivers I know are being loaded for the interface are for
Prolific
> > 2507 chip. A .sys &.pdr.
> > Comparitive note, but it may mean nothing.
> > I have a compact flash reader. it also installs itself under the hdd
> > controller and as a disk drive. I'm able to assign a letter with it
also.
> > Both hooked up through the same hub, the reader gives me no trouble. So
on
> > the surface, it would make me think Iomega has lousy drivers or the
> > interface they used is grunge.
> >
> > Norman
> >
> > "Jeff Richards" > wrote in message
> > ...
> >> If drive letter D is getting assigned then that sounds like you have
DOS
> >> drivers for the IOMEGA drive. Since DOS does not usually support USB,
> > then
> >> that in turn implies something in BIOS setup is enabling DOS to see a
USB
> >> drive. Look in BIOS setup and make sure any support for USB drives or
> >> external drives is disabled.
> >> --
> >> Jeff Richards
> >> MS MVP (Windows - Shell/User)
> >> "E_Net_Rider" > wrote in message
> >> ...
> >> > Two days of trying to deal with the problem and Iomega and I can tell
> > you
> >> > I
> >> > O them nothing.
> >> >
> >> > They are blaming MS and the OS and that is why I dropped into the
site.
> >> > Drive installs with USB drivers, then plugging in, followed with
backup
> >> > software. Note, the box says Ghost is in the box, but it is not. They
> > say
> >> > they've discontinued it, but still put the sticker on the box. They
> > offer
> >> > a
> >> > free alternative, but only compatible with 2K & XP.
> >> > But what happens is that all looks OK initially. Drive hooks itself
to
> > the
> >> > USB and assigns itself the next open drive letter. All seems to be
good,
> >> > until I reboot. Then it grabs the D partition and shifts all
partitions
> > up
> >> > and also the next available letter. That right, the single one
> > partition
> >> > of
> >> > the USB drive claims to drive letters. From either the D or the K you
> > can
> >> > see the same contents of the drive.
> >> > I changed it to removable in the device manager and assigned it
letter
> > X.
> >> > So now it will claim D and X after a reboot. Same thing in safe mode.
> >> > What am I missing that I can't seem to figure this out?
> >> > And are there any good search engines that don't bring you every ad
or
> >> > sale
> >> > in the world when searching the net for a solution?
> >> > Thanks in advance. BTW, I'm running SE. And I don't know if this is
> >> > related.
> >> > Running thorough scandisk on that drive after running format. It has
> > been
> >> > running for an hour and isn't half done. The standard seemed to run
OK.
> >> >
> >> > HELP!!!!
> >> > thanks Norman
> >> >
> >> >
> >>
> >>
> >
> >
>
>

[Jeff Richards]

Boot to a DOS boot disk that you can create using a utility from
www.bootdisk.com. Is the drive accessible? If so, then it is being enabled
in the BIOS, and you will need to consult the BIOS documentation to discover
how to turn it off. Of course, it's possible that there isn't actually an
option to turn it off. Note that newer operating systems allow full control
over all drive lettering. Perhaps the BIOS manufacturer assumed you would be
running something newer than W98, in which case what the BIOS did with the
drive would be irrelevant (except, of course, that if it is accessible from
DOS that certainly overcomes a major problem in using these drives).
--
Jeff Richards
MS MVP (Windows - Shell/User)
"E_Net_Rider" > wrote in message
...
> There was a listing for USB keyboard and storage. I tried that and all I
> gained was not being able to use the keyboard until in windows regular
> mode.
> After killing power and several attempts, I did get it to recognize the
> delete key so I could get in BIOS and turn it back on.
> I've looked through the config.sys and autoexec.bat and see nothing that
> relates to this drive.
> Norman

[E_Net_Rider]

The Good, the Bad, & Ugly, to DOS or not to DOS,heh?
I emailed the MOBO maker about a BIOS setting if it is available. The maker
did furnish W98 & SE drivers, but maker the maker of the BIOS didn't figure
it.
Norman
"Jeff Richards" > wrote in message
...
> Boot to a DOS boot disk that you can create using a utility from
> www.bootdisk.com. Is the drive accessible? If so, then it is being
enabled
> in the BIOS, and you will need to consult the BIOS documentation to
discover
> how to turn it off. Of course, it's possible that there isn't actually an
> option to turn it off. Note that newer operating systems allow full
control
> over all drive lettering. Perhaps the BIOS manufacturer assumed you would
be
> running something newer than W98, in which case what the BIOS did with the
> drive would be irrelevant (except, of course, that if it is accessible
from
> DOS that certainly overcomes a major problem in using these drives).
> --
> Jeff Richards
> MS MVP (Windows - Shell/User)
> "E_Net_Rider" > wrote in message
> ...
> > There was a listing for USB keyboard and storage. I tried that and all I
> > gained was not being able to use the keyboard until in windows regular
> > mode.
> > After killing power and several attempts, I did get it to recognize the
> > delete key so I could get in BIOS and turn it back on.
> > I've looked through the config.sys and autoexec.bat and see nothing that
> > relates to this drive.
> > Norman
>
>

[Jeff Richards]

Be sure to let us know how it turns out!
--
Jeff Richards
MS MVP (Windows - Shell/User)
"E_Net_Rider" > wrote in message
...
> The Good, the Bad, & Ugly, to DOS or not to DOS,heh?
> I emailed the MOBO maker about a BIOS setting if it is available. The
> maker
> did furnish W98 & SE drivers, but maker the maker of the BIOS didn't
> figure
> it.