Check that you are actually editing the config file that DOSBox uses. It's written in the console at every startup.

Yes, I have verified that it is loading the right config file.

The first two lines of the config file (non-comment are):

ne2000=true
realnic=3

DosBox lists the 3 nics (one for VirtualBox, one for VirtualPC, and the actual NIC)

shouldn't there be a section above it ? (surrounded by [])

Qbix wrote:

shouldn't there be a section above it ? (surrounded by [])

I imagine there should, but the documentation for hal9000 doesn't say what the section header should be.

Let hal megabuild create a config. It should have it

Dominus wrote:

Let hal megabuild create a config. It should have it

That was the ticket, although it put the default config in AppData/Local, when I was expecting it it to go in the same path as the program.

The section header is [ne2000] for those of you wondering.

Dosbox doesn't put the config file into the program folder anymore due to Vistas and W7s more restrictive rights management. You'd need admin rights to run dosbox otherwise...

Dominus wrote:

Dosbox doesn't put the config file into the program folder anymore due to Vistas and W7s more restrictive rights management. You'd need admin rights to run dosbox otherwise...

That makes perfect sense.

Although I'm using dosbox as a "portable" application, and running it off a USB stick.

If you put the config Into the dosbox folder it will be read AFAIK.