China DOS Union

Why is it that after DOS boots, if I type
device protman.dos /i:\DRV
it shows IBM protocol manager Version 2.1
and then it just stops there without moving at all

But if I load it directly in config.sys then everything is normal...

[ Last edited by gongsheng1980 on 2005-10-31 at 22:47 ]

There is no problem with the location of the protocol.ini file

So frustrating

Re gongsheng1980:

Then we need to know your config.sys and autoexec.bat configuration environment. For now, you can do the following test: first back up both files, then delete everything below protman.dos in config.sys, and also delete autoexec.bat. After rebooting, run device protman.dos /i:\DRV again.

If the problem still remains, then it may be a compatibility problem with device, and you can try using some other driver-loading tool; if the problem disappears, then it must be caused by some program in config.sys or autoexec.bat. Just continue using the process of elimination and test step by step.


——————————————— Edited by willsort ———————————————
Original title: Moderator, help, it's urgent, waiting online
For the convenience of all users browsing and moderator management, please note that the title should be a refinement and summary of the content
——————————————— Edited by willsort ———————————————

Thanks to the moderator for replying.
I've already tried it, and the problem is still there.
What other driver-loading tools are there?

What other driver-loading tools are there?

Re gongsheng1980:

You can try devlod.com, but I don't have it here, you can Google for it. But I think this problem may be related to memory configuration; I'm only offering this suggestion for reference.

Thanks

Where can I find materials related to memory configuration?

I want LOADSYS.EXE

I tried using DEVLOAD
and it showed IBM protocol manager version 2.1
driver staying resident
I feel that the latter sentence is the key
Could one of you experts translate it for me? I'd be very grateful

Re gongsheng1980:

That English sentence means the “driver is staying resident” in memory. Looking at it this way, it really may be a memory configuration problem. You can focus on testing how the driver behaves after being loaded from the command line with/without emm386 loaded. But it may also be a limitation of the driver itself, causing certain problems when loaded from the command line. In that case, you'll need to try a different version of the driver.

Thanks, moderator!
I'd already tested that EMM386 earlier! It has nothing to do with EMM386!
It should be a limitation of the driver itself.
I'll go look for another version of PROTMAN.DOS and try it!
THKS~~~

There isn't any documentation about PROTMAN.DOS

I have the same confusion; if you found out, please let me know.

This problem is very simple, pay attention to the version of protman.dos