"Insert Windows CD"
 

Every time when we try to install a new hardware to a version of
Windows, Windows ask to put Windows CD into the CD drive and hit OK. The
next message is that the installation program cannot find a certain
driver file such as a *.vxd or alike while it is showing, for example,
E: Win98 in the folder location, which is correct. Frustrated, we add a
backslash so that it looks now E: Win98\. Saaame errrrror message.
Finally having given up, we select Cancel. Then the same thing happens
for the next file. Often we must keep canceling more than one hundred
times before we finally get out of this mess and settle with no drivers.
Next time we start Windows the same thing is repeated. If we check
whether the requested file is indeed present in the \Win98, we find a
cab file for the requested file as can be demonstrated by using extract.exe.
Because millions people will encounter this exasperation, I can't
comprehend why the Microsoft people has ignored a glitch in such a
fundamental function. Or am I missing something even dummy users know?

E:Win98 is incorrect syntax.
Try E:\Win98
(assuming E: is your CD drive)

....Alan

--
Alan Edwards, MS MVP W95/98 Systems
http://dts-l.org/index.html

In microsoft.public.win98.setup, Junji Tsuzuki
wrote:

Every time when we try to install a new hardware to a version of
Windows, Windows ask to put Windows CD into the CD drive and hit OK. The
next message is that the installation program cannot find a certain
driver file such as a *.vxd or alike while it is showing, for example,
E: Win98 in the folder location, which is correct. Frustrated, we add a
backslash so that it looks now E: Win98\. Saaame errrrror message.
Finally having given up, we select Cancel. Then the same thing happens
for the next file. Often we must keep canceling more than one hundred
times before we finally get out of this mess and settle with no drivers.
Next time we start Windows the same thing is repeated. If we check
whether the requested file is indeed present in the \Win98, we find a
cab file for the requested file as can be demonstrated by using extract.exe.
Because millions people will encounter this exasperation, I can't
comprehend why the Microsoft people has ignored a glitch in such a
fundamental function. Or am I missing something even dummy users know?

Sorry about misstype. But as you know E:\WIN98 is automatic.
It seems that you don't have any problem by accepting that automatic
typing. If tha's true, please confirm.

Alan Edwards wrote:

E:Win98 is incorrect syntax.
Try E:\Win98
(assuming E: is your CD drive)

...Alan

E:\WIN98 is not automatic for me, as mine is D:\Win98 and I don't
recall a problem accepting that. It is what shows in the Registry for
SourcePath in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Setup

....Alan

--
Alan Edwards, MS MVP W95/98 Systems
http://dts-l.org/index.html

In microsoft.public.win98.setup, Junji Tsuzuki
wrote:

Sorry about misstype. But as you know E:\WIN98 is automatic.
It seems that you don't have any problem by accepting that automatic
typing. If tha's true, please confirm.

Alan Edwards wrote:

E:Win98 is incorrect syntax.
Try E:\Win98
(assuming E: is your CD drive)

...Alan

Try extracting fresh copies of "layout.inf", "layout1.inf" and =
"layout2.inf"
from your Windows 98 CD to the "c:\windows\inf" folder.

Ben

"Junji Tsuzuki" wrote in message =
news:B0Zve.1308$Zt.578@okepread05...
Every time when we try to install a new hardware to a version of=20
Windows, Windows ask to put Windows CD into the CD drive and hit OK. =
The=20
next message is that the installation program cannot find a certain=20
driver file such as a *.vxd or alike while it is showing, for example, =
=20
E: Win98 in the folder location, which is correct. Frustrated, we add =
a=20
backslash so that it looks now E: Win98\. Saaame errrrror message.=20
Finally having given up, we select Cancel. Then the same thing happens =

for the next file. Often we must keep canceling more than one hundred=20
times before we finally get out of this mess and settle with no =
drivers.=20
Next time we start Windows the same thing is repeated. If we check=20
whether the requested file is indeed present in the \Win98, we find a=20
cab file for the requested file as can be demonstrated by using =
extract.exe.
Because millions people will encounter this exasperation, I can't=20
comprehend why the Microsoft people has ignored a glitch in such a=20
fundamental function. Or am I missing something even dummy users know?

Try copying your CAB files to a location on the hard disk, and then nominate
that location for Windows to search for the files it needs.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"Junji Tsuzuki" wrote in message
news:B0Zve.1308$Zt.578@okepread05...
Every time when we try to install a new hardware to a version of
Windows, Windows ask to put Windows CD into the CD drive and hit OK. The
next message is that the installation program cannot find a certain
driver file such as a *.vxd or alike while it is showing, for example,
E: Win98 in the folder location, which is correct. Frustrated, we add a
backslash so that it looks now E: Win98\. Saaame errrrror message.
Finally having given up, we select Cancel. Then the same thing happens
for the next file. Often we must keep canceling more than one hundred
times before we finally get out of this mess and settle with no drivers.
Next time we start Windows the same thing is repeated. If we check
whether the requested file is indeed present in the \Win98, we find a
cab file for the requested file as can be demonstrated by using
extract.exe.
Because millions people will encounter this exasperation, I can't
comprehend why the Microsoft people has ignored a glitch in such a
fundamental function. Or am I missing something even dummy users know?