Setup Has no Driver for Installing Drivers

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?

The verbatim text of an error message is essential when you post a problem.

One thing that you may find out is that upgrading a W95 box to W98 is
generally not a good idea as there are often too many problems to solve.
I've found that a clean install of W98 gives a much better running and
stable system. For information on installing W98, go to:
http://home.satx.rr.com/badour/html/w98_restore.html

--
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



"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?

That was the verbatim. The blue screen simply states cannot write to the C
drive, and the problem is that at some point that script leaves the computer
without a driver to do it with.

I am not happy with the upgrade so far either, although I have located
copious documentation indicating that hardware problems with the install are
a known problem at that point in the script.

Is there a way to uninstall 98 at this point? I do have it in there as a
recoverable install, with backed up files, but since it did not complete, I
don't have the tools I should have at this point.

"Ron Badour" wrote:

The verbatim text of an error message is essential when you post a problem.

One thing that you may find out is that upgrading a W95 box to W98 is
generally not a good idea as there are often too many problems to solve.
I've found that a clean install of W98 gives a much better running and
stable system. For information on installing W98, go to:
http://home.satx.rr.com/badour/html/w98_restore.html

--
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



"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?

Verbatim means to list **exactly** what it says, not tell us what it says in
your words.

This article will tell you if you can uninstall W98 and how to do it:

http://support.microsoft.com/?kbid=186102


--
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



"internetuse" wrote in message
...
That was the verbatim. The blue screen simply states cannot write to the
C
drive, and the problem is that at some point that script leaves the
computer
without a driver to do it with.

I am not happy with the upgrade so far either, although I have located
copious documentation indicating that hardware problems with the install
are
a known problem at that point in the script.

Is there a way to uninstall 98 at this point? I do have it in there as a
recoverable install, with backed up files, but since it did not complete,
I
don't have the tools I should have at this point.

"Ron Badour" wrote:

The verbatim text of an error message is essential when you post a
problem.

One thing that you may find out is that upgrading a W95 box to W98 is
generally not a good idea as there are often too many problems to solve.
I've found that a clean install of W98 gives a much better running and
stable system. For information on installing W98, go to:
http://home.satx.rr.com/badour/html/w98_restore.html

--
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



"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?

Sounds like an I/O problem. Hard to say unless, as Ron said, you give the
exactamoondo error message.

--
Lil' Dave
Beware the rule quoters, the corp mindset, the Borg
Else you will be absorbed
"internetuse" wrote in message
...
That was the verbatim. The blue screen simply states cannot write to the
C
drive, and the problem is that at some point that script leaves the
computer
without a driver to do it with.

I am not happy with the upgrade so far either, although I have located
copious documentation indicating that hardware problems with the install
are
a known problem at that point in the script.

Is there a way to uninstall 98 at this point? I do have it in there as a
recoverable install, with backed up files, but since it did not complete,
I
don't have the tools I should have at this point.

"Ron Badour" wrote:

The verbatim text of an error message is essential when you post a
problem.

One thing that you may find out is that upgrading a W95 box to W98 is
generally not a good idea as there are often too many problems to solve.
I've found that a clean install of W98 gives a much better running and
stable system. For information on installing W98, go to:
http://home.satx.rr.com/badour/html/w98_restore.html

--
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



"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?

That was exactly what it said.

The script is a real illustration of the use of entry level persons to write
installation scripts which are not carefully tested prior to use, as a mess.

The hardware installation installed 3 of everything, most of which I did not
have.

Manual surgery on that hardware system manager shortened the process, but
the script still fails and the mess really is that whoever wrote this up, has
a path of execution that results removing all the drivers without leaving one
to write to the C drive with for installing the new ones.

FourthShift had a release that was like this when the install script was run
too, and the XP upgrade for nonNT family windows is on this level too.

I am going to uninstall 98 as I cannot install without executing a path that
cannot possibly complete due to whatever the internals are that my system
config is resulting in.

I would like to know if the manual extraction of cab files and install from
disk is less likely to also give the same hardware error, which appears to be
general 98 install problem that is probably in all the script versions for my
configuation based on prior experience with the scripts MS produces for this
and the profit margin using people who will stay up all night and work for
low pay until they are no longer low paid or something, produces as the
programmers don't know how to do the versions of software that are not bloat
ware, for example, and the bugs that cannot be fixed or cost a fortune for
persons who it is unreasonably hard for for that reason, are also just
commonly what it costs too much to fix for MS since the market will not pay
the additional costs.

Unless Tiger and Unix showing up eventually make this competitive enough
that addressing this problem has to happen.

Thanks anyway.

"Ron Badour" wrote:

Verbatim means to list **exactly** what it says, not tell us what it says in
your words.

This article will tell you if you can uninstall W98 and how to do it:

http://support.microsoft.com/?kbid=186102


--
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



"internetuse" wrote in message
...
That was the verbatim. The blue screen simply states cannot write to the
C
drive, and the problem is that at some point that script leaves the
computer
without a driver to do it with.

I am not happy with the upgrade so far either, although I have located
copious documentation indicating that hardware problems with the install
are
a known problem at that point in the script.

Is there a way to uninstall 98 at this point? I do have it in there as a
recoverable install, with backed up files, but since it did not complete,
I
don't have the tools I should have at this point.

"Ron Badour" wrote:

The verbatim text of an error message is essential when you post a
problem.

One thing that you may find out is that upgrading a W95 box to W98 is
generally not a good idea as there are often too many problems to solve.
I've found that a clean install of W98 gives a much better running and
stable system. For information on installing W98, go to:
http://home.satx.rr.com/badour/html/w98_restore.html

--
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



"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?

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?

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?

If Windows will start in Safe mode, go into Control Panel,
System, Device Manager and remove any duplicated
entries. Then restart normally. You may be prompted for
your Windows 98 CD.

Ben

"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?

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?