VOGONS


Windows 95

Topic actions

First post, by snipe

User metadata
Rank Newbie
Rank
Newbie

Hi all, Just wondered if someone could help me out here.
I have successfully managed to get windows 95 running via DOSBox, I have DOSBox portable running on my USBdrive and a hdd image which contains a windows 95 installation, also in that directory. So I now have a portable windows 95 system which I can run on any machine be it mac or PC. So far so good!
I then managed to get the correct sound drivers installed so that the emulated SB16 card works nicely and I was able to hear the old familiar windows start-up tune! I managed to install the correct display drivers so that I have 1024x768 resolution and 16bit colour.
OK then, my problem is getting the internet up and running, ie communicating with the router used by my host machine, via the emulated dial-up modem in DOSBox.
For instance I need a telephone number to dial out to, is this the IP of my router, or the host PC?
Any advise would be very welcome.

Many thanks.

Reply 3 of 18, by Svenne

User metadata
Rank Member
Rank
Member

How did you manage to install Windows 95? I get the "invalid DOS-version" error.

Intel C2D 2.8 GHz @ 3.0 GHz | ASUS P5KPL | ASUS GTS250 1 GB | 4GB DDR2-800 | 500 GB SATA | Win 7 Pro/Ubuntu 9.10

Reply 4 of 18, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author
snipe wrote:

Thats great, thanks. Real DOSBox novice here, only been using it for 5 days, how do I install the patch ".diff" into DOSBox?

Get the binary, not the patch file.

1+1=10

Reply 5 of 18, by snipe

User metadata
Rank Newbie
Rank
Newbie

Svenne: As I said I am a novice when it comes to DOSBox, but from what I understand, you could try typing 'ver set 8.0' (without the quotes) and that may solve your problem??

h-a-l-9000: Thanks for the info, am I to assume that this is the latest 'Megabuild'? Its just that I am currently running the portable DOSBox and would prefer to continue doing so if possible?

Thanks

Reply 6 of 18, by DosFreak

User metadata
Rank l33t++
Rank
l33t++

They are both have the same "portability".

DOSBox Compilation Guides
DosBox Feature Request Thread
PC Game Compatibility List
How To Ask Questions The Smart Way
Running DRM games offline

Reply 11 of 18, by snipe

User metadata
Rank Newbie
Rank
Newbie

I appreciate that you could make any build portable, it's just that the version I have is specifically designed to be used on USB drives, it uses the bare minimum of writes to the drive thus prolonging the life of the device. Given the life of an average mlc flash device is over 10k read/write cylces but still! 😉

Reply 14 of 18, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Well, one could modify DOSBox and SDL to eliminate the stderr and stdout files... those are a source of create, write, and delete activity through normal use. Dunno if that's what was done, though.

Edit: I just tried creating 0-byte stderr.txt and stdout.txt files where dosbox.exe is located and marked them as read-only. Using the filemon app, I see that all the create, write, and delete activity for them silently fails. So, one doesn't need a custom build to shut down the writing associated with those files.

Reply 15 of 18, by leileilol

User metadata
Rank l33t++
Rank
l33t++

Ironically i've seen the 'portableapps' stuff write more to the USB drive than typical, kind of defeaitng thier own point.

Besides, if you're going to have a PORTABLE Win95 install, you can't, as the drive image will ALWAYS be written to, screwing all your genius USB plans. DOSBox doesn't support Undo Disks.

apsosig.png

Reply 16 of 18, by snipe

User metadata
Rank Newbie
Rank
Newbie

Portableapps.com host software which has been modified in such a way that most of the writes are done in the RAM rather than the USB, in my experience with their software, it seems to be true in most cases. I will not argue the point with you over 'portable DOSBox' as I wouldn't have a clue if this is the case here or not, I can only take the word of those hosting the site. The fact that DOSBox writes to an image file, as mentioned, would certainly suggest that there has to be pretty heavy writing to the drive for that alone, so I suspect you have a point. Ok so I will try the NE2000 route again, how do I install te binary into the official build?