http://www.infradead.org/devload/

There are other tools like that too.

Or you can always boot DOS in DOSBox.

Hi
Thank you for a quick reply!

I'm not able to download from http://www.infradead.org/devload/
Could you please send me another link?
BEs

Works fine, try another PC.

Ok. Thanks. I'll try later today. BEs

Hi
Has anyone used devload?
When I use it:
c:\>devload.exe /v comdev.dev 9600 with program and driver at root
devload reports filename and load adress : 011B:000
then dosbox "freezes"

Any sugstions?

BTW, The same thing happens if I try to load ansi.sys

Then, try DEVICE.COM from QEMM software instead.

Thank you ykhwong.
That device program loads the driver. Now I must deal with the communication which doesn't seem to work.

Hi, I have little bit similar question:
I want to use program which uses so called GSS drivers. It needs the DOS device driver named "GDMS" to be installed.
Even I install GDMS driver via recommended DEVICE.COM, program cannot open this driver. Installation of GDMS looks to be OK (driver is correctly placed in DOS devices internal list).
After bit of debugging I saw that the program tries to open "GDMS" device via INT 21h AH=3dh but it is unsuccessful.
I made short look into DOS Box source code and it looks like DOS Box cannot use any installable DOS device driver - there are only standard DOS devices inside DOS Box which are emulated "inside" DOS Box.
Questions:
1. Did I miss something?
2. If my analysis above is OK, exists some workaround how to make installable DOS device working in DOS Box?

Note: I know it is possible to boot DOS in DOS Box but I am afraid:
a) It will be probably slower.
b) It maybe doesn't help in this case.

DOSBox does not support device drivers that are accessed through their name; meaning that the driver cannot be opened, read from, written to, or communicated with via IOCTL functions that use a handle. Some device drivers can be used, at least partially, through interrupt calls; and that functionality may work if you use the command line device loader programs.

Booting DOS in DOSBox is an effective solution. You shouldn't be concerned about speed, because you'll actually get more accurate speed with the overhead of real DOS. Device drivers will function correctly, but you shouldn't expect them to work if they're for hardware that isn't emulated.

Thx ripsaw8080!

According to Your answer it looks like only one possible solution is booting DOS. OK, why not, I try it.

But in this case one more question:
As I understood, in "booted" DOS I have to use only mounted images (via imgmount) - mounting of folders is not possible (via mount) - is it right?
This little bit limits sharing of data between Linux/Windows and DOSBox. Isn't here some workaround to simplify data sharing for such case?

Yes, you must use disk images to boot DOS; local folder mounts cannot be used with real DOS. In booted DOS the only workaround, if you want to call it that, for easy sharing of files with other systems is networking; and for that you'll need unofficial builds of DOSBox like MB6 or ykhwong's.

OK, thank You for all advices!