PDA

View Full Version : Extracting Files


jimb11
January 23rd, 2004, 07:02 PM
When I put my start up disk in I pick to boot from cd rom support. At the a prompt I type ext. It then asks what path I want to extract the file from. I want to extract from the windows me cd but I'm not sure what path I should type in at the a prompt. I know the files I want are in win9x/precopy1 but what is the exact path I should type in?

GretaP
January 23rd, 2004, 07:36 PM
Hi jimb11,
Type in the drive letter of the CDROM followed by :\win9x
The drive letter for the CDROM will be specified in this line that should appear above the A: prompt when you first boot from startup disk and choose to start WITH CDROM SUPPORT:
Drive X: = Driver MSCD001 unit 0
(where the X that I have written will display the actual drive letter designation that your CDROM is going to use)

If the CDROM drive letter is E, then, for the path, you'd key in:
E:\win9x

jimb11
January 23rd, 2004, 08:08 PM
I tried that and it did the scan but didn't find any of my files I want. The files are on the cd so why didn't they show up? The two files are netdi.dll and netos.dll both in precopy1 of win9x.

GretaP
January 23rd, 2004, 08:32 PM
You could give the following command a try (it assumes that your CDROM drive letter is E and that the destination for the extracted files is C:\Windows\System.....replace with the appropriate information, if necessary):

extract /a e:\win9x\base2.cab netdi.dll /L c:\windows\system
and
extract /a e:\win9x\base2.cab netos.dll /L c:\windows\system

jimb11
January 23rd, 2004, 09:03 PM
I tried that and it still tells me no matching files.

GretaP
January 23rd, 2004, 11:47 PM
If you haven't already done so, give this a try:
extract /a e:\win9x\precopy1.cab netdi.dll /L c:\windows\system
and
extract /a e:\win9x\precopy1.cab netos.dll /L c:\windows\system

jimb11
January 25th, 2004, 07:07 PM
I tried to extract these two dll files and I think it worked but I'm not sure because when I went into my system folder and checked the two files it didn't show today's date 1/25/2004 in the created:column. Should it do that? When I extracted the two files it asked me if I wanted to overwrite the files in the c: windows system and I said yes and then it continued on and then went to another A prompt. I figured it was finished and that everything worked so I pulled out the start up disk and cd-rom and rebooted back to windows.

GretaP
January 25th, 2004, 09:34 PM
It sounds like everything worked out okay.....did it help to resolve whatever problem you were troubleshooting for which you wanted to extract those two files?

What date is displayed in the Created column?

jimb11
January 25th, 2004, 09:48 PM
1/19/2004 is the date in the created:column because I downloaded the files from a web site on that date. But when I extracted the same exact files from the windows cd today and then checked to see if the created:column changed to today's date it still read 1/19/2004. That's why I don't know for sure if it worked because if it did work wouldn't it have changed the created:column date to 1/25/2004?

I extracted netdi.dll,netos.dll and netcpl.cpl and my network tool in control panel still doesn't open. I thought these files would fix the problem but they didn't. Do you happen to know what could be wrong?

GretaP
January 25th, 2004, 11:38 PM
When you try to open Network applet, does it just not open or do you get an error message?
I know that a few days ago someone was having a problem with Control Panel and ended up resolving it by extracting the Rundll32.exe file from the CD to C:\Windows folder. However, I think that they were not able to open Control Panel at all. Might be worth a shot, though.

jimb11
January 25th, 2004, 11:43 PM
I can open control panel but when I click on the network icon I get this error message: Your program is making an invalid dynamic link call to a .DLL file.

GretaP
January 26th, 2004, 02:58 AM
I can't find anything on that error as it applies to the network applet in Control Panel. Have found other stuff, but the fixes relate to the specific program that's causing the error........either that, or very broad "fixes" (i.e., reinstall the operating system to replace/restore the corrupted or missing DLL that's causing the problem.....the one that doesn't get mentioned, of course, so you can't pinpoint it).