> I and many of the regulars here have been using BING for years.
> Suggest you visit the web site:
> http://www.terabyteunlimited.com/support.html and if you can't
> find an answer, email David at:
>
> support@terabyteunlimited.com
It's not BING and it's not Windows. It's almost certainly your hardware.
That's my opinion and I'm sticking to it. Test your drives and RAM, etc.,
thoroughly. Use floppy-boot drive test apps, like IBM's Drive Fitness Test,
and DocMemory from www.sysinternals.com
BIOS settings, IDE arrangement (which drives are on which cables) and jumper
settings may also be involved.
Alternatively, you could move those installation files to the C:\ drive,
just to get the slave drive out of the way. Run SYS C: from the Startup
floppy, then reboot and at the C:>\ prompt, locate and run Setup.
Just how did you partition the drive with BING (and why use BING in the
first place? I want to hear your answer rather than guess.) I trust BING
more than almost any other app to give real information about drives. Your
use of Scandisk may have been what messed it up, but that would still be
more likely due to problems with the hardware. Plus, you're talking about
the Slave drive. Did you partition that using BING? Is it possible that a
drive overlay like EZ Drive is involved?
When it comes down to it, you've provided very scant information about the
whole situation.

Signature
Gary S. Terhune
MS MVP Shell/User
> I appreciate the suggestion, but can anyone respond more
> specifically to the substance of my OP? If you and others have
[quoted text clipped - 17 lines]
> >
> > support@terabyteunlimited.com
everyman - 15 Oct 2005 21:32 GMT
> It's not BING and it's not Windows. It's almost certainly your
> hardware. That's my opinion and I'm sticking to it. Test your drives
> and RAM, etc., thoroughly. Use floppy-boot drive test apps, like IBM's
> Drive Fitness Test, and DocMemory from www.sysinternals.com
It is not BING. It is windows. Thanks for your suggestions.
> BIOS settings, IDE arrangement (which drives are on which cables) and
> jumper settings may also be involved.
[quoted text clipped - 3 lines]
> Startup floppy, then reboot and at the C:>\ prompt, locate and run
> Setup.
Better to use another drive or partition, so when winsh*t screws up I
can nuke the partition without having to worry about it screwing up even
more.
> Just how did you partition the drive with BING (and why use BING in
> the first place? I want to hear your answer rather than guess.) I
[quoted text clipped - 4 lines]
> using BING? Is it possible that a drive overlay like EZ Drive is
> involved?
Bing has proven so far to be very good. The only criticism I have with
it is that it's documentation is hard to understand and incomplete. But
they do have an excellent support group. Bing is being used to boot
several OS's from different partitions and to obviate the need to allow
windows to screw with the rest of the drive(s).
> When it comes down to it, you've provided very scant information about
> the whole situation.
Problem already solved, thanks for your reply.
When W98 was my primary system, I did not install it as you did. Instead, I
used a floppy start up disk and the W98 CD and never had any problems.

Signature
Regards
Ron Badour, MS MVP for W98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo
>I appreciate the suggestion, but can anyone respond more
> specifically to the substance of my OP? If you and others have
[quoted text clipped - 17 lines]
>>
>> support@terabyteunlimited.com
everyman - 15 Oct 2005 21:33 GMT
> When W98 was my primary system, I did not install it as you did.
> Instead, I used a floppy start up disk and the W98 CD and never had
> any problems.
Your right, that is ok way to do it. Also do not use emm386 or other mem
managers, winshit will choke on them.