Upper memory on notebook

Using UMBPCI the way you did is not a good idea if Jemm386 is to be installed as well. Since UMBPCI is loaded after Himem, it will install itself as an "UMB provider", which might be a problem if Jemm386 also has to supply UMBs (FreeDOS accepts ONE UMB provider only). Better is:

Upper memory on notebook

> This is on EDR-DOS_7.0.1.8> > DEVICE=D:\DOS\UMBPCI.SYS /I=D800-EFFF> DEVICE=C:\WINDOWS\HIMEM.SYS /TESTMEM:OFF /Q> DEVICE=D:\DOS\JEMM386.EXE X=D000-D3FF S=D800-DFFF FRAME=E000> > The upper memory is still 0kB, why? I removed PCMCIA ethernet card> Realtec and It was no way to change this situation

Please ask yourself a question: what do you expect us to do? Then try to imagine what kind of information might be needed to effectively do those things! At last, PROVIDE these informations!

Upper memory on notebook

Hi Japheth,
I would like to know why RAM on my notebooks are diferent from RAM standard PC? Why I can`t attempt to upper memory on notebooks, when I use UMBPCI or EMM386? Can I read somewhere how notebook memory works?
Thank you David

Upper memory on notebook

> Hi Japheth,> I would like to know why RAM on my notebooks are diferent from RAM> standard PC? Why I can`t attempt to upper memory on notebooks, when I use> UMBPCI or EMM386? Can I read somewhere how notebook memory works?> Thank you David

What are you you talking about? What does Jemm386 tell about its UMBs when you start it from the command line?

Upper memory on notebook

> What are you you talking about? What does Jemm386 tell about its UMBs when> you start it from the command line?

There is no difference betwen PC and notebook?
I started jemm386 from command line > jemm386.exe load < and then nothing strench, jemm386 displayed > jemm386 loadded < nothing more.
Then I started mem from command line and upper memory is 0kB ??
This stay on my notebooks with Datalight DOS and Enchanced DR-DOS, why?
When I use QEMM9 memory manager, then notebooks frozen

Upper memory on notebook

> I started jemm386 from command line > jemm386.exe load < and then nothing> strench, jemm386 displayed > jemm386 loadded < nothing more.> Then I started mem from command line and upper memory is 0kB ??> This stay on my notebooks with Datalight DOS and Enchanced DR-DOS, why?> When I use QEMM9 memory manager, then notebooks frozen

What is the BIOS and what are the settings? Some BIOSes require correct setting of OS, or OS type. Some perhaps are not friendly to DOS.

Upper memory on notebook

> Why not use CTMouse? Unlike the other one, it can unload (instead of> forcing a reboot).

Because mouse is sensitive and ctmouse crashes everytime durring boot to EDR-DOS. it is sufficient to small move or shock durring boot and EDR-DOS is stoped , sometime jemm386 calls report of ctmouse driver.

DR-DOS CONFIG.SYS settings

> Because mouse is sensitive and ctmouse crashes everytime durring boot to> EDR-DOS. it is sufficient to small move or shock durring boot and EDR-DOS> is stoped , sometime jemm386 calls report of ctmouse driver.

All I can think of is try loading it low (-w, IIRC). If that doesn't work, then never mind.

EDIT: There are actually three versions of CTmouse in circulation: 1.9 stable, 2.0 alpha, and 2.1 "non-EGA". I usually don't use a mouse in DOS, but I know that my (brief) tests have noticed that sometimes 1.9 works better when 2.0 won't work at all (or vice versa). So try another version instead and see if that helps:

Dunno. I just meant that UIDE should support both CD and DVD at the same time, no?

