#136 JEMMEX - NTSTS network problem
Hello,
I write here because i don't know where to ask, if it's not the right place i apologize.
I'm trying to move our machines control program from MS-DOS 6.22 to FreeDos 1.1 to obtain because we have hardware components that are going in phase out.
So, to start studying how freedos works, i took the same hardware where i used MS-DOS and create a installation fo FreeDos with Rufus software, i updated the kernel and fixed autoexec.bat to get everything i need for my C application to run.
My hardware is an industrial panel PC with AMD GX3 and 1 GB Ram.
Everything worked fine in a couple of hours, except one thing that i can't stand:
i'm not able to get the network connection work properly.
I'm not sure about the reason and i ask you all if someone can help me to find a solution.
In my MSDOS system i had a config.sys list of devicehigh statements that worked fine, but in FreeDos looks like there is not enough memory to work.
The config.sys is like that
DEVICE=C:\locale\JEMMEX.EXE
DOS=HIGH,UMB
DEVICEHIGH=C:\NET\PROTMAN.DOS /i:C:\NET
DEVICEHIGH=C:\NET\DLSHELP.SYS
DEVICEHIGH=C:\NET\e100b.dos
DEVICEHIGH=C:\NET\NTSTS.DOS
BUFFERS=15,0
FILES=60
LASTDRIVE=Z
FCBS=4,0
STACKS=9,256
When the config arrives to the DEVICEHIGH=C:\NET\NTSTS.DOS it crashes immediately, or trying with various JEMMEX configurations i obtained that upper memory is not enough.
If with F8 i execute step by step the config statements, everything works except the ntsts.dos loading.
I need that driver works for my Intel 82551QM, and i see that it works on DOS so i'm pretty sure that probably it's only a extended memory issue that in MS-DOS 6.22 does not happen.
I know my english is not perfect, i hope that my explaination it's understandable.
Thanks for any idea for solve the problem.
I suggest you ask on one of the mailing lists (e.g. freedos-user) since very few read these bug trackers anymore.
Having said that, did any of the software explicitly say "Not enough memory"?
JEMMEX is basically just HIMEMX and JEMM386 combined. I see that you're trying to use UMBs, presumably because whatever needs lots of low (conventional) memory to be free. So you're sure that HIMEMX alone wouldn't work?? I would also personally recommend HIMEMX + JEMM386, just in case (and read the docs, you may have to add things like "X=TEST I=TEST").
Other than that, dunno. It might be a rare bug. It could even be a regression. Which kernel ("ver /r") are you using? Try a few others, and see if that helps:
https://sourceforge.net/projects/freedos/files/Kernel/
Thank you for the answer Anthony.
I'm using the 2041 kernel, i'll try with someone else.
By the way, i'm trying to use UMBs because, as you said, there is not enough memory to run everything. I tried JEMMEX, HIMEMX + JEMM386 with almost all the possible options but there are 2 possibilities:
1. when Config.sys reaches DEVICEHIGH=C:\NET\NTSTS.DOS the system crashes in very bad way, reboots or shows vary bad video problems
2. when DEVICEHIGH=C:\NET\NTSTS.DOS starts, it says that there is not enough upper memory.
This happen all the time, even if I change the order of my config.sys it happens only with NTSTS.
I look also with mi.exe but i didn't find anything strange or different from MS-DOS memory usage, so I'm starting think that is a NTSTS driver incompatibility with freedos (maybe some memory area used by ntsts and some kernel stuff? dunno...).
Now I'll try one last time to work it out with a different kernel, i'll try the 2039.
Last edit: Luca 2015-09-25
"when DEVICEHIGH=C:\NET\NTSTS.DOS starts, it says that there is not enough upper memory" ... Try changing to "DEVICE=" and see if that changes anything. (Doubt it, but ....)
Anyways, I still insist you get on one of the mailing lists, e.g. freedos-user, even temporarily, because there are several experts there that can explain and test this much better than I can. I think that's your best hope.
The difference is just that the memory lack is about conventional memory instead the upper one.
Nothing changes even with other kernel.
I think the problem is that the ntsts.dos is an IBM Warp component, maybe in FreeDos it creates some problem.
Now i try to move to mailing list.
Thanks for everything :)
This is not a bug, but more of set up help. This has been moved to the freedos-devel mailing list as of September 2015. I will close this bug.
Closed - bug's reporter sent his request to the freedos-devel mailing list instead.