Jump to content

LoneCrusader

Moderator
  • Posts

    1,495
  • Joined

  • Last visited

  • Days Won

    7
  • Donations

    3100.00 USD 
  • Country

    United States

Everything posted by LoneCrusader

  1. I actually do not have much experience with this. I know generally HOW to do it, but I have never needed to do it manually or add it to Windows. Boot Disks are already automated for it. So I hope some other members will chime in. Take a look at these pages, which are directed more at your situation rather than directed at use on Boot Disks. (And there are no weird references to "tomatoes" or "bananas" ) MSKB Article on the subject. General CONFIG.SYS and AUTOEXEC.BAT instructions. (Many of the examples given on the second one are not really necessary, just depends on the machine and user preference.) You will need to load OAKCDROM.SYS in CONFIG.SYS, and MSCDEX.EXE in AUTOEXEC.BAT.
  2. No. Name of the package should be "W95ws2setup.exe." I don't have a link for it handy at the moment, but if you can't find it I will upload it somewhere. Try looking on MDGx.com under the 95/95OSR2 Updates sections.
  3. EXPLORER is probably set to "Hide filename extensions for known file types." In this case the .BAT would be hidden. I always disable that setting, and always turn on "Show All Files."
  4. Links already given. I doubt you would be able to "easily" find it on Microsoft's site these days...
  5. Hmm.. I don't think I've ever seen that before, but maybe TCP/IP was already installed on all of the systems I installed the Winsock2 update on. Windows 95 supports TCP/IP, but does not install it by default. It has to be manually selected during install or added afterward. The TCP/IP protocol can be installed by going to: Start>Settings>Control Panel>Network stay on the Configuration tab click Add choose Protocol click Add again choose Microsoft choose TCP/IP click OK you will have to restart at this point.
  6. You can just leave them sitting there. If they are compressed, they will not be detected.
  7. Well... It's not so easy as you make it sound. The Windows 9x CAB files are all "linked" together like a split RAR archive, etc. You can't rebuild ONE of them without breaking the chain of links. Also, there is a major "learning curve" about how Windows 9x SETUP works and how to add things to it. You have 3 options - 1.)Copy the \WIN98 folder from the CD to your HDD and fully unpack/extract (no .EXE or .ZIP, etc, must break down all the way to .INF's and SYS/VXD/whatever) the drivers you want into it, then create a new CD. SETUP will use any drivers or any newer files it finds in the \WIN98 folder. 2.)Read up on, and use this. 3.)Purchase RLoew's slipstreaming tools.
  8. "Root" means the "Root folder," or in other words just in C:\ without being inside another folder. The "\" without any "named" folder after it stands for the root folder. You'll have to read up on basic DOS commands and PATH. It's essential to really knowing how your computer works, not just with Windows 9x, but with any system. A drive must be partitioned and formatted. Then the entire file and folder(directory) structure is built from the "root" folder C:\. So, in other words, WINDOWS\ is a subfolder of the root folder, and \SYSTEM is a subfolder of the WINDOWS folder. The PATH to this location would be C:\WINDOWS\SYSTEM\ and you get there by typing CD\WINDOWS\SYSTEM. "CD" is "Change Directory" and the backslashes \ denote deeper folder(directory) levels. In order to run a program, you must first navigate to the folder(directory) where it resides before you issue the command to run it. Take a look at the "Properties" of some of the Shortcuts in the Start Menu, say for Notepad or the Calculator for example. Notice the paths given to each program and how Windows automates this.
  9. No DOS CDROM driver is loaded. You will have to load a DOS CDROM driver or copy the DETECT.EXE to your hard drive (C:\). Since you have no DOS experience, the easiest way to get a DOS CDROM driver loaded would be to use a Windows 9x Boot Disk... But the best thing to do for now is place DETECT.EXE in the root of the C:\ drive. When you get the C:\WINDOWS> prompt, type "cd\" and press ENTER. Then type "DETECT" and press ENTER.
  10. So if I restart Win95 in MS-DOS mode, I can run it from there? Yes, or press F8 while the machine is first booting up and choose "Command Prompt only" from the Startup Menu. Ok, I am at the command prompt with the detect program on cd. I'm trying D>setup, D>detect, not sure what to do here. Never ran DOS programs. I assume you are at the "C:\>" prompt? If so type "D:" (or the letter of the CD drive if not D) without the quotes and press ENTER. Should get a "D:\>" prompt. Then type "DETECT" and press ENTER.
  11. Yes, but be certain you have a backup of those drivers in case they are needed again. NUSB provides a generic driver that should work for all such devices, but keep a copy of the original in case your devices don't play well with NUSB.
  12. So if I restart Win95 in MS-DOS mode, I can run it from there? Yes, or press F8 while the machine is first booting up and choose "Command Prompt only" from the Startup Menu.
  13. With 7-Zip or WinRAR, etc.
  14. I only have 2 nVidia cards in all of my computer parts stockpile... I always used 3dfx (long ago ) and ATi cards, so I am not very familiar with nVidia... I believe later versions of the nVidia Control Panel do not work on 95 at all. I seem to remember something about the 77.xx (??) release of ForceWare being the last version that works 100% under 95, but I can't remember where I got that information. The later drivers may work, but the Control Panel itself does not. Many of these may be unrelated, but besides DCOM95, and DirectX8, I always install the Winsock2 update, the Windows 95 Y2K update, Dial-Up Networking 1.4, Internet Explorer 5.5 SP2, and Windows Media Player 7 (or unofficial 7.1). Should be able to get MSCONFIG from here...
  15. EDIT 06-10-2013: THIS LINK IS NOW TO THE OLD VERSION 2.0. SEE THE NEXT POST, OR THE FIRST POST OF THIS THREAD FOR THE NEW VERSION 3.0. Due to reported problems with MDGx's website , Drugwash has kindly provided a new download link for FIX95CPU. This will be in effect until we find out what is going on...
  16. Thanks for hosting those files. I will add the link to the FIX95CPU thread until we know what is going on. I have thought about trying to make a backup of the website, but I have no experience with such things at all. We do need to hake some proactive steps though, just in case... and even many of those old, broken MS links are valuable now because some of them still work in the Wayback Machine and others may give the specific names of package files that could be lost otherwise...
  17. I have also been concerned about MDGx, he did not answer the last couple of emails I sent him (2 or 3 messages over a span of about a year) so we may need to look into making some kind of archives in case his site goes down... The files inside FIX95CPU.ZIP should carry a date of 4/16/10, and the README should say "Version 2.0." USBSTR95 was only issued in one version AFAIK, and 12/2007 is correct I believe.
  18. USBSTR95 is a little "disorganized" as it was left in a Beta state before PassingBy left us. However, USBSTR95 contains the BEST CURRENTLY (PUBLICLY) AVAILABLE USB Storage Drivers for Windows 95. I know this for a fact, because I have spent literally DAYS combing DriverGuide, old FTP servers, and the like searching for better drivers. I have even contacted the manufacturers of early USB Storage Devices (such as Phison and Apacer) and requested any older 95-compatible drivers they may have had (no luck here of course, all claim to have never supported it, despite some documentation I have found that claims otherwise... ). The only "issues" with USBSTR95 are 1)unnecessary files included, and 2)a later version of EjectUSB exists than the version in the full package. The drivers themselves have limitations, but this it not the fault of USBSTR95 or PassingBy who created it.
  19. I believe they are all fine. Only (usually) on a much newer system would you have to do a lot of worrying about these settings.
  20. If you use the two official USBSUPP packages, do NOT use my XUSBSUPP update that I linked. They should not be mixed. XUSBSUPP, while itself "unofficial," merges ALL available official USB-related updates into ONE installation. (Includes USBSUPP.EXE, USBUPD2.EXE, and 4 or 5 HotFixes)
  21. (It's like a hot potato , pass it on ) jaclaz BTW, off-topic, but after finding this I finally understand the "de La Palice" references.
  22. Eh? I assume specific to non-US keyboards. Should be Ctrl+Alt+Del on US ones.
×
×
  • Create New...