Jump to content

CamTron

Member
  • Posts

    286
  • Joined

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by CamTron

  1. I ran into a bit of a problem installing the SNAP graphics driver. While running the inst9x.bat script, it throws an 'Unable to create directory' error when trying to create the 'C:\Windows\System\Snap' directory. I'm not sure, but I think this is because it creates an extensionless file called SNAP in the SYSTEM directory, and as we know, having two items with the same name is a no-no. And hence, when the script tries to copy the config files, it says "Path not found". Under Linux, the SNAP file shows up as a DOS\Windows executable, so I just renamed it SNAP.EXE. I figured this was probably okay. Then I just manually made the directory and copied the files. It didn't say anything when I right-click>installed the .inf, but it showed up when I clicked Change Display Device. Only problem is I can't get 1024x600 resolution. Selecting 1024x768 cuts of the bottom. I want to try GAMODE.exe, but I don't know what to put as <device>. I still have bearwindows's VBIOS TSR installed at boot.
  2. OK, so the PATH environment variable does exist in DOS/Windows. That's great. This is a bit off-topic, but what's the easiest way to create a symlink in Windows?
  3. Do these things work for Windows 8? Man, would that be awesome!
  4. In Linux, we can open a terminal and run a command by simply typing in the command's name. So, if I wanted to run DosBox, I'd just type: dosbox The $PATH environment variable is set to /bin,/sbin,/usr/bin,/usr/local/bin,/usr/local/games. And Linux looks in all of those directories for the executable. However, in Windows, one must type the full path of the executable. So, typing: C:\Program Files (x86)\DOSBox-0.74\DOSBox.exe would run DosBox. Is there an easy way to run programs from Command Prompt without having to type all of this?
  5. I don't really think this is true. I've been able to run Windows 95 on a Celeron 353 M @ 900 MHz with no problems. I do sometimes get a BSOD when I reboot after making a lot of configuration changes, but it's not that common.Are there any Windows 95 drivers for an Intel 915GM chipset?
  6. I read that forum. Where do you obtain the Atheros ndis2 driver? I can't find such a thing. I assume wireless is out of the question for Win95, but I'd like to be able to plug in my ethernet cable and connect to my wired network.I do get nice software shutdowns with Win95, even though it doesn't at all support ACPI, which must mean that the Eee PC's BIOS has some APM features. Win95 doesn't detect my AC adapter or battery, so the Eee PC must not be fully APM-compatible. I must also note that the BIOS can emulate a USB device, so USB keyboards and mice will work, although the USB mouse is a bit jerky.
  7. So... I guess this means that MS-DOS is now open source! Releasing the source code for something just doesn't seem like Microsoft, but I guess it's got no practical value other than educational purposes. Interesting, to say the least!
  8. While cleaning out my closet recently, I found my old Windows 95 installation disk that came with my first computer (still in working order). So, I decided to test it out and see if it could run on modern (2008) hardware. I followed this YouTuber's tutorial on running Windows 3.1 from a flash drive, but copied the files from my Win95. The installation went successfully and it booted right up after editing the System.ini file to work around the memory bug. So, I've decided to challenge myself and see how useful I can make it run. I've installed BearWindows's VBEMP9x driver to get correct display resolution, and a mouse wheel driver to get two-finger scroll working. But I currently have no sound or ethernet. I could not find a Realtek HD Audio driver nor a Atheros AR81xx to get these working. Has anyone attempted this on similar hardware? Is it possible to use DOS drivers for some of these things? This is an Asus Eee PC 1000HD and I'm running Windows 95 OSR1 "A".
×
×
  • Create New...