[Freedos-user] Kernel 2040 16-bit
Hi, Last year I wrote about a problem with 16-bit 2039 kernels in portable computers: ChkDsk would report errors, and wouldn't even run. I later found that the 2039 32-bit kernel did not produce these errors, so I started using it in my two portables (IBM ThinkPad and Compaq Armada), and the errors never occurred again. No such problem had ever happened to me in desktops; it was restricted to portables. So much for last year. Now I downloaded kernel 2040 and began to use the 16-bit version in my desktop. Surprisingly, it has produced the same kind of error seen last year in portables. Here's a sample of the ChkDsk (version 0.9.2) messages: \FDOS\HIMEM is a directory without '..' \FDOS\JAPHETH is a directory without '..' \FDOS\JEMM is a directory without '..' \FDOS\USB is a directory without '..' \FDOS\HELP is a directory without '..' \FDOS\NLS is a directory without '..' \FDOS\DIVERSOS is a directory without '..' \FDOS\UIDE is a directory without '..' \FDOS\INI is a directory without '..' \FDOS\ESCONDER is a directory without '..' \RECURSOS \RECURSOS doesn't contain an '.' as first entry \RECURSOS\.AA2 is a directory without '..' \RECURSOS\. AA is a directory without '..' Error accessing the volume DosFsCk runs normally, and does not find any fault with the file system. I also tried kernel 2040 16-bit in one portable (ThinkPad), and the same errors happened. In short, this is the same story as last year; the only difference is that now it happens in the desktop too. My desktop computer is a Pentium 133 MHz with 128 MB memory. Marcos -- Marcos Favero Florence de Barros Campinas, Brazil -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unicode (It was 'Problem with USB keyboard insome c omputers')
> Most programs could already be loaded earlier in CONFIG.SYS if they > were adjusted in that way, though some of the DOS structures aren't > available yet in that case. That's one of the big advantages of TSR's, in my opinion. While CONFIG.SYS is being processed, DOS is not yet "all there". As a result, there are certain advanced DOS support functions you can't (or at least shouldn't) try to use, because they may not actually exist yet. -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unicode (It was 'Problem with USB keyboard in some computers')
> Ok, sorry, that's what I meant. That you find the chain at the List > of Lists, right? Yes. The first Device Driver header (NUL) is in the LoL. From there, you can follow the chain (a linked list of pointers) as far as you want, and can insert/remove new headers wherever 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unicode (It was 'Problem with USB keyboard insome computers')
> IMHO, TSR's have a lot of advantages over device drivers, and can still be > installed in CONFIG.SYS if you actually want/need to do that (with the > INSTALL= option). You can even write a single executable which can be loaded both as "device driver" (DEVICE= or DEVLOAD) and as normal program (INSTALL= or just usual execution). (Technical details in the next two paragraphs, skip at your leisure.) The easy way to do that is to utilize MZ (.EXE) format files that have another entry point specified in the header than (relative) address 0, because for "device driver" executables address 0 must contain the device header. A more interesting (though usually not necessary) way to do that is to realize that device loaders (including the one that's part of DOS's initialization code) don't actually use the "next header" pointer in the device header until after the initialization call returns. This allows one to initialize a part of that field with a jump instruction in the source code, which will be executed if the flat (.COM) format file is executed as a normal program. The device initialization code of course needs to overwrite the jump instruction with something else before returning to DOS's device loader. Most programs could already be loaded earlier in CONFIG.SYS if they were adjusted in that way, though some of the DOS structures aren't available yet in that case. Regards, Christian -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unicode (It was 'Problem with USB keyboard in some computers')
Ok, sorry, that's what I meant. That you find the chain at the List of Lists, right? Aitor 2011/7/10 Bret Johnson : >> I'm curious, you check the LoL to get the pointers and override it? > > No, you just insert a new one with the same name in the Device Driver chain. > DOS always searches the chain in order, and uses the first one with the > correct name that it finds. It doesn't actually know, or even care, where > the "real" one is. > -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unicode (It was 'Problem with USB keyboard in some computers')
> I'm curious, you check the LoL to get the pointers and override it? No, you just insert a new one with the same name in the Device Driver chain. DOS always searches the chain in order, and uses the first one with the correct name that it finds. It doesn't actually know, or even care, where the "real" one is. -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unicode (It was 'Problem with USB keyboard in some computers')
I'm curious, you check the LoL to get the pointers and override it? Aitor 2011/7/10 Bret Johnson : >> Appart from turning DISPLAY into a DOS device driver and override >> kernel's CON, but not only IOCTL, but also write. > > FWIW, you don't actually need to turn DISPLAY into a device driver in order > to replace/enhance CON. You can do that with a TSR also. See my USBPRINT if > you want an example of how -- it "replaces" the default LPT1-LPT3, adds > LPT4-LPT9, and even passes calls through to the old LPTx in situations where > that is needed. > > IMHO, TSR's have a lot of advantages over device drivers, and can still be > installed in CONFIG.SYS if you actually want/need to do that (with the > INSTALL= option). > > > -- > 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-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unicode (It was 'Problem with USB keyboard in some computers')
> Appart from turning DISPLAY into a DOS device driver and override > kernel's CON, but not only IOCTL, but also write. FWIW, you don't actually need to turn DISPLAY into a device driver in order to replace/enhance CON. You can do that with a TSR also. See my USBPRINT if you want an example of how -- it "replaces" the default LPT1-LPT3, adds LPT4-LPT9, and even passes calls through to the old LPTx in situations where that is needed. IMHO, TSR's have a lot of advantages over device drivers, and can still be installed in CONFIG.SYS if you actually want/need to do that (with the INSTALL= option). -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] weird keyboard keys (was Re: Problem with USB keyboard in some computers)
Hello, 2011/7/7 Rugxulo : > All keyboards aren't all the same, though, which is why it's best not > to hardcode key settings or use anything too obscure. My old 486 had a > Macro key (available to use in SETEDIT via included TSR), my P166 had > a Turbo key (typematic rate?), my laptop doesn't even have Pause/Break > nor SysReq (does any DOS software use that???) nor numpad (natch, > though some few laptops do). And of course that makes things like > Ctrl-Break or Ctrl-Alt-SysReq-R-E-I-S-U-B impossible! ;-) Oh, and > Eric (Auer) only buys 102-key keyboards (no Win or Menu keys, which > most DOS apps ignore anyways except TDE). I think (old) XKEYB allowed > for some user-defined stuff for those keys (0xE0 prefix???), but since > XKEYB is deprecated, I guess it doesn't matter here. This should be possible with FD-KEYB too. The only xkeyb thing that is not implemented is the so-called "X-Functions", which allows your TSR to do a CALL FAR upon pressing some key. Aitor -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