> > > HISTACKS> > > > Are you sure you need this? Some people avoid it like the plague unless> > you really need it.> > I understand what means stack on microchips, but here I don`t know its> function ...

I don't really know either (interrupt stack or some b.s.). That's why it's best to avoid it unless you know otherwise. Something about IBM PC compatibles need ... while others need .... (I can check DR-DOS' DOSBOOK.EXE later today for you, if you want.) Nevermind, I can boot FreeDOS in QEMU and use it's HELP.EXE:

> stacks> Adds stacks to handle hardware interrupts.
>> stacks=nn,nnn
>> Options
>> nn> the number of stacks in the range 8-64, and 0.
>> nnn> The size of each stack, in bytes, in the range of 32-512.

Bah, not very descriptive. Oh well, just avoid it unless some app needs it.

> > > HILASTDRIVE=Z> > > > I wouldn't set it so high unless you really need it (e.g. various SUBST> > drives). It wastes extra memory this way.> > I have drivers > A-M installed.

With the built-in history, you can't adjust it or unload it. Toddy is both a DOSKEY and HISTORY replacement, is open source, small, very configurable, and can be unloaded. That's why I like it. Same thing applies to DR-DOS' VDISK (use TDSK or SHSURDRV instead, they can be resized if you need the extra RAM). I find these more flexible options, but feel free to use whatever.

DR-DOS CONFIG.SYS settings

I will try it , ver.2.0a4 works but boot from autoxec.bat is dangerous

> Dunno. I just meant that UIDE should support both CD and DVD at the same> time, no?

OK, works I removed vide-cdd.sys from CONFIG.SYS

> I don't really know either (interrupt stack or some b.s.). That's why it's> best to avoid it unless you know otherwise. Something about IBM PC> compatibles need ... while others need .... (I can check DR-DOS'> DOSBOOK.EXE later today for you, if you want.) Nevermind, I can boot> FreeDOS in QEMU and use it's HELP.EXE:

> With the built-in history, you can't adjust it or unload it.> Toddy is both> a DOSKEY and HISTORY replacement, is open source, small, very configurable,> and can be unloaded. That's why I like it. Same thing applies to DR-DOS'> VDISK (use TDSK or SHSURDRV instead, they can be resized if you need the> extra RAM). I find these more flexible options, but feel free to use> whatever.

I removed HISTORY, but toddy is a little bit diferent from UNIX doskey style?

DR-DOS CONFIG.SYS settings

> > I don't really know either (interrupt stack or some b.s.). That's why> it's> > best to avoid it unless you know otherwise. Something about IBM PC> > compatibles need ... while others need .... (I can check DR-DOS'> > DOSBOOK.EXE later today for you, if you want.) Nevermind, I can boot> > FreeDOS in QEMU and use it's HELP.EXE:> > I removed it and I did`nt recognize a change.>

DR-DOS 7.03's DOSBOOK says something like this: "STACKS are 0,0 for IBM PCs and PC/XTs and 9,128 for others." I dunno if that means by default (probably) or something to manually set. Either way, it's probably not accurate for modern (> 486) computers. I can't remember exactly, but I think SETUP /A reports my P166 as a 486. So, it's woefully out of date (as some would say). Hence the reason that FreeDOS has replaced/improved a lot of functionality.

> I removed HISTORY, but toddy is a little bit diferent from UNIX doskey> style?>

* "toddy" brings up a menu of your cmdline history.
* "toddy /ml" shows you all your macros.
* "toddy blah=echo hello, $1 $t cls $s" says hello to parameter #1 while cls afterwards (the $s is parameter sink since parameters are passed to cls otherwise which probably won't work)
* "toddy /ow" writes your current setup (macros, etc.) to TODDY.CFG although you can also write to TODDY.COM itself

There's also adjustable history and macro size (among a billion other options). However, I've found that TODDY doesn't work w/ FreeDOS' FreeCOM (which has limited history support built-in by default). Oh well.

> Many thanks for prompter how to improve system files.

BTW, just to be ultra pedantic, here's two things I changed recently:

* CONFIG.SYS -- changed all REM to ; (for floppies, that could save a whole cluster, w00t!)
* CONFIG.SYS -- if you use SWITCH, apparently using ":himemumb" (HIMEM/UMBPCI) and ":himem" (HIMEM only) won't work b/c "goto himem" will always go to ":himemumb" (bug?), so you have to rename ":himem" to ":himem2" and then it'll work.

P.S. You can SET, ECHO, CHAIN, CPOS, GOSUB in CONFIG.SYS. In fact, w/ DR-DOS' COMMAND.COM, you can GOSUB, IF ... AND, IF ... OR, ECHOS, ECHOERR, etc. Of course, Lucho would tell you that 4DOS is much better.

