A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows 98 » Setup & Installation
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

"Insert Windows CD"



 
 
Thread Tools Display Modes
  #1  
Old June 27th 05, 09:08 PM
Junji Tsuzuki
external usenet poster
 
Posts: n/a
Default "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?

  #2  
Old June 27th 05, 09:41 PM
Alan Edwards
external usenet poster
 
Posts: n/a
Default

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?


  #3  
Old June 28th 05, 05:22 AM
Junji Tsuzuki
external usenet poster
 
Posts: n/a
Default

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



  #4  
Old June 28th 05, 07:27 AM
Alan Edwards
external usenet poster
 
Posts: n/a
Default

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




  #5  
Old June 28th 05, 07:55 AM
Ben Myers
external usenet poster
 
Posts: n/a
Default

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?

  #6  
Old June 29th 05, 06:12 AM
Jeff Richards
external usenet poster
 
Posts: n/a
Default

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?





 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Error reloading Explorer.exe, you must re-install Windows, MSVCRT.dll file not found London General 1 April 27th 05 10:19 PM
Registery problem? Paul General 15 December 8th 04 12:29 PM
error loading explorer.exe. SHLWAPI.dll Gary General 4 October 20th 04 04:08 AM
FAQ: Win98 users: Upgrading to WinXP, IE6, etc. JM Improving Performance 6 July 26th 04 01:44 PM
Zero-byte D: drive should not show, C: missing from Device Manager *Vanguard* General 8 June 12th 04 04:19 AM


All times are GMT +1. The time now is 10:00 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.