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 lot too. But I've found 0.84 stable for my uses. (And that's what DOSEMU includes, and LFNs work there, so ....) >>> MOUSE >> Eh? Renamed CTmouse or ... ? Make sure to use 2.1b4, possibly with >> "/w" and maybe (?) "/o". > > Ah yes renamed CuteMouse. With the update to 2.1b4 I'm not sure how much > is left of the separate language versions. Dunno, check http://cutemouse.sf.net > Did I mention hating CuteMouse 2.1b4's cursor/pointer refreshing speed > in EDIT ? Like 5 times per second instead of once every 2 seconds or so :( Is that a CTmouse bug (Eric) or EDIT (Aitor)? >> 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. > > Nice trick. BTW, anybody know if "alias" was ever meant for anything with parameters? I'm not so convinced and haven't looked too hard. A quick play finds that %%a will maybe do what I want, but I'm not sure. In any case, I end up doing weird hacks sometimes like "for %%a in (cls dir) do %%a". :-)) Yeah yeah, I know, 4DOS .... ------------------------------------------------------------------------------ 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
