[Freedos-devel] confused by NLS-settings
Dear developer list, could anyone please help me out with a config.sys/autoexec.bat implementation of NLS-specific settings? I'm horribly confused by how startup files should look, as to my knowledge we've got the following: * COUNTRY in config.sys (harddisk installation) versus no such setting (bootdisks, as the file takes up too much space) * stable kernels (no COUNTRY support) versus unstable kernels (experimental COUNTRY support) * official MSDOS way of codepage setting versus FreeDOS adhoc settings (NLSFUNC related?) This involves the following: * COUNTRY= (config.sys, COUNTRY.SYS / COUNTRY2.SYS / COUNTRY3.SYS) * DISPLAY (a TSR by Aitor, versus device driver in MSDOS) * NLSFUNC (with optional COUNTRY support, but only if not listed in config.sys yet?) * MODE versus MODECON versus different configurations whether or not COUNTRY= is set? * CHCP (internal command to FreeCOM) * KEYB (and CPI/CPX files) I'd like to add above in a working configuration for a FreeDOS 1.1 (work-in-progress) including kernel 2040 (stable, with support for nlsfunc/country) but so many settings to consider it's hurting my head. Along with that there's ofcourse a few more annoying issues: * DEVLOAD /H (devload 3.21) bails out entirely of loading a device driver in no-UMB environments. I dislike having to make 2 or more entries for simply loading a CD driver. Non-optimal result thus for options 1 and 2 * EDIT 0.9a prints its version and DFLAT banner at every invocation. * FreeCOM unfortunately allows environment variables to end with empty spaces instead of stripping them. * I'm not sure which version of SHARE to include, there's quite a few of them floating around the internet Bernd (FD)CONFIG.SYS so far: !COUNTRY=001,437,C:\FDOS\BIN\COUNTRY.SYS !SET DOSDIR=C:\FDOS !LASTDRIVE=Z !BUFFERS=20 !FILES=40 !MENUCOLOR=7,0 MENUDEFAULT=1,5 MENU 1 - Load FreeDOS with JEMMEX, no EMS (most UMBs), max RAM free MENU 2 - Load FreeDOS with EMM386+EMS and SHARE MENU 3 - Load FreeDOS including HIMEM XMS-memory driver MENU 4 - Load FreeDOS without drivers 123?DOS=HIGH 12?DOS=UMB 12?DOSDATA=UMB 1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST 2?DEVICE=C:\FDOS\BIN\HIMEMX.EXE 2?DEVICE=C:\FDOS\BIN\JEMM386.EXE X=TEST I=B000-B7FF 3?DEVICE=C:\FDOS\BIN\XMGR.SYS 3?SHELL=C:\FDOS\BIN\4DOS.COM C:\FDOS\BIN /E:1024 /P:C:\AUTOEXEC.BAT 4?SHELL=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT 12?SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT Autoexec.bat so far: @echo off SET LANG=EN SET PATH=%dosdir%\BIN SET NLSPATH=%dosdir%\NLS SET HELPPATH=%dosdir%\HELP SET TEMP=%dosdir%\TEMP SET TMP=%dosdir%\TEMP SET WATTCP.CFG=%dosdir% SET MTCPCFG=%dosdir%\MTCP.CFG SET BLASTER=A220 I5 D1 H5 P330 SET DIRCMD=/P /OGN /4 if %config%==4 goto end DOSLFN SHSUCDX /QQ /D3 IF EXIST FDBOOTCD.ISO LH SHSUCDHD /Q /F:FDBOOTCD.ISO LH FDAPM APMDOS if %config%==2 LH SHARE MOUSE DEVLOAD /Q %dosdir%\BIN\UIDE.SYS /D:FDCD0001 /S5 ShsuCDX /QQ /~ /D:?SHSU-CDH /D:?FDCD0001 /D:?FDCD0002 /D:?FDCD0003 goto end :end MEM /C /N if not %config%== SHSUCDX /D SET CFGFILE=C:\FDCONFIG.SYS SET AUTOFILE=%0 alias reboot=fdapm warmboot alias halt=fdapm poweroff echo Done processing startup files %cfgfile% and %0 echo Type HELP to get support on commands and navigation echo. echo Welcome to the FreeDOS 1.1 operating system (http://www.freedos.org) -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] confused by NLS-settings
Hi, quick reply from memory, others can answer too of course, On Thu, Jun 30, 2011 at 2:01 AM, Bernd Blaauw bbla...@home.nl wrote: Dear developer list, could anyone please help me out with a config.sys/autoexec.bat implementation of NLS-specific settings? I'm horribly confused by how startup files should look, as to my knowledge we've got the following: * COUNTRY in config.sys (harddisk installation) versus no such setting (bootdisks, as the file takes up too much space) COUNTRY.SYS isn't needed for DISPLAY-only stuff, e.g. codepages on screen, nor for KEYB either. It's only other stuff (collate tables, y/n), I think. * stable kernels (no COUNTRY support) versus unstable kernels (experimental COUNTRY support) 2037, 2039 are the only ones supported (not counting 2040, which is unreleased). * official MSDOS way of codepage setting versus FreeDOS adhoc settings (NLSFUNC related?) It's all ad hoc! MS-DOS was far from perfect either. And, well, let's just say that MS-DOS is more limited than FreeDOS (esp. re: codepages, thanks to Henrique). This involves the following: * COUNTRY= (config.sys, COUNTRY.SYS / COUNTRY2.SYS / COUNTRY3.SYS) Eh? I'm only actively aware of COUNTRY.SYS, not any others. Ask Eduardo Casino (I think) for more info. * DISPLAY (a TSR by Aitor, versus device driver in MSDOS) The only difference here is it lacks certain int 21h calls, no huge problem. Also, FreeDOS may not (much, if at all) support PRINTER.SYS. Otherwise, it shouldn't matter (much). * NLSFUNC (with optional COUNTRY support, but only if not listed in config.sys yet?) I don't think CONFIG.SYS' COUNTRY= affects NLSFUNC. You still need to run NLSFUNC at runtime (I think) to activate the collate tables, y/n, currency, time, etc. * MODE versus MODECON versus different configurations whether or not COUNTRY= is set? Isn't MODECON deprecated / unnecessary?? * CHCP (internal command to FreeCOM) This was supposed to (I think) unify all the various subsystems (PRINTER, DISPLAY, KEYB) into one overall system codepage. Some of these subsystems (e.g. KEYB) try to align with DISPLAY and can stop you independently changing the codepage if no layout is supported (for example). My personal example (Esperanto), for my amusement only, it only works with DISPLAY and KEYB (for which I'm grateful!), not CHCP nor COUNTRY.SYS (lacking explicit E-o support, natch, which I don't really need anyways). * KEYB (and CPI/CPX files) KEYB uses KEYBOARD, KEYBRD2, KEYBRD3.SYS (library) files. CPX is just a (UPX-)compressed CPI file. I'd like to add above in a working configuration for a FreeDOS 1.1 (work-in-progress) including kernel 2040 (stable, with support for nlsfunc/country) but so many settings to consider it's hurting my head. Well, what explicit languages are you trying to support? Honestly, if you don't care about full NLS, you don't need everything and the kitchen sink. Latin-1 (850 or 819) is pretty much all you need for the common folk. (I'm not trying to marginalize anyone, just saying it's easier to support a subset.) Really, just including EGA.CPX alone (and without *.CPX) is probably sufficient for basic needs. Along with that there's ofcourse a few more annoying issues: * DEVLOAD /H (devload 3.21) bails out entirely of loading a device driver in no-UMB environments. I dislike having to make 2 or more entries for simply loading a CD driver. Non-optimal result thus for options 1 and 2 Kinda a hack, ain't it? Just don't use DEVLOAD at all unless really required. (That may not be what you want to hear, though.) It's not meant to be used in 100% of cases, IMHO. * EDIT 0.9a prints its version and DFLAT banner at every invocation. Recompile? :-) Or just include a different editor (I'd cram TDE, if possible, or EZEDIT if not). * FreeCOM unfortunately allows environment variables to end with empty spaces instead of stripping them. You mean the name or contents? set BLAH=name TDE can (optionally) trim trailing spaces upon save, if that bothers your .BATs. ;-) Or just use:sed -e s/ *$// myfile.bat myfile.new * I'm not sure which version of SHARE to include, there's quite a few of them floating around the internet It's supposedly mostly non-functional anyways, doesn't fully support MS SHARE. I think Japheth had a hacked one for some old Win 3.x Office tools (Word, etc). Other than that, I don't know of any huge reason for it (and never use it personally). (more inline comments below) (FD)CONFIG.SYS so far: !COUNTRY=001,437,C:\FDOS\BIN\COUNTRY.SYS I don't think you need to specify this COUNTRY line at all for 437 (U.S.). !LASTDRIVE=Z Too many unless you're really using them all (or relying on hardcoded drive values). I'd suggest P as a compromise. !BUFFERS=20 Too many and unnecessary ... but only if using UIDE. Otherwise fine. !FILES=40 Is that enough? Should be for most stuff, but 80 would be safer (in theory). 1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST Should
Re: [Freedos-devel] confused by NLS-settings
I will try to respond better when I'm home. Kernel 2040 is released but not yet announced. Use share country that is with kernel. I believe I checked all versions floating around a year or so ago have latest share with kernel (I need to verify both SVN versions). I don't know much about using NLS support as I always used default codepages. Jeremy -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] confused by NLS-settings
Op 29-6-2011 23:07, Rugxulo schreef: COUNTRY.SYS isn't needed for DISPLAY-only stuff, e.g. codepages on screen, nor for KEYB either. It's only other stuff (collate tables, y/n), I think. Ah yes thanks for mentioning that. I'd like kinda 'full' support. 2037, 2039 are the only ones supported (not counting 2040, which is unreleased). You might want to check the kernel list archives. Jim seems to be on holiday so nothing listed yet. Don't know about Sourceforge files. This involves the following: * COUNTRY= (config.sys, COUNTRY.SYS / COUNTRY2.SYS / COUNTRY3.SYS) Eh? I'm only actively aware of COUNTRY.SYS, not any others. Ask Eduardo Casino (I think) for more info. You might be right, maybe I'm confusing country.sys with keyboard.sys. Oops http://eduardocasino.es/index.php?option=com_contentview=categorylayout=blogid=4Itemid=9 is on Eduardo's site, not sure this made it into 2040 or not. The only difference here is it lacks certain int 21h calls, no huge problem. Also, FreeDOS may not (much, if at all) support PRINTER.SYS. Otherwise, it shouldn't matter (much). I remember DISPLAY 2.0 being troublesome with regard to UMBs, but that was years ago. * NLSFUNC (with optional COUNTRY support, but only if not listed in config.sys yet?) I don't think CONFIG.SYS' COUNTRY= affects NLSFUNC. You still need to run NLSFUNC at runtime (I think) to activate the collate tables, y/n, currency, time, etc. NLSFUNC seems to be able to take COUNTRY.SYS file as an argument/parameter Isn't MODECON deprecated / unnecessary?? Guess so, but that's what my entire help request is about. Well, what explicit languages are you trying to support? Honestly, if you don't care about full NLS, you don't need everything and the kitchen sink. Latin-1 (850 or 819) is pretty much all you need for the common folk. (I'm not trying to marginalize anyone, just saying it's easier to support a subset.) Really, just including EGA.CPX alone (and without *.CPX) is probably sufficient for basic needs. It's easy enough to add full support once someone's able to give me a fully implemented specific configuration. http://support.microsoft.com/kb/60080 seems to list a specific example, but that's tied to MSDOS and I'm not sure it's complete. Thought Win98 bootdisks had some codepage stuff also but bootdisk.com website only shows modified file images. Kinda a hack, ain't it? Just don't use DEVLOAD at all unless really required. (That may not be what you want to hear, though.) It's not meant to be used in 100% of cases, IMHO. Fair enough, but I like the flexibility. The loading works, but the /H option appears to have been modified from use UMBs if available, otherwise still load in normal memory into a use UMBs if available, otherwise refuse to load at all Changing it to 0123?DEVICEHIGH= should be a solution yes, as that won't refuse to load when no UMBs (only give a huge warning) * EDIT 0.9a prints its version and DFLAT banner at every invocation. Recompile? :-) Or just include a different editor (I'd cram TDE, if possible, or EZEDIT if not). Pretty stuck at using EDIT as a baseline replacement of MS EDIT. Other programs always welcome as extension. You mean the name or contents? set BLAH=name TDE can (optionally) trim trailing spaces upon save, if that bothers your .BATs. ;-) Or just use: sed -e s/ *$// myfile.bat myfile.new Contents indeed. I've thus got a batchfile to fix somewhere. * I'm not sure which version of SHARE to include, there's quite a few of them floating around the internet It's supposedly mostly non-functional anyways, doesn't fully support MS SHARE. I think Japheth had a hacked one for some old Win 3.x Office tools (Word, etc). Other than that, I don't know of any huge reason for it (and never use it personally). Not even sure what SHARE was used for, was it MS-Client (TCP/IP) and Windows 3, to gain multiple accesses to same file by locking? (FD)CONFIG.SYS so far: !COUNTRY=001,437,C:\FDOS\BIN\COUNTRY.SYS I don't think you need to specify this COUNTRY line at all for 437 (U.S.). I know, just want a full implementation/example so people can modify it themselves if desired so, without finding syntax and dependencies. Is that enough? Should be for most stuff, but 80 would be safer (in theory). Worth considering, I'd have to check the memory increase. If stuff goes into HMA anyway, I don't mind :) 1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST Should probably have an ultra-safe choice somewhere in here: JEMMEX NORAM NOEMS X=TEST I=TEST The docs list a different safer value, probably preferable, but I don't have it here. I'll read up on those parameters, thanks for your info. (easier) set TMP=%TEMP% you're right, thanks. This should be echoed at bootup, IMHO, so that people know what it's default set to (in case of troubles). echo. echo %%BLASTER%% = %BLASTER% echo. worthwile considering. Perhaps I should even add DHCP and packet
Re: [Freedos-devel] confused by NLS-settings
Hi again, On Thu, Jun 30, 2011 at 5:46 AM, Bernd Blaauw bbla...@home.nl wrote: Op 29-6-2011 23:07, Rugxulo schreef: 2037, 2039 are the only ones supported (not counting 2040, which is unreleased). You might want to check the kernel list archives. Jim seems to be on holiday so nothing listed yet. Don't know about Sourceforge files. Well, I don't know the entire list, of course. And apparently 2040 is out! But I haven't tested it yet (obviously??). The only difference here is it lacks certain int 21h calls, no huge problem. Also, FreeDOS may not (much, if at all) support PRINTER.SYS. Otherwise, it shouldn't matter (much). I remember DISPLAY 2.0 being troublesome with regard to UMBs, but that was years ago. It still needs a lot of unnecessary UMB room free to load there, e.g. 64 kb or some fairly high amount. And you may even have to explicitly mention it. I forget exactly and always (I think) loaded it low. Well, I'd have to check * NLSFUNC (with optional COUNTRY support, but only if not listed in config.sys yet?) I don't think CONFIG.SYS' COUNTRY= affects NLSFUNC. You still need to run NLSFUNC at runtime (I think) to activate the collate tables, y/n, currency, time, etc. NLSFUNC seems to be able to take COUNTRY.SYS file as an argument/parameter Yes, but it's hardcoded to a specific DISPLAY version, I think. Like I said, I never heavily used it (COUNTRY + NLSFUNC) since it lacked support for 853 anyways. Isn't MODECON deprecated / unnecessary?? Guess so, but that's what my entire help request is about. Well, you'll have to wait for Eric's reply, then. It's easy enough to add full support once someone's able to give me a fully implemented specific configuration. http://support.microsoft.com/kb/60080 seems to list a specific example, but that's tied to MSDOS and I'm not sure it's complete. Thought Win98 bootdisks had some codepage stuff also but bootdisk.com website only shows modified file images. No offense to anybody, but even I know MS i18n codepage support is a joke. They never even bothered supporting Latins 1-4. I did make a bootdisk a while back (year ago?) intending to demo the codepage stuff with FreeDOS, but I never finished it (and nobody else seemed interested). I could (hopefully) dig it up if you're interested. * EDIT 0.9a prints its version and DFLAT banner at every invocation. Recompile? :-) Or just include a different editor (I'd cram TDE, if possible, or EZEDIT if not). Pretty stuck at using EDIT as a baseline replacement of MS EDIT. Other programs always welcome as extension. Well, the 64 kb file limit was a bit of a put-off for me, personally. Maybe good for average use, I guess (just not my favorite preference). You mean the name or contents? set BLAH=name TDE can (optionally) trim trailing spaces upon save, if that bothers your .BATs. ;-) Or just use: sed -e s/ *$// myfile.bat myfile.new Contents indeed. I've thus got a batchfile to fix somewhere. sed -n l myfile.bat should show various escapes. Or you could do this: sed -n -e / *$/= myfile.bat (that's two blanks there, one is optional, some seds confuse \+ with +) * I'm not sure which version of SHARE to include, there's quite a few of them floating around the internet It's supposedly mostly non-functional anyways, doesn't fully support MS SHARE. I think Japheth had a hacked one for some old Win 3.x Office tools (Word, etc). Other than that, I don't know of any huge reason for it (and never use it personally). Not even sure what SHARE was used for, was it MS-Client (TCP/IP) and Windows 3, to gain multiple accesses to same file by locking? It was something dumb like that, I dunno. ;-) (FD)CONFIG.SYS so far: !COUNTRY=001,437,C:\FDOS\BIN\COUNTRY.SYS I don't think you need to specify this COUNTRY line at all for 437 (U.S.). I know, just want a full implementation/example so people can modify it themselves if desired so, without finding syntax and dependencies. I think we need more real i18n testers. But they are hard to find. :-(( This should be echoed at bootup, IMHO, so that people know what it's default set to (in case of troubles). echo. echo %%BLASTER%% = %BLASTER% echo. worthwile considering. Perhaps I should even add DHCP and packet driver to the standard setup. Getting complicated then though. This is just my personal opinion, but if you want to go that route, the best (IMHO) path would be to include suitable ones for QEMU (NE2000?) and VirtualBox (AMDPD). Though I'm not 100% sure those work as I haven't tried recently, but I've heard they do at least. SET DIRCMD=/P /OGN /4 set DIRCMD=/P /OGN /4 /LFN lfnfor on lfnfor complete on Are these FreeCOM 0.84pl2 abilities? I've used many versions, some had LFN, other had different abilities (/Z for errorlevel reporting for example). Confusing :) Only 0.84 has LFN, which (according to Eric) was Blair's work, which wasn't checked too closely, hence they still were careful about using 0.82 a
Re: [Freedos-devel] confused by NLS-settings
I live in the USA, so don't have a need for any alternative language settings in my everyday life. But, I have messed around with a lot of keyboard layouts and code pages to test some of my keyboard related programs over the years, so I'll let you know what I've discovered. Nearly all of my experience is with MS-DOS, not FreeDOS, so take it with a grain of salt. COUNTRY.SYS isn't needed for DISPLAY-only stuff, e.g. codepages on screen, nor for KEYB either. It's only other stuff (collate tables, y/n), I think. I think I agree here. The main things I think people care about are Code Pages (which I've always manipulated with MODE CON CODEPAGE PREPARE and MODE CON CODEPAGE SELECT) and keyboard layouts (KEYB). Most of the other stuff (NLSFUNC, COUNTRY, etc.) are mostly for sorting/collation and currency/number/time display. But, even this is limited to DOS itself, or programs that call DOS services to provide this functionality. I'm not sure how many programs would call DOS services to do this kind of thing for them, anyway -- a serious program would likely do all of this internally and not depend on the user to enter the appropriate settings in CONFIG.SYS or AUTOEXEC.BAT. Again, because I live in the USA, this has never been a concern for me, so I can't say for certain. Also, FreeDOS may not (much, if at all) support PRINTER.SYS. Otherwise, it shouldn't matter (much). IIRC, PRINTER.SYS only supported a few different kinds of printers anyway, and was relatively useless even back in the day (at least for me). !LASTDRIVE=Z Too many unless you're really using them all (or relying on hardcoded drive values). I'd suggest P as a compromise. I personally always use LASTDRIVE=Z. This makes it much easier to manipulate things the way I want to on the fly when messing with USB drives or using SUBST or ASSIGN to create temporary drive letters. If you don't make LASTDRIVE big enough, you can end up needing to edit CONFIG.SYS and reboot -- really annoying. 1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST Should probably have an ultra-safe choice somewhere in here: JEMMEX NORAM NOEMS X=TEST I=TEST If you are trying to make a universal disk that will work on any machine, you need to be careful about using JEMMEX. It doesn't work on every machine. I have a Sony laptop that JEMM refuses to install on, no matter which configuration options are chosen. MS HIMEM.SYS+EMM386.EXE installs just fine on the same computer. alias reboot=fdapm warmboot alias halt=fdapm poweroff I always put all aliases in a single file, e.g. MYALIAS.BAT. Then, in autoexec, I could say if exist MYALIAS.BAT call MYALIAS.BAT. And of course alias myalias=edit myalias.bat for easy tweaking. On the same machine (Sony laptop), FDAPM doesn't work at all because the BIOS doesn't have APM (only ACPI). So, if you're trying to create a universal disk, you probably shouldn't use FDAPM at all. -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] [Freedos-user] New kernel
Op 30-6-2011 1:29, Santiago Almenara schreef: Thanks Eric! I'll try 2040 instead of 2030. Just for everyone's information, I'm still able to hit a double BAD FAT INFO - Run CHKDSK error message from the kernel occasionally The only situation in which I sometimes am able to trigger that, is by booting from USB flash drive (at 1.1 speeds, bah) and then deleting a 8MB (or more) ISO file from root of that directory. In addition to that the USB flashdrive and keyboard disappear, forcing a system reboot through the case's hardware button. Not narrowed down this situation, but wasn't using USB drivers. However, for general use 2040 should be perfectly safe as floppy and harddisk controllers aren't such a mess as legacy bios emulation. -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] FreeDOS web site updates
I wanted to share some behind the scenes changes on the FreeDOS web site. You may not have noticed, but I've cleaned up many of the web pages, including some updates and new features. The latest changes include better support for mobile web browsers. In the past, if you used a mobile device to visit the FreeDOS web site, you automatically saw a mobile-enabled page. In the last few weeks, I've trimmed what appears on the mobile version, so pages will load faster. For example, news items on the front page don't show full details when viewed on a mobile device - you can click on the link to read the complete news item. That's great on a mobile phone or similar device, but for larger devices (iPad?) on a Wi-Fi connection, you may prefer to see the regular, full-size web site. There's now a link at the bottom of each page for view full site (or view mobile site if you're on the full-size version.) This sets a cookie in your web browser for 1 hour, to change your web site preference. You can change this manually by visiting http://www.freedos.org/?m=1 to set the mobile view, or http://www.freedos.org/?m=0 for the full-version web site (handy for bookmarks.) -jh -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] confused by NLS-settings
Hi, On Wed, Jun 29, 2011 at 5:37 PM, Bret Johnson bretj...@juno.com wrote: I live in the USA, so don't have a need for any alternative language settings in my everyday life. Ditto. But we're behind the times. I think only 24% of the world (or some such small number) is monolingual. Everybody else speaks more than one. Most of the other stuff (NLSFUNC, COUNTRY, etc.) are mostly for sorting/collation and currency/number/time display. But, even this is limited to DOS itself, or programs that call DOS services to provide this functionality. I'm not sure how many programs would call DOS services to do this kind of thing for them, There aren't that many (relatively), but I'd be wrong to say none. Especially European users seem to do it (more) often. One example offhand is FASMD, though I can't remember exactly what for (perhaps 8-bit filename capitalization in the file open browser). Maybe some others (NDN?) do also, but again, like you, I never tested too heavily for default reasons (English only). anyway -- a serious program would likely do all of this internally and not depend on the user to enter the appropriate settings in CONFIG.SYS or AUTOEXEC.BAT. Correct, e.g. TDE or Mined or GNU Emacs. IIRC, PRINTER.SYS only supported a few different kinds of printers anyway, and was relatively useless even back in the day (at least for me). Well, I can't remember if it even exists! And, let's be honest, printers are a pain even at the best of times. So me holding out blind hope that FreeDOS will ever work (for me), in this particular hardware area, is not going to happen. Eric (Auer) probably knows more (or maybe Jim Tabor). I personally always use LASTDRIVE=Z. I know, but it wastes a (tiny?) bit of extra RAM that way. Besides, who needs more than P?? Besides you (in heavy testing), of course. ;-) If you don't make LASTDRIVE big enough, you can end up needing to edit CONFIG.SYS and reboot -- really annoying. JEMM386 FASTBOOT:-) If you are trying to make a universal disk that will work on any machine, you need to be careful about using JEMMEX. It doesn't work on every machine. I have a Sony laptop that JEMM refuses to install on, no matter which configuration options are chosen. MS HIMEM.SYS+EMM386.EXE installs just fine on the same computer. Well, we'd *all* have to test all our dopey machines (even virtual). Or you'd have to make sure it can be overriden (F8, so don't do SWITCHES=/F /N). We still never officially patched HIMEMX to 3.33 with the jmp $+2 patch for old 386s. :-( alias reboot=fdapm warmboot alias halt=fdapm poweroff On the same machine (Sony laptop), FDAPM doesn't work at all because the BIOS doesn't have APM (only ACPI). So, if you're trying to create a universal disk, you probably shouldn't use FDAPM at all. My old (dead) laptop didn't work with CTmouse. I think we all know that hardware is flaky and incompatible, sometimes. Just be sure not to use SWITCHES=/F /N, and it'll be fine, IMHO. Or alternately include a (very lean, spartan) setup as #1 choice or whatever. At least then somebody can reboot just to see if it'll work then if it didn't otherwise. -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] confused by NLS-settings
Hi Bret, Em 29/06/2011 18:37, Bret Johnson escreveu: I live in the USA, so don't have a need for any alternative language settings in my everyday life. But, I have messed around with a lot of keyboard layouts and code pages to test some of my keyboard related programs over the years, so I'll let you know what I've discovered. Nearly all of my experience is with MS-DOS, not FreeDOS, so take it with a grain of salt. you say you've messed around with a lot of keyboard layouts and codepages. That called my attention. Would you mind telling me which codepages you tried? I'm particularly looking for cp854 and cp776. I just know that they existed but I never found their description. If necessary, I could send you a list of all codepages I know and you could check it against your list. Thanks, Henrique -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] confused by NLS-settings
Hi Ruĝulo, No offense to anybody, but even I know MS i18n codepage support is a joke. They never even bothered supporting Latins 1-4. I did make a bootdisk a while back (year ago?) intending to demo the codepage stuff with FreeDOS, but I never finished it (and nobody else seemed interested). I could (hopefully) dig it up if you're interested. How did that demo work? Henrique -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] confused by NLS-settings
Hi, On Wed, Jun 29, 2011 at 9:10 PM, Henrique Peron hpe...@terra.com.br wrote: Well, what explicit languages are you trying to support? Honestly, if you don't care about full NLS, you don't need everything and the kitchen sink. Latin-1 (850 or 819) is pretty much all you need for the common folk. Cp819, along with almost all other ISO 8859-x codepages, has never been released; I know. :-) But Kosta Kostis' old ISOLATIN.CPI works in a pinch. I've prepared them a long time ago but I really don't know whether is there any interest on ISO 8859 codepages. Probably not much. And I don't use i18n in FreeDOS very much these days. :-/ I have also prepared, a long time ago, MAC OS and Windows codepages. Should (all | most) of you tell me that support for them is interesting for FreeDOS, I would work on distinct sets of KEYB*.SYS keyboard layout library files. Well, as you've previously said, things like 853 vs. 913, we already have 853 (DISPLAY, KEYB), big thanks to you, which (unlike 913) additionally supports box chars. 913 (Latin-3) is only good for ultra compatibility, but it's easy (for me) to translate a text (semi-)manually if needed. In short, sure, it'd be cool, but it's probably not worth you wasting too much time on it unless you really, really wanted to. I don't want to overburden you. :-(It's a volunteer project, so feel free to work on whatever you want. -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] confused by NLS-settings
Saluton, scipovanto!:-) On Wed, Jun 29, 2011 at 9:50 PM, Henrique Peron hpe...@terra.com.br wrote: Hi Ruĝulo, No offense to anybody, but even I know MS i18n codepage support is a joke. They never even bothered supporting Latins 1-4. I did make a bootdisk a while back (year ago?) intending to demo the codepage stuff with FreeDOS, but I never finished it (and nobody else seemed interested). I could (hopefully) dig it up if you're interested. How did that demo work? How else? Just crammed a bunch of stuff on floppy, basically, trying to make as useful a disk as possible, esp. catering to i18n (KEYB, DISPLAY, COUNTRY, Mined, Blocek, Foxtype) while still being overall useful in general for DOS. I never finished it, and nobody whined. Plus I'd have to vaguely update it and gather all sources (ugh). But I can dig it up (maybe) if desired. -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] confused by NLS-settings
Saluton denove, On Wed, Jun 29, 2011 at 10:16 PM, Rugxulo rugx...@gmail.com wrote: Saluton, scipovanto! :-) On Wed, Jun 29, 2011 at 9:50 PM, Henrique Peron hpe...@terra.com.br wrote: Hi Ruĝulo, I did make a bootdisk a while back (year ago?) intending to demo the codepage stuff with FreeDOS, but I never finished it (and nobody else seemed interested). I could (hopefully) dig it up if you're interested. How did that demo work? How else? Just crammed a bunch of stuff on floppy, basically, trying to make as useful a disk as possible, esp. catering to i18n (KEYB, DISPLAY, COUNTRY, Mined, Blocek, Foxtype) while still being overall useful in general for DOS. I never finished it, and nobody whined. Plus I'd have to vaguely update it and gather all sources (ugh). But I can dig it up (maybe) if desired. At risk of boring everyone (or even accidentally spamming the group), I'll post my AUTOEXEC.BAT and CONFIG.SYS here, as well as ls -lR contents of the disk itself (which I just dumped via PuppyLinux, in case you're wondering why it says root everywhere). I doubt anybody cares, but perhaps Bernd will see what settings he's looking for. (CONFIG.SYS): MENU 1 NLS: Greek MENU 2 *** NLS: Esperanto *** MENU 3 no NLS extras loaded MENUDEFAULT=2,20 REM SWITCHES=/F /N 12?IDLEHALT=1 12?KEYBUF=0x120,0x1d0 REM this needs 286+ (XMSv2 only) REM DEVICE=A:\FDOS\FDXMS286.SYS REM 386+ (XMSv3) 123?DEVICE=A:\UTILS\XMGR.SYS REM 5 MB cache (386+) REM DEVICE=A:\UTILS\UIDE.SYS /S5 /N2 123?DEVICE=A:\UTILS\UIDE.SYS /S5 /D:FDCD000 /C0 123?DEVICE=A:\FDOS\NANSI.SYS 123?DEVICE=A:\FDOS\MORESYS.SYS 123?SHELL=A:\COMMAND.COM A:\ /E:1024 /P 1?COUNTRY=030,869,A:\FDOS\COUNTRY.SYS 2?COUNTRY=1,,A:\FDOS\COUNTRY.SYS 123?DOS=HIGH,UMB 123?BUFFERS=10 123?FILES=40 123?LASTDRIVE=G (AUTOEXEC.BAT): @echo off if %CONFIG%==1 set DEFAULT=869 if %CONFIG%==2 set DEFAULT=853 alias autoexec=ezedit a:\autoexec.bat alias config=ezedit a:\config.sys alias 7za=7zdecode alias 7zdec=7zdecode alias p7zip=7zdecode alias gunzip=untar -d alias grep=xgrep alias uname=ver /r alias mined=mined386 alias attrib=attr alias edit=ezedit alias cpuid=cpulevel alias fdisk=xfdisk alias m=mem /c /p REM (must have soundcard hooked up to CD drive ??) alias playcd=cdrom2 play01 d: REM won't switch to 853 if KEYB is loaded, must unload + switch + reload alias esperanto=mode con cp sel=853 alias 853=mode con cp sel=853 alias 737=mode con cp sel=737 alias 869=mode con cp sel=869 alias sta=mode con cp /sta alias status=mode con cp /sta alias 25=mode 80,25 alias 43=mode 80,43 alias 50=mode 80,50 prompt [ FreeDOS ] $p$g path a:\;a:\fdos;a:\utils;a:\extras;g:\ for %%a in (TEMP TMP TMPDIR) do set %%a=g:\ set DIRCMD=/lfn lfnfor on lfnfor complete on REM (normally uses LONGNAME.DAT, not silly patented VFAT hacks) REM (note that your .EXEs need int 21h, 71xxh Win9x API, e.g. DJGPP) :: starlfn /i REM screen saver, auto-sleep monitor after 7 mins. of inactivity idledpms 7 :: (now using UIDE w/ 5 MB cache, sorry Eric!) REM 32/4 = 8 MB cache :: lbacache flop 32 REM tickle == cache helper for floppy :: tickle REM Jack's RAM disk rdisk /s10 /:g if %CONFIG%==3 goto notnls g: if exist a:\fdos\ega2_17.tgz untar a:\fdos\ega2_17.tgz NUL a: mode 80,43 display con=(ega,,3) mode con cp prep=((853) a:\fdos\ega.cpx) mode con cp prep=((,737,869) g:\ega5.cpx) mode con cp sel=%DEFAULT% nlsfunc /y a:\fdos\country.sys REM ... NLSFUNC test begin ... echo a:\tmp\upper.com êÖîÞë a:\tmp\upper.com êÖîÞë echo. echo a:\tmp\upper.com Rugxulo a:\tmp\upper.com Rugxulo echo. REM ... NLSFUNC test end ... :notnls REM (can unload later) REM BioMenace (bmenace2.exe) needs this setup + BIO.COM :: jemm386 load x=test i=test noram REM (both of these can unload later) ctmouse /w /o shcdx33e /Q /D?FDCD000 /~ if %CONFIG%==3 goto finish g: if exist a:\fdos\keybrd.tgz untar a:\fdos\keybrd.tgz NUL a: REM (can unload later, needs 286+) REM !! BUG ALERT !!: do NOT use 2009 KEYB*.SYS files w/ 2006 KEYB.EXE if %DEFAULT%==853 keyb us,,g:\keyboard.sys if not %DEFAULT%==853 keyb gk,,g:\keybrd2.sys echo. echo KEYB: Ctrl-Alt-F1 to disable or Ctrl-Alt-F2 to re-enable! echo. :: mode con cp /status country.exe :finish time /t date /t ver /r set DEFAULT= cd\tmp (I18NDOS.TXT): /mnt/sdb: total 117 -rwxr-xr-x 1 root root 2573 2011-02-15 08:40 autoexec.bat -rwxr-xr-x 1 root root 65846 2008-03-25 23:33 command.com -rwxr-xr-x 1 root root 640 2011-02-12 10:33 config.sys drwxr-xr-x 2 root root 512 2010-10-22 02:48 extras drwxr-xr-x 2 root root 1536 2010-10-22 02:38 fdos -rwxr-xr-x 1 root root 45161 2009-08-01 16:18 kernel.sys drwxr-xr-x 2 root root 512 2010-10-22 02:39 tmp drwxr-xr-x 2 root root 1024 2010-10-22 02:38 utils /mnt/sdb/extras: total 698 -r-xr-xr-x 1 root root 1528 2010-10-30 06:24 biopatch.txt -r-xr-xr-x 1 root root 264340 2010-10-22 02:49
