Setup Has no Driver for Installing Drivers

Thank you.

By the way, my diatribe about bugs at MS and most companies is just that the
software they write and maintain currently is many orders of magnitude more
complicated than it was when very smart people could write entire operating
systems for simpler systems.

I think the paradigm from then and saving money by keeping that paradigm is
not saving any money, its making things more difficult and expensive. And
that places like MS should cultivate people who will stay, even part-time or
for a consulting arrangement, so they have as many highly expert people as
possible for the bugs that are too costly for other people to fix, as
actually much cheaper and producing better software.

"PattyL" wrote:

In addition to Ben's suggestion, you might try using a clean system.ini. In
any upgrade situation, it's possible that there are older drivers loading in
the system.ini that are incompatible with Win98. In an upgrade situation,
Windows will take care of and upgrade any drivers that were included with
the earlier version of Windows but it leaves third party drivers in place.
In this case, you need to get the correct drivers from the manufacturer of
the hardware. I'm not sure what you are referring to when you say "system
config" but if you mean system.ini, this will take care of any unwanted
device drivers loading from the earlier version.

If you haven't tried a clean install on this computer, I'd try that. If it
works, that should tell you that the problem is with something in the
earlier version that is being upgraded.

Creating a New System.ini File Without Third-Party Drivers
http://support.microsoft.com/?kbid=140441

How to Install Windows 98 Into a New Folder
http://support.microsoft.com/?kbid=193902

BIOS upgrades often fix the problem of duplicated hardware devices during
installation.

PattyL


"internetuse" wrote in message
...
As a former developer, I took apart what I had access to, as someone
probably
too expensive for Microsoft who does the 4 hour job for the employees who
had
the 9 month debacle of bringing the entire system down with a key bug
nobody
had any idea about, the following is the case.

That is the error message, like I said.

The development screwup is that the script has installed many copies of
system components for example, such that I appear to have 8 C drives
between
the types of devices that the script has installed.

As why people like me come in to consult and take care of problems like
this, created by the fact that no matter how smart people are, they are
not
the creatures on Stargate imparted with all prexisting knowledge by any
process MS can provide.

The system then does not have a driver for my drive, either due to the
path
not leaving any driver or the drunken midnight programmer who wrote that
part
of the script having it running through devices mistakenly installed which
cannot operate my device.

Like I said, no driver, and I really don't want to fix that system config
for the "devices" either, as it is a real drunken list of devices not on
the
system for the most part.

Apologies, but that is why problems like this are too costly to fix at MS,
the same way the 9 month debacle was a 4 hour eval, fix, and put in
production problem for me, from our point of view.

"Ben Myers" wrote:

A look at "c:\setuplog.txt" might be helpful. Please note that this
file usually has the "hidden" attribute set.

Ben

"internetuse" wrote in message
...
I am upgrading Win95 to Win98, setup /c, and when the script gets to
installing drivers, the graphic stops, and eventually a blue screen
with a
message about not being able to write to the C drive comes up.

And the process stops.

Is there a fix or workaround for this problem?