A Windows curiosity

[PtBetsie]

Not a problem, just looking for an explanation on this. I wanted to install the onboard sound files for a system running WIN98SE. When I tried, it told me to insert the WIN98 cdrom as it was looking for some files. I did, but it kept telling me it couldn't find them on the cdrom. I then went to another computer running the same vintage WIN98SE, did a search and found the files which I then inserted into Windows/system on the first pc. Then it completed the audio install. Why couldn't it find the files on the WIN98SE install disk?

[classicsoftware]

You need to point the system to where the install files are located.

Usually in Windows\Options\Cabs Folder

[Whyzman]

My off-the-cuff thought would be that usually when the system is scanning the Operating System installation disks for files it needs "fairly" precise direction to the area the file is contained.

The "browse" function that we usually are furnished to find a file in these instances most often doesn't let us actually point to the file itself but rather to a "folder" where the file might possibly be contained...

I'm wondering if when you put the disk into the other machine where you could actually perform a file search or explore if you were afforded more detailed search capability...

[classicsoftware]

Whyzman:

When the disc was palced in the other machine, it was already set in the registry to read the cab files from the cd rom.

They key, no pun intended, is the registry key:

HKLM\Software\Microsoft\Windows\Current Version\Setup\SourcePath

If the source path matches where the cab files are, then when presented with the option to insert the cd, after inserting the CD you need to browse to the location of the CAB files.

[PtBetsie]

When I inserted the cdrom, it brought up the Windows/Cabs option but then gave the error message about not finding the file. If there was a different cab file needed, I wouldn't know which one to choose.

[Whyzman]

Yeah, what's up with that anyway?! :D You'd think that when Windows tells you to insert the OS disk because it needs a file that it knows where it is on the disk...what's up with the browse deal? Windows certainly should know on its own stuff if it needs a CAB file where to look for it...

I freely admit that working with files is not my forte...definitely, my back is sore from being bent over the learning curve for so long. :)

Example: When I was first upgrading from a Win95 system to Me. Newbie comes to the part where it says to insert your Win95 disk for product verification. Okay, I extract the Me disk and insert the Win 95 disk...then it asks me to browse the disk.

Given the choices there, I begin to ask myself, "It certainly knows what it wants and it certainly should know where it is!" So, I start highlighting folders...down at the bottom of the list was the Win95 folder...it took a bit of trial and error to get there.

I'm understanding your explanation classic, I guess I'm just not sure why Windows isn't smart enough to provide the path when it reads it's own product disks when it's looking for a specific file??

I need a back rub! ;)

[classicsoftware]

Becuase let's say you are installing a NIC and the program to fetch files is reading the E:\driver\win95 folder. When you need to get a Windows file, you need to point it back to the E:\Win95 folder or the C:\Windows\Options\Cabs folder.

I agree it should know where it put the files, but it's windows..... :eek:

[Fruss Tray Ted]

I guess at this point in time just being 'Windows' is an excuse in itself! :rolleyes:

Windows, "I'm having trouble getting in contact with my inner self. I need help and guidance to achieve harmony and inner peace"... :D