CamTron

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?

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?

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.

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!

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".