DOSfreak!? - DOS Questions under Windows 95a
What can I do to increase data transfer over a small 8 system network. We are using a DOS based database program with 7 Windows 95 machines (The program seems to run faster on 95) and the database is stored on an NTFS partition on our Win2K Pro (Acting as our server) A couple other questions.
What can I do to increase data transfer over a small 8 system network. We are using a DOS based database program with 7 Windows 95 machines (The program seems to run faster on 95) and the database is stored on an NTFS partition on our Win2K Pro (Acting as our server)
A couple other questions...
How much memory does DOS recognize?
Are there speed limitations via networking with DOS?
What other limitations are there with DOS?
Heya DOSfreak..you around? =)
Oh..anything I can add to or remove from config.sys or autoexec.bat that might improve performance?
A couple other questions...
How much memory does DOS recognize?
Are there speed limitations via networking with DOS?
What other limitations are there with DOS?
Heya DOSfreak..you around? =)
Oh..anything I can add to or remove from config.sys or autoexec.bat that might improve performance?
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Quote:How much memory does DOS recognize?
640k Conventional
384k Upper Memory
IIRC, 64mb Extended/Expanded under all versions of MS-DOS. (FreeDos can use all available memory).
Quote:Are there speed limitations via networking with DOS?
I've never seen any 100m NIC drivers for DOS....it's been awhile since I last played around with DOS NIC drivers but a couple of months ago while playing around with an integrated NIC on a DELL using a Ghost Disk I believe the drivers were 10m. A DOS database program wouldn't benefit from a 100m NIC anyway. I would just verify that your running at half/dup or full/dup (depending on your network configuration)
Quote:What other limitations are there with DOS?
There are plenty but none that I can think of that would slow down your transfers. I recommend trying this tho. Get a test Windows 2000 workstation. Load up Connectix Virtual PC with MS-DOS on it and try your Database program from there. It's possible that transfer rate/response time would increase.
Are you actually running the program under DOS or under Windows 95? If possible try to run it under Windows 95 since you'll have the added benefit of more driver support, later drivers and a faster TCP/IP stack.
640k Conventional
384k Upper Memory
IIRC, 64mb Extended/Expanded under all versions of MS-DOS. (FreeDos can use all available memory).
Quote:Are there speed limitations via networking with DOS?
I've never seen any 100m NIC drivers for DOS....it's been awhile since I last played around with DOS NIC drivers but a couple of months ago while playing around with an integrated NIC on a DELL using a Ghost Disk I believe the drivers were 10m. A DOS database program wouldn't benefit from a 100m NIC anyway. I would just verify that your running at half/dup or full/dup (depending on your network configuration)
Quote:What other limitations are there with DOS?
There are plenty but none that I can think of that would slow down your transfers. I recommend trying this tho. Get a test Windows 2000 workstation. Load up Connectix Virtual PC with MS-DOS on it and try your Database program from there. It's possible that transfer rate/response time would increase.
Are you actually running the program under DOS or under Windows 95? If possible try to run it under Windows 95 since you'll have the added benefit of more driver support, later drivers and a faster TCP/IP stack.
As DOSFreak mentioned, I'd also try out a test box with Win 2K Pro on it with Virtual PC running a DOS machine and see if that helps out. I'm thinking that if you have a 100Mbit switch and NIC's this will help out with reducing your packet collision. This may or may not be a factor in your current setup however. You'll have to do some experimenting and see
The reason Windows 2000's dos emulation is slower is that it's using Win2K unoptimized DOS virtual machine. That is Windows 2000 all it's many layers are running underneath your DOS application. That is everything else is getting more direct access to your CPU and memory. Windows 95 on the other hand runs on DOS so it's not emulating DOS, because DOS is actually running. Therefore DOS is the closest and most actively used element by your CPU. Here's something most people don't know: Windows 95 is a DOS GUI just like Windows 3.1. In fact the only version of the Windows 9X platform that doesn't run on dos is Windows Millenium which nobody uses anyways since Win2K was better and came out first to boot. You could try the virtual machine, but I doubt that will help. Have you tried just using DOS? Do the workstations require Windows functionality as well like e-mail, web browsing, and the like?
While FreeDos might support all of your system's memory I don't think most DOS apps were written to see anything over 64 so that probably won't do you a bit of good in terms of memory gains. On the other hand FreeDos would have the most recent optmizations. YOu may however run into problems getting your real mode drivers working since FreeDos uses a different Kernel than MS-DOS. I think giving freedos a try would be an excellent idea though. Also I think there are 100Mbit drivers for dos and I'm pretty sure I observed performance gains related to them while working with a DOS/Ghost based imaging system in 1999.
While FreeDos might support all of your system's memory I don't think most DOS apps were written to see anything over 64 so that probably won't do you a bit of good in terms of memory gains. On the other hand FreeDos would have the most recent optmizations. YOu may however run into problems getting your real mode drivers working since FreeDos uses a different Kernel than MS-DOS. I think giving freedos a try would be an excellent idea though. Also I think there are 100Mbit drivers for dos and I'm pretty sure I observed performance gains related to them while working with a DOS/Ghost based imaging system in 1999.