DR-DOS CONFIG.SYS new settings + Arachne

One problem is occured after new settings in CONFIG.SYS, Now I can login to forum from Debian, and I have better comfort than in Arachne.
The problem concern Arachne, when I am openning INBOX, Arachne displays 'cannot allocate memory for reading of the index' the free dos memory is 141 [+] , why?, when I decrease space of low memory, then I have not displayed this message and openning INBOX normally.

The second question is about djgpp. I ask you once about symlinks emulated in djgpp library. When I want compile cdrtools package. I can create smake.exe but there are created no function links, I have to copy files.
There is not this situation on cygwin enviroment.

DR-DOS CONFIG.SYS new settings + Arachne

> One problem is occured after new settings in CONFIG.SYS, Now I can login> to forum from Debian, and I have better comfort than in Arachne.> The problem concern Arachne, when I am openning INBOX, Arachne displays> 'cannot allocate memory for reading of the index' the free dos memory is> 141 [+] , why?, when I decrease space of low memory, then I have not> displayed this message and openning INBOX normally.

So it has problems with too much low memory free? I dunno, probably a bug, report it.

> The second question is about djgpp. I ask you once about symlinks emulated> in djgpp library. When I want compile cdrtools package. I can create> smake.exe but there are created no function links, I have to copy files.> There is not this situation on cygwin enviroment.

No idea what you mean here (and I've never used cdrtools). Only DJGPP 2.04-compiled stuff supports symlinks of data (non-EXE) files. To make symbolic links that 2.04 understands, you have to use LN.EXE (dated Dec. 15, 2003) from the 2.04-compiled FIL41B.ZIP (under /beta/). That's all I know, sorry.

symlinks_djgpp

> So it has problems with too much low memory free? I dunno, probably a bug,> report it.

I wrote to Glenn about this

> No idea what you mean here (and I've never used cdrtools). Only DJGPP> 2.04-compiled stuff supports symlinks of data (non-EXE) files. To make> symbolic links that 2.04 understands, you have to use LN.EXE (dated Dec.> 15, 2003) from the 2.04-compiled> FIL41B.ZIP> (under /beta/). That's all I know, sorry.

Yes create ln -s XX YY works, but this message

!<symlink>../cdrecord/defaults.c
This is just a text to force symlink file to be 510 bytes long. Do not delete it nor spaces following it.

in file defaults.c explain what??

This is an example, files 510 bytes long are there a lots of, they should be replace unix symlinks in djgpp?
This is what I mean.

symlinks_djgpp

> Yes create ln -s XX YY works, but this message > > !<symlink>../cdrecord/defaults.c> This is just a text to force symlink file to be 510 bytes long. Do not> delete it nor spaces following it. > > in file defaults.c explain what??> > This is an example, files 510 bytes long are there a lots of, they should> be replace unix symlinks in djgpp?> This is what I mean.

I hope this explains it (as best I understand, anyways):

For instance, I use an editor called TDE. It is compiled for DOS twice (16-bit, 32-bit) and Windows. However, the 32-bit build was compiled via DJGPP 2.03p2. So, I have to rebuild w/ DJGPP 2.04 (e.g. GCC 4.2.2 in this instance). Done! Now, I do a "ln -s macro.c david.c", and "tdep david.c" (with the new 2.04-compiled TDE), and it actually ends up opening macro.c instead. So, I type "david" in the "david.c" file, save, close. Now open macro.c, and it miraculously says "david" at the top! See?

symlinks_djgpp

> I hope this explains it (as best I understand, anyways):> > For instance, I use an editor called TDE. It is compiled for DOS twice> (16-bit, 32-bit) and Windows. However, the 32-bit build was compiled via> DJGPP 2.03p2. So, I have to rebuild w/ DJGPP 2.04 (e.g. GCC 4.2.2 in this> instance). Done! Now, I do a "ln -s macro.c david.c", and "tdep david.c"> (with the new 2.04-compiled TDE), and it actually ends up opening macro.c> instead. So, I type "david" in the "david.c" file, save, close. Now open> macro.c, and it miraculously says "david" at the top! See?

many thanks, I will create and test symlink according to your directions