Subdirectories seem to be a good idea... by date, by project, alphabetically, most recently used, whatever...

I spent about 3 hours of my time sorting the files into subdirectories at work this morning. Each program has three files (Program, graphic, CAP or interface) and even putting 50-100 files in a directory it has a 20 second lag. That would be so many sub-sub-subdirectories that I think it would be confusing. I'm not the only one running this.

I checked out that thread, thanks Mini-Max. It seems to be the mapped network drive more than the number of files. I already suggested having the program live on the hard drive and just backing up daily automatically and the IS supervisor didn't like the idea.

So what's that supervisor's idea then?

Replacing the existing software with less expensive third party software. Thus me pestering you. I don't like that idea at all.

Well then read that other thread completely, in essence it means get the dosbox
sources compiling, do some profiling, identify the slow operations, try to fix them.

I am looking at dosbox Hal's megabuild 5. I'm using dosbox at home now for dos games, imagine that.

The megabuild 5 has a line in the config for FILES=127. Is this a new feature on megabuild 5? I didn't see it in the megabuild 4 we use at work.

Looks like it:
http://home.arcor.de/h-a-l-9000/

I'll be seeing if that will make it access large directories more quickly when I get the time.

Also, does anyone know if dosbox mb5 will work under Windows 7?

> I'll be seeing if that will make it access large directories more quickly when I get the time.

It won't.

Thanks for saving me the trouble.

Is this patch in DosBox version 0.74?

I am trying to talk to a device on a serial port with an MS-DOS program.

The device sends a break signal before it starts responding.

The "break" signal is (in h/w terms) where it holds the data line in the "0" position
for a period longer than the character length (it's equivalent to unplugging the
RS232 connection, hence the name "break"). But DosBox 0.74 treats this as a
"framing error" and reports it as such and the application falls over.

Is there any way of disabling the DosBox checking the serial port framing error?

Hope you can help, regards, Roger

Looking forward to some assistance in getting the serial ports working in DOSBox.
I have set up the DOSBox config for serial ports as instructed with the following.
serial1=directserial: realport:COM1
serial2=directserial: realport:COM2

Yet, I get the following message upon running DOSBOX for both instructions.
"directserial:" is not a valid value for varible: type.

I am working version 0.74-3

Please review attached screenshot.
Any help will be greatly appreciated,

remove the : after directserial ?

Thanks much for your advice. I now have DOSBox Com2 working and the CompuSail program working as well. I apologize for my tardy response as I had shelved the project till this week. Now that my sailing season is past for the year I returned to the project. By the way, my system is Win7,64 bit.