Re: [Freedos-user] Com1: corruption from PS2 mouse
> More detail: > The rs232 port Com1: is connected via a Null modem cable to an Adam 232 to > 485 converter. > In the Bios I have Com2 to 3 disabled. > An IRQ clash is possible if Cutemouse uses IRQ4 from Com1. > My next step is to try different mouse drivers, unless I get more > suggestions. there can't be an interrupt conflict: in DOS, there is no interrupt chaining. if the interrupts would be in conflict, you would not receive any characters at all. > In fact it even corrupts without movement as a result of being polled. you didn't specify: what is 'corrupt' ? a) characters as received on the other end? b) input messed? c) input characters dopped? if c): are you using the FIFO? do you see the overrun error bit set? (most likely caused by the USB BIOS which disables interrupts longer then your baudrate allows. use the FIFO!) Tom -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Com1: corruption from PS2 mouse
> The serial port is opened in FreeBasic with : > Open Com "COM1:38400,n,8,1,cs0,ds0,cd0,rs" For Random As #CP FreeBasic doesn't support FIFO, and most likely no IRQ. try Open Com "COM1:600,n,8,1,cs0,ds0,cd0,rs" For Random As #CP and see if that changes your problem. Tom -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Com1: corruption from PS2 mouse
> FreeBasic doesn't support FIFO, and most likely no IRQ. > try > Open Com "COM1:600,n,8,1,cs0,ds0,cd0,rs" For Random As #CP > and see if that changes your problem. sorry, not true. FreeBasic seems to use IRQ, but not FIFO. anyway, try Open Com "COM1:600,n,8,1,cs0,ds0,cd0,rs" For Random As #CP Tom -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Quickview ver 2.60
> DOS might have problems with SATA drive. DOS reads from the harddrive a > lot. > Since SATA is serial (just one bit at a time) The data ransfer rate might > be too slow for DOS to live with. I know I can't get it to run on a SD card > because one bit at a time is just too slow. back in the good old times, when DOS was popular, PATA disk drives used PIO for transfer, which is limited to (less then) 8 MB/sec. currently, SATA hard disks transfer up to 120 MB/sec and SATA SSDs transfer ~500 MB/sec. this should be fast enough even for DOS. > You won't know until you try it. I don't have the faintest idea what you are doing wrong, but you are doing it the wrong anyway. Tom -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Shaw's Nightmare
> I've released alphas and beta versions of the game. > http://www.mediafire.com/download/36t9ql7z19x14i8/SN0_1.ZIP: tech demo. > http://www.mediafire.com/download/ddem9tk51xdaidu/SN0_3.ZIP: alpha 0.3 > http://www.mediafire.com/download/u7hdsdtevhv4omt/SN0_6.ZIP: alpha 0.6 > http://www.mediafire.com/download/k88mk8zv58ztgs3/SNBETA.ZIP: Beta 0.91 this is NOT a mailing list of your subscribers releasing ALPHA whatever to a public mailing list is considered spam >Do not contact us about this. If you do you will be Fusion Cannoned. :) :<< Tom -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Loading UIDE with devload
> Is it safe to load UIDE in FDAUTO.BAT with DEVLOAD.COM, instead > of loading it in FDCONFIG.SYS as recommended in the > instructions? yes, this is save. Tom -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] [Freedos-devel] FreeDOS 1.2 and 2.0 roadmap discussion
> Now the new multi-TB hard drives have 4096-byte physical sectors,
> at least some of them try to act as if sector size were 512 bytes.
virtually ALL disks act as having 512 byte sectors, even if they have
internally 4096 byte ('advanced format').
search for '4K native' drives, and you will see that they are rare.
there's a good reason for this: only Windows 8 can boot from 4K
sectors, not Win7. and making hardware incompatible to 80% of all
existing computers is usually not such a smart idea.
see also
http://www.heise.de/ct/ausgabe/2014-18-Test-Ungemach-durch-Festplatten-mit-4K-Sektoren-2283687.html
only recently 4kn drives became available
Seagate Enterprise Capacity 3.5 HDD 4Kn 6TB, SATA 6Gb/s (ST6000NM0004)
Toshiba MG04ACA500A
> So any modern OS needs to support at least 4096-byte sectors.
it certainly doesn't hurt, but this is not urgent
> There really needs to be GPT support with hard drives that would have
> 4096-byte sectors.
wrong. GPT is needed for drives with more then 4G sectors, which is
disk size 2TB for 512 sector size, and 16 TB for 4K sectorsize.
as a side note: a good portion of modern USB enclosures *simulates*
sectorsize 4K, so big disks ( >2 TB) can be handled without GPT
(read 'Windows XP')
> Next step up from 4096 bytes could be 8k, 16k ...
this will most likely never happen. the gain from moving 512 byte -> 4K is
roughly 10% in disksize, and may be worth the trouble. the gain for going from
4K
to 16K would be much less, and almost certainly not worth the trouble.
Tom
--
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS wishlist
> Ability to run Windows 3.1 in 386 enhanced mode. has been discussed multiple times. conclusion: forget it Tom -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS wishlist
> My reason for wanting to use Windows 3.1 in FreeDOS is for some > very specific apps (yes among them are a couple of bible programs) > and just having access to some utilities such as Winimage Winzip, > etc. That said, since 1993 I have always had Compaq DOS/Windows 3.1 > on at least one of my PCs so, I can always fall back to that - just a bit > inconvenient. whatever your reason is: forget it. this would be a lot of work, and the developers find it more then 'a bit inconvenient' to put much effort in things that they aren't interested in. Tom > On Mon, May 18, 2015 at 8:32 PM, Rugxulo wrote: > Hi, > > On Mon, May 18, 2015 at 4:42 AM, Tom Ehlert wrote: >> >>> Ability to run Windows 3.1 in 386 enhanced mode. >> >> has been discussed multiple times. conclusion: forget it > > Okay, but let's be clear here: > > 1). It's proprietary, so it's not redistributable. > 2). It's old, so most people don't have (nor want) it. > 3). It used undocumented MS-specific data, so it's fairly hard to be > compatible. > 4). It's harder (maybe impossible) to run on even semi-modern machines > due to its own bugs and design limits. > > However, that doesn't mean it's totally not worth supporting. In fact, > I could be wrong (never cared much personally, thus never tested, I > prefer "real" DOS, not Win16 GUI apps), but I think DOSBox claims to > work with Win 3.x (or maybe even Win95). I know for a fact that DR-DOS > 7.03 fully works, but I'm not sure about OpenDOS or EDR-DOS. > (Obviously those have different licenses, but I know it's not [always] > totally illegal to reverse engineer or clean-room, esp. when dealing > with explicit compatibility problems like this.) > > Regarding DOS apps themselves, the only real reason to use Win 3.1 > would be for something like multitasking (or maybe some obscure > drivers??). In that case, it's probably easier to instead just use > DOSEMU under Linux. > > So, summary: it's hard to support but not impossible, but the simple > answer is to look elsewhere at pre-existing solutions (or similar). > > > -- > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 -- One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Getting any CD player to work
> On 6/8/2015 7:27 AM, Dale E Sterner wrote: >> For printers its usually easy to find the control commands but >> for cd units I've never seen them made available to the public. >> Is there a command list published anywhere for cds. >> > Yes, it's called ATAPI and there exist a lot of different documents for > the different classes of ATAPI devices. The only non-ATAPI CD-ROM drives > that I am aware of are/were those of some early Creative > soundcard/CD-ROM drive combos. Those used their own subset of ATAPI > commands, hence a more standard CD-ROM driver won't work, as well had > their own digital audio connector that made those CD-ROM drives only > work with their bundled sound cards and vice versa... > The catch with the documentation however is that this is stuff that you > have to buy from t13.org, the committee that defined those standards... googling 'ATAPI specification' turned up www.bswd.com/sff8020i.pdf at position 2. there are MANY other links containing the ATAPI spec. even you old time DOS guys should start to use a search engine instead of asking such (easy answered) questions on mailing lists. Tom -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Doom unstable with LBACACHE or RDISK
Hallo Herr Eric Auer, am 27. Juni 2015 um 19:18 schrieben Sie: > Hi Mateusz, >> After some investigations, I pin-pointed the problem to this: >> >> If I load any of these TSRs: LBACACHE, RDISK, then Doom either freezes >> at start, or make the computer reboot. > If I have to guess: RDISK, LBACACHE and DOOM may all cause > the A20 to toggle wrong. in normal circumstances A20 is always enabled. A20 is disabled when programs are started, and is disabled with the next INT21 interrupt (assuming the kernel is loaded high). and no program has any reason to disable it ever again. > as a side effect of doing protected mode > stuff (even if it is only accessing XMS) and USB emulation > of PS/2 and keyboard controllers, or injection of events > to the actual controllers, in BIOSes may have bad stability > as well. You could try other A20 methods or configure your > EMS and/or XMS drivers differently, maybe even towards A20 > being locked to the "modern" state. Or you could try some > other DOS extender than the one which is default for DOOM. > The latter can also help if things are generally less stable > due to issues with UMB, XMS 2 versus 3 or having large RAM > amounts in the first place. For example DOS32A as a modern > replacement of DOS4GW :-) > Cheers, Eric > PS: FreeCOM and kernel also affect A20 by using XMS swap > and the high memory area (HMA). wrong, too. > You can try a non-XMS-swap > version of FreeCOM and/or tell the kernel to use no HMA. Tom > -- > Monitor 25 network devices or servers for free with OpManager! > OpManager is web-based network management software that monitors > network devices and physical & virtual servers, alerts via email & sms > for fault. Monitor 25 devices for free with no restriction. Download now > http://ad.doubleclick.net/ddm/clk/292181274;119417398;o > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Rugxulo IS A FRAUD!!!
I recommend to ignore this thread. Tom -- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to make the R-Alt key act like L-Alt?
Hallo Herr John Hupp,
am 16. Juli 2015 um 01:48 schrieben Sie:
> For a US layout keyboard and the default BIOS keyboard driver: I brought
> this issue up a long time ago and learned that by design R-Alt is a dead
> key and does not duplicate the functionality of L-Alt.
> I have always found it to be awkward, slow and displeasing to invent
> some other finger usage to do an Alt-File or Alt-X, which are very
> common key combinations.
> Today I have been studying xkeyb and keyb, trying to find a way to get
> what I wanted, but I have come up dry so far.
> With xkeyb, recent versions now support an extended scancode for R-Alt
> (E56), but L-Alt is 56, and the [Shifts] section of its US.KEY supports
> association of only one scancode with ALT, and by default that scancode
> is 56. By contrast, [Shifts] has a Shift1 and Shift2 association,
> thereby enabling both L-Shift and R-Shift to be identified as Shift keys.
> With keyb, documentation notes that one might edit a KEY file and use KC
> with that to compile a custom keyboard layout (KL) file to load, and I
> am now trying to plow through the KC doc files, but it's pretty dense
> reading.
> Can anyone detail or at least outline a solution?
outline, without *any* warranties:
L-ALT sends scancode 0x38
R-ALT sends scancode 0xe0 0x38
the keyboard handler should :
if scancode 0x38 is detected, clear 'extended' status
in BIOS
locate MKEYB to modify (castrate)
replace
int cdecl NAME(cint15_handler)(uchar scancode)
{
...
}
with
int cdecl NAME(cint15_handler)(uchar scancode)
{
debug_scancode = scancode; /* very nice for debugging */
/* hit ESC - and we are gone */
if (scancode == 0x38)
{
*(char far*)MK_FP(0x40, 0x96) &= ~0x02;
}
return scancode;
}
compile and test
good luck ;)
Tom
--
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] picoTCP: a modern, open-source TCP/IP stack for DOS
Hello Mateusz, a) you forgot to publish the source for picotcpl.lib and picodosl.lib b) the only provided example program PING.EXE is HUGE (120K/63K when compressed) when compared to mTCP ping.exe (40K/28K compressed) what exactly is the advantage of 'pico'TCP? Tom am 19. November 2015 um 20:00 schrieben Sie: > Hello group, > I write this message to share a little news about what I was doing in my > spare time these last two months: porting picoTCP to DOS. > picoTCP is a modern, dual-stack, open-source TCP/IP stack. It has been > created by the good people at Intelligent Systems (Altran), primarily as > a stack designed for embedded computing (hence hardware with very > limited horse power). It is backed by a well established corporation and > it's actively maintained. > I played with the stack for some times now, and ended up building an > entire DOS compatibility layer around it. A few patches were required to > the stack, a few days of development, many hours of debugging - but here > it is - the first public release of picoTCP for DOS! > http://picotcp4dos.sourceforge.net > The project contains three major parts: > - ipcfg: a little tool that allows to configure networking on your DOS > machine (IP, DNS, etc). No, it's not a text file - I wanted to avoid the > complexity of parsing a text file, and opted for a binary configuration > file that is manipulated via ipcfg. It's much more flexible that a text > config file, while being much easier/faster to load at runtime. > - ping: no need to explain, I guess... my ping tool for DOS, based on > picoTCP - crucial when it comes to testing your networking > - an OpenWatcom library package (openwatcom, large memory model) - this > is for the fellow developers that would like to use the DOS version of > picoTCP inside their network-enabled, 16-bit DOS programs. I integrated > a packet driver schim, a DOS-compatible timer, as well as the whole IP > configuration logic, so it is now a simple (2 functions!) public API > that allows to load picoTCP, use it, and unload it. > *** Short how-to *** > 1. Download picotcp4dos and unzip it on your drive > 2. Set the location where the config file will be stored, for example: > SET PICOTCP=C:\PICOTCP.DAT > 3. Bind picoTCP to the interrupt vector of your packet driver, example: > ipcfg int 60 > 4. Configure your IP settings using ipcfg, or use DHCP (ipcfg dhcp) > enjoy! > Mateusz > -- > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] UltraDMA warning corrected
> I am concerned by this statement from Jack's email: "Take a look at > the sources for Microsoft HIMEM or EMM386, as I have…" This is the > first I was aware that Jack had reviewed any source code from > Microsoft. Microsoft made the source for HIMEM.SYS available to programmers in 1988. "February 7, 1989 Copyright (c) 1988, Microsoft Corporation, Lotus Development Corporation, Intel Corporation, and AST Research, Inc. Refer to the document "eXtended Memory Specification (XMS), ver 2.0" for HIMEM.SYS copyright and warranty information. ... Some programmers may want to obtain the full XMS distribution disk, which contains the source code to HIMEM.SYS, a C interface to the XMM, a test of test programs, and documentation. In the domestic United States, to obtain the latest official XMS release disk, call Microsoft customer service at (800)426-9400 and ask for a copy of the XMS Specification and it's supplemental diskette." yes, it's copyrighted and shouldn't be copied. (btw: the source for himem.asm has no copright mentioned). but most low level programmers that were active in ~1990 (looong before FreeDOS) had already looked at this (including me). and I feel in no way tainted by this. FreeDOS HIMEM.EXE is in no way influenced by my reading of HIMEM.ASM in ~1990. note: source for EMM386 was never published, but leaked to the public in ~2003. Jack probably talks about this EMM386. > When Microsoft released the source code to an earlier version of > MS-DOS (March 2014) source for MSDOS 1.1 and 2.0 is completely useless for FreeDOS design and implementation. and has no HIMEM anyway. BASE >> XMGR > http://www.freedos.org/software/?prog=xmgr > * providing XMSv3 > So we will now need to remove XMGR from the FreeDOS distribution. I don't think so. I took a look at XMGR.ASM. XMGR.ASM is so obviously coded by Jack (judging by coding style) that the claim of a copyright violation would be ridiculous. Tom -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] INTERLINK
>> Just want to know if FreeDOS can run interlink.exe and intersrv.exe >> If FreeDOS is compatible with interlink, then what steps should follow? interlink/intersrv are part of msdos. this should work in theorie, but you are probably the first to test this on FreeDOS. > As far as I remember, those provide sector based connection wrong. it provides a file based service, and makes remote drives available as drive letters. > of FAT > partitions through a serial or printer port cable: As long as your > sector size is 512 bytes, that should probably work. Note that you > only have those tools if you already own MS DOS anyway and that the > tools only support FAT16 and maybe FAT12, but not FAT32. interlink/intersrv doesn't care about fat12/16/32 Tom -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] INTERLINK
Bret, > Eric/Tom: > I used to use INTERxxx a lot many years ago using the special > parallel cables designed for that purpose (I think I still have a > couple of those cables in my "spare cable box"). Parallel is MUCH > faster than serial (null modem) cables. I also used it *A LOT*. in times when there were no network cards a commodity. (the times they are a changing ...) > I believe Eric is correct when he says INTERxxx is sector-based > rather than file-based as Tom states. I do know that the client > (INTERLNK) must be capable of "understanding" the file system of the > server (INTERSVR). For example, if the client is MS-DOS 6.2 (which > doesn't understand FAT32) and the server is MS-DOS 7.x (which does > understand FAT32) and you're trying to access a FAT32 disk on the > server, it doesn't work. I know this for sure because I've tried > it. If INTERxxx was file-based, it wouldn't matter which version of > FAT was on either computer (and could even work on non-FAT drives > the server had mounted, like CD's and network drives). you are right, my memory was plain wrong on this. and - while debugging the crashing problem - I also saw that it installs itself as handler for INT 25/26 'DOS DISK READ/WRITE' Tom -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] INTERLINK
> Something else that should work if you don't want to modify it, add > /low option which will also bypass the problematic code. > Tom's workaround will be in svn kernel soon, but I need to do some > more testing as I'm still getting crashes, but haven't determined if > its because of memory managers, virtual box, or another kernel issue > with interlnk. (It crashes later in booting, but only if I load > interlnk, though it's fine if I add low to interlnk which seems odd > as functionally should behave same with applied patch.) I had only tested this with softice himem interlnk what is your crashing configuration? Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] INTERLINK
> The patched version of ITERLNK leads to problems if I still have a line > version=3.31 version=3.31 is lying about location and size of a couple DOS datastructures. don't do this, or expect trouble. use /low or a new kernel to run interlnk. tom -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS 1.2 Package LSM Data Verification
> CRYNWR - Unknown License, Dropped. > GCDROM - Listed as GPL, No Sources, Based on XCDROM, Removed. GCDROM sources are available. > UIDE - Free for non-commercial, Removed. > UMBPCI - Listed as free, No sources, Dropped. > XCDROM - Removed. an operating system without CDROM and network drivers doesn't sound very useful to me, even if everything has the correct license. YMMV. Tom -- Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS 1.2 Package LSM Data Verification
>> Without DOSLFN, no support at all for long filenames? > Correct. Although, I hear the was another very buggy one that was > around before DOSLFN. I don’t know the name. THIS.IS.RIDICULOUS. one of the worst manifestations of Stallmanitis ever. bye Tom. -- Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] JimDOS 1.0
>> an operating system without CDROM and network drivers doesn't sound >> very useful to me, even if everything has the correct license. YMMV. > I think that the key is to perceive FreeDOS as a replacement to MSDOS, > nothing else (that is, "BASE"). after 10+ years advertising that FreeDOS is better then MSDOS because UDMA, LFN, ... > The legalese on these things can be a > bit confusing, the distributor is obviously confused > so I believe that the extreme caution that FreeDOS > applies in this area is legitimate. it is not. LFNDOS is older then FreeDOS, and comes with a license 'open source. I don't care what you do wit it' CRYNWR drivers are older then linux. same licensing. UDMA is one of the drivers that actually made a huge difference on older motherboards. to stop delivering these packages suddenly after more then 10 years is more about this open source religion (Stallmanitis) then anything about legalese. Tom -- Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] command / shell conflict
Hallo Herr dosgeek57, > I am a user of DataPerfect and the WordPerfect shell. The command is > shell.exe. When I load by the shell I get a command.com strings error, my > path is wiped out and I have to reboot. The shell is necessary to run > macros, so not using it is not an option. I tried loadfix and that works the > first time if Jemmex and jemm386 are not loaded, but hangs on the second > try. Any suggestions are welcome. start by posting (pointers to) the files necessary to reproduce your problem: config.sys, autoexec.bat, shell.exe > -- > View this message in context: > http://freedos.10956.n7.nabble.com/command-shell-conflict-tp25034.html > Sent from the FreeDOS - User mailing list archive at Nabble.com. > -- > Mobile security can be enabling, not merely restricting. Employees who > bring their own devices (BYOD) to work are irked by the imposition of MDM > restrictions. Mobile Device Manager Plus allows you to control only the > apps on BYO-devices by containerizing them, leaving personal data untouched! > https://ad.doubleclick.net/ddm/clk/304595813;131938128;j > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 -- Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] command / shell conflict
Don, could you (or anybody else) prepare a virtual disk/floppy where this bug can be reproduced? If so, I'll give it a shot, as this seems to be the first reproducable memory corruption bug in freecom. Tom am 6. Juni 2016 um 12:42 schrieben Sie: >>So "all my path variables are intact" means there is probably a memory >>corruption issue somewhere?? > Since this happens on every PC (7 total) that is unlikely; and > this does not happen with the regular DOSes. > I am now using a menu (PowerMenu by Brown Bag Software) with the > %WPSHELL%/C command and our current FreeCOM which is working well. >>You mean "SET" within FDCONFIG.SYS?? > > I have a MENU selection in FDCONFIG.SYS pointing to an IF > "%config%" option in AUTOEXEC.BAT which loads my PowerMenu which > takes over from there, this is the "cleanest" way of resolving the issue that > I have found. >>But yes, FreeCOM has various bugs and needs to be cleaned up and >fixed >>(eventually), but so far nobody has stepped up to do it. > Yeah, we need to prioritize that for 2.0. > > On Mon, Jun 6, 2016 at 4:31 AM, Rugxulo wrote: > Hi, > > On Sat, Jun 4, 2016 at 4:34 AM, Don Flowers wrote: >> UPDATE: >> So after three or four loads of shell.exe per session, the strings error >> showed up again (Freecom 0.84) > > Even when using "/MSG /P"? So what is the implication, that there's a > memory leak in FreeCOM somewhere? I wouldn't be too surprised. > >> and Freecom 0.80 has some issues (2GB max shown on HD, OGN not recognized) > > Testing an old release for comparison? Why not test 0.82pl3 from SF.net? > > > https://sourceforge.net/projects/freedos/files/FreeCOM/082pl3%20%28use%20xmsswap%20for%20386%2B%20PC%29/ > > But yes, FreeCOM has various bugs and needs to be cleaned up and fixed > (eventually), but so far nobody has stepped up to do it. > >> I discovered one other alternative that seems to be working - I set a >> %config% variable (SET WPSHELL=C:\DP23\SHELL.EXE), > > You mean "SET" within FDCONFIG.SYS?? > >> then %WPSHELL% /C; >> following that I execute a batch file with the same command and the shell >> loads as it should and on exit all my path variables are intact with no >> strings error messages. > > So "all my path variables are intact" means there is probably a memory > corruption issue somewhere?? > > >> On Mon, May 23, 2016 at 5:21 PM, Rugxulo wrote: >>> >>> On Mon, May 23, 2016 at 4:18 PM, Don Flowers wrote: >>> > >>> > So /MSG seems to work, more testing needed to be sure, What does this >>> > switch >>> > do, (besides help me of course)? >>> >>> http://help.fdos.org/en/hhstndrd/base/command.htm >>> >>> "/MSG Stores all error messages in memory (requires /P as well)." > > > -- > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. > https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] command / shell conflict
Don, in my opinion this is a SHELL bug. after executing a program (being it command.com or dataperfect), shell does some 'cleanup' code. it simply thinks that all (MZ) memory blocks above SHELL.EXE are leftovers from external execution, and calls DOSfree(). if they are leftover PSPs, the potential environment at psp:[2c] is also freed. now freedos command.com loads it's own environment as high as possible; usually at around 9F9F:0. when SHELL executes an external program, this environment gets freed, and soon after trashed. SHELL bug. case closed. Tom am 6. Juni 2016 um 12:42 schrieben Sie: >>So "all my path variables are intact" means there is probably a memory >>corruption issue somewhere?? > Since this happens on every PC (7 total) that is unlikely; and > this does not happen with the regular DOSes. > I am now using a menu (PowerMenu by Brown Bag Software) with the > %WPSHELL%/C command and our current FreeCOM which is working well. >>You mean "SET" within FDCONFIG.SYS?? > > I have a MENU selection in FDCONFIG.SYS pointing to an IF > "%config%" option in AUTOEXEC.BAT which loads my PowerMenu which > takes over from there, this is the "cleanest" way of resolving the issue that > I have found. >>But yes, FreeCOM has various bugs and needs to be cleaned up and >fixed >>(eventually), but so far nobody has stepped up to do it. > Yeah, we need to prioritize that for 2.0. > > On Mon, Jun 6, 2016 at 4:31 AM, Rugxulo wrote: > Hi, > > On Sat, Jun 4, 2016 at 4:34 AM, Don Flowers wrote: >> UPDATE: >> So after three or four loads of shell.exe per session, the strings error >> showed up again (Freecom 0.84) > > Even when using "/MSG /P"? So what is the implication, that there's a > memory leak in FreeCOM somewhere? I wouldn't be too surprised. > >> and Freecom 0.80 has some issues (2GB max shown on HD, OGN not recognized) > > Testing an old release for comparison? Why not test 0.82pl3 from SF.net? > > > https://sourceforge.net/projects/freedos/files/FreeCOM/082pl3%20%28use%20xmsswap%20for%20386%2B%20PC%29/ > > But yes, FreeCOM has various bugs and needs to be cleaned up and fixed > (eventually), but so far nobody has stepped up to do it. > >> I discovered one other alternative that seems to be working - I set a >> %config% variable (SET WPSHELL=C:\DP23\SHELL.EXE), > > You mean "SET" within FDCONFIG.SYS?? > >> then %WPSHELL% /C; >> following that I execute a batch file with the same command and the shell >> loads as it should and on exit all my path variables are intact with no >> strings error messages. > > So "all my path variables are intact" means there is probably a memory > corruption issue somewhere?? > > >> On Mon, May 23, 2016 at 5:21 PM, Rugxulo wrote: >>> >>> On Mon, May 23, 2016 at 4:18 PM, Don Flowers wrote: >>> > >>> > So /MSG seems to work, more testing needed to be sure, What does this >>> > switch >>> > do, (besides help me of course)? >>> >>> http://help.fdos.org/en/hhstndrd/base/command.htm >>> >>> "/MSG Stores all error messages in memory (requires /P as well)." > > > -- > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. > https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Games
> I'm building the new website. I'll update the notice to encourage new > users to install FreeDOS in a virtual machine. any reason why we don't provide ready to run virtual machines as .VHD images? Tom -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohomanageengine ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Games
>> I'm building the new website. I'll update the notice to encourage new >> users to install FreeDOS in a virtual machine. > > any reason why we don't provide ready to run virtual machines as .VHD > images? > > Tom > Hmm... I don't know why we haven't. I don't know anything about VHD > though. Is that a standard virtual disk image that any PC > emulator/virtual machine can read? Can free/open source software > virtual machines read these (or create them)? .VHD is a fairly generic virtual *disk* format, and most virtual machines providers should be able to read them. a tiny bit more specialized are the virtual machine configuration files, but we should be able to provide multiple formats, for Virtual Box, DosBox, HyperV, ... still no rocket science, and no risk to damage user data. Tom -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohomanageengine ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] a unique directory tree question?
> I have a rather Unusual question about directory trees in dos. > I have a zip compressed file that contains rather a large number of .txt > files. > the files are of stories, and series, with the person who put the > materials together using some major breakdown, for example an item might > look like this. > d:\stories\abandoned\series\the-end-of-time.txt > Now when I ran pkunzip on the archive, the directory tree was created > correctly. > By which I mean there is a directory for abandoned, then a sub-directory > for series, then the stories underneath. > However in allot of cases the actual directory holding the .txt file is > different. Here would be a nice place to be more specific, and give an explicit example. > for the record, I am using word perfect to read the files. shouldn't matter. use the DIR command to show *real* filenames. > My question is this. > is there a limit to the number of branches so to speak, one can have in a > dos directory tree? no. sounds like a bug in LFNDOS. > Frankly I have never seen this problem before. I do have lfn loaded, so do > not think it is the names of the files, especially since some of the > content is present, and I got no error when I was unzipping the archive. > Thoughts? > Thanks, > Karen > -- > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San > Francisco, CA to explore cutting-edge tech and listen to tech luminaries > present their vision of the future. This family event has something for > everyone, including kids. Get more information and register today. > http://sdm.link/attshape > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 -- Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] upper memory trick
>> Has anyone tried "Installhigh=C:\FDOS\COMMAND.COM"
>> I have that working for a few apps (including DP and so far no issues, also
>> am loading CDROM drivers earlier in autoexec.bat and I can cram nealy
>> everything into upper memory.
> No, I never use INSTALL, though I'm vaguely aware of it. But FreeCOM
> isn't a TSR.
> Perhaps you meant SHELLHIGH?
right. INSTALLHIGH doesn't make sense for COMMAND.COM, use SHELLHIGH
> But I'm not sure how stable that would be
> in all circumstances.
is this your usual FUD ('I'm ot sure, but may be ...'), or do you have
a reason for this?
> (Honestly, FreeCOM needs to be better optimized for size and then we
> wouldn't have to worry at all. That is one of our weakest links.)
seriously: command.com has ~3 K resident size. what are you
complaining about?
Tom
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] upper memory trick
> On 22/07/2016 10:34, Tom Ehlert wrote: >>> (Honestly, FreeCOM needs to be better optimized for size and then we >>> wouldn't have to worry at all. That is one of our weakest links.) >> >> seriously: command.com has ~3 K resident size. what are you >> complaining about? > This implies swapping capability, which not every PC has. FreeCom is > nearly unusable on my 8086 fitted with 256K of RAM, you are absolutely right. FreeDOS without HIMEM is almost useless, with only ~93 K memory remaining for this machine. however note the topic of the post is 'upper memory trick', which excludes 256 K RAM machines. > unless recompiled > with all possible compile-time options disabled. use a CSWAP'ing command.com > COMMAND.COM from MS is > a much better performer in this (very specific) context. amen. Tom -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to use German keyboard layout with FreeDOS?
Kai, an amazing amount of effort to get a german keyboard driver :<< > Hi Eric, > thanks for the quick reply. In the meantime I found out that I can load a > German layout with just "keyb gr", just not the layout file itself or the > /E switch that is mentioned in that article. I assume the gr.kl is > embedded in the keyboard.sys file. > That's good enough for me. I don't need the Euro sign. I use FreeDOS > mainly on a USB stick for flashing bios and controller cards on rack > machines and my own workstations. And it drives me crazy if I have to > input some special characters like - _ / which commonly occur. Each time I > have to go by trial and error. And it seems you cannot type a ~ (tilde) at > all on a German keyboard under an en-us layout. > Now I can :-) > There is one thing still with keyb, though, that makes me wonder. > Shouldn't I be able to run it from autoexec.bat? I added "keyb gr" to it, > but it isn't executed (or it doesn't work at this stage). I have to run it > manually at the prompt. I'm also running keybw.com in autoexec.bat, right > before that. I don't know what that does. I just have it in there and > don't know if I added it some time ago or if it came with the first > FreeDOS configuration. Should I remove it? >> The KEYB layouts can be found here: >> >> http://www.freedos.org/software/?prog=kpdos > That's the point where the circle starts (and ends). There are no plain > keyboard layout files (.kl) in there, only the .key files. But these need > kc for compiling to a .kl file. And there's nowhere you can get kc from. in that case, KPDOS does not qualify as open source, and I recommend to remove KPDOS from future releases of FreeDOS > I don't need it now anymore it seems. But still wondering if it's really > not available from anywhere. >> Viel Spass! > Gleichfalls, von Berlin nach Berlin :-) > Kai instead I recommend http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/keyb/mkeyb/mkeyb041.zip and a command line KEYB GR (note: I'm the author) Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to use German keyboard layout with FreeDOS?
Hallo Herr Kai Schaetzl, am 18. August 2016 um 15:31 schrieben Sie: > Tom Ehlert wrote on Mon, 15 Aug 2016 16:00:55 +0200: >> an amazing amount of effort to get a german keyboard driver > Not really once you know that you don't need the .kl file. > According to > http://help.fdos.org/de/hhstndrd/base/keyb.htm > you have to run (as an example) "keyb GR,,GR GR.KL /E". > You need the .kl file for this. > However "keyb gr" suffices. Just that it's not mentioned anywhere. As I > said I assume the GR layout is embedded in keyboard.sys, anyway. > With that in mind, it's the same as with your driver: download and run > "keyb gr". Anyway, just to see if there's a difference I changed now to > mkeyb. Both keyboard drivers work. > But I have the same problem with it. Adding "keyb gr" to autoexec.bat does > not run it. It seems autoexec.bat isn't executed at all. if something 'seems', add echo HELLO WORLD to the front of your autoexec.bat > Shouldn't it run > automatically once DOS is loaded? yes. as our clairvoyant has left us, how about posting CONFIG.SYS? > Thanks! > Kai Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dma crosses 64k boundary error
> I keep getting the error dma crosses 64k boundary when using tools > like rawrite3 or hard drive manufacturers tools floppy creation > software. I need to boot from Windows 98 bootdisk to get rid of it. > Please let me know if there is a way to get rid of this problem under FreeDOS. MSDOS redirects int 13 to an internal driver, detects DMA access crossing a 64k boundary, and avoids it. FreeDOS ddoes not do this; sorry. there was no need to do this so far; IMO rawrite3 could/should handle this by itself. of course, software is usually only tested against MSDOS, so there is little motivation to do so for rawrite3 programmers. I'm still surprised this comes up today, and not 15 years ago. do you have remarkable hardware? Tom -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Ynt: Urgent FreeDos Keyboard Layout Hardware Help
Dear Eric Auer, could concentrate ONCE on the problem at hand, and not on all this blablabla about file versions? the problem seems to be that this freedos.img, booted in VirtualBox, is able to generate funny characters (i without dot, C with hook, ...) and not on real hardware. now it would be cool if we had a screenshot (photo) of this iamge, booted on real hardware. btw: don't use EMM386 at all (for the moment), although I would not expect problems. now remove EVERYTHING not strictly necessary except keyboard.sys last question: do you have the problem on the command line as well, or only in VTUR? Tom am 10. September 2016 um 13:52 schrieben Sie: > Hi Salih, > thanks for sharing the 1.44 MB boot floppy image. It is correct that > you cannot send files to the list, but the config & autoexec easily > fits into a mail for the list by cut and paste: >> !DEVICE=A:\DRIVER\HIMEM.EXE > Supports options to manually select things but default should be okay. >> !DEVICE=A:\DRIVER\EMM386.EXE FRAME=d800 X=TEST > If you do not really need EMS 3 support, you should not force EMM386 > to provide a page frame. In particular, you should not force it to > use a hardcoded location which may or may not work on a given system. > You could for example try: X=TEST I=TEST NOEMS /VERBOSE >> !COUNTRY=090,857,A:\DRIVER\COUNTRY.SYS >> !SHELL=A:\COMMAND.COM A:\ /E:2048 /F /MSG /P=A:\FREEDOS\FDAUTO.BAT >> !DEVICEHIGH=A:\DRIVER\XDMA.SYS > XDMA is rather old. If you do not need it, you can skip it. >> !DEVICE=A:\DRIVER\SRDXMS.SYS > You may want to specify the size of the desired ramdisk here? >> !DOSDATA=UMB >> !DOS=HIGH,UMB >> !FILES=120 >> !BUFFERS=30 >> !LASTDRIVE=Z >> @echo off >> >> PATH=A:\;A:\FREEDOS;A:\DRIVER >> >> DISPLAY con=(EGA,857,1) >> mode con codepage prepare=((857) A:\FREEDOS\EGA.CPX) >> mode con codepage select=857 >> NLSFUNC /Y A:\DRIVER\COUNTRY.SYS >> KEYB.exe tr,857,A:\FREEDOS\keybrd2.sys /id:179 > Interesting that you specify a special variant of keyboard. > As mentioned earlier, you may want to use /NOHI for KEYB. >> VTUR > Your software gets started at boot automatically. > Finally, here is a full list of versions of used files. They > seem to be a bit old in general, but it is quite possible that > many files simply had no updates since then, as they already > had reached the desired state. > File sizes & versions root: >315 fdconfig.sys > 46685 KERNEL.SYS 2042 (build 2042 OEM:0xfd) [compiled May 11 2016] > 66945 COMMAND.COM 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00] > File sizes & versions freedos: > 233 fdauto.bat > 504 getargs.com reads memdisk command line > 510 hdd.bat textinst / postinst installer caller?? > 1024 xmssize.com 2005, checks free XMS > 1456 iniadd.com 2004, edits config > 1530 oscheck.com 2004, checks boot sector type > 2839 nlsfunc.exe 2004, version 0.4, /Y loads optional Y/N tables > 2977 append.exe 2004, appends search path for data files > 3657 DISPLAY.EXE 0.13b, loads custom fonts > 3759 localize.com 2003, shows translateable messages > 4149 choice.exe 2003, version 4.4, lets user make choices > 5861 DOSKEY.COM obsolete, command.com has functionality built-in > 6464 EGA.CPX from CPIDOS, with fonts 437, 850, 858, 852, 853, 857 > 11446 KEYB.EXE version 2.01 > 11681 sys.com version 3.6e > 13077 KEYBRD4.SYS keyboard definitions > 14395 VTUR.COM (your own software) > 16254 MODE.COM old 2005 version > 17049 USBKEYB.COM version 0.09 > 29722 KEYBRD2.SYS keyboard definitions > 30189 EDIT.HLP compressed help texts > 36640 KEYBRD3.SYS keyboard definitions > 40332 KEYBOARD.SYS keyboard definitions > 49264 srdisk.exe version 2.09 (Marko Kohtala's resizeable ramdisk) > 64046 EDIT.EXE (text editor) > File sizes & versions driver: > 1577 eltorito.sys version 1.4 > 2423 shsucdhd.exe version 3.01 > 2535 xdma.sys old version 3.3 > 2882 srdxms.sys version 2.09 (see above) > 3069 devload.com version 3.15 > 3745 xcdrom.sys version 2.3 > 4595 cdrcache.sys 2004 version > 5612 shsucdx.com version 3.03a (SHCDX33A) > 8058 himem.exe version 3.26, Aug 25 2006 > 15201 USBUHCI.OVL overlay for usbuhci > 16799 emm386.exe version 2.26, Aug 25 2006 > 20776 USBUHCI.COM version 0.14, apparently 2010 > 30250 country.sys data file for nlsfunc country specific settings > Maybe the others have additional comments on the used file versions! > Regards, Eric > -- > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Ynt: Ynt: Ynt: Ynt: Urgent FreeDos Keyboard Layout Hardware Help
> On physical machine any of keyboard layouts not work. In Virtualbox every > keyboard layout is working. > > We think real machine memory side has a problem with loading keyb.exe. there is a tool called MEM.EXE where you can detect if KEYB is loaded or not. it may be as well that MEM gets loaded, but your BIOS or hardware does not behave as KEYB is expecting it. to debug your problem: reduce FDCONFIG.SYS to !SHELL=A:\COMMAND.COM A:\ /E:2048 /F /MSG /P=A:\FREEDOS\FDAUTO.BAT and FDAUTO.BAT to DISPLAY con=(EGA,857,1) mode con codepage prepare=((857) A:\FREEDOS\EGA.CPX) mode con codepage select=857 NLSFUNC /Y A:\DRIVER\COUNTRY.SYS KEYB.exe tr,857,A:\FREEDOS\keybrd2.sys /id:179 or possibly even KEYB.exe tr,857,A:\FREEDOS\keybrd2.sys /id:179 are you able to produce turkish characters? if not, you are runnning interesting hardware. no way to debug this over the internet, you have a real problem. you may try if MKEYB behaves differently. MKEYB GR should swap 'Y' and 'Z'. Tom -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Ynt: Ynt: Ynt: Ynt: Urgent FreeDos Keyboard Layout Hardware Help
Hello Salih, did you try to boot your image on real, but different hardware, like a standard PC? Tom -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Ynt: Ynt: Ynt: Ynt: Ynt: Urgent FreeDos Keyboard Layout Hardware Help
as usual. urgent problem. even 'Solver of this problem will be rewarded with 500$.' a lot of more or less helpful messages exchanged. then all of sudden the original poster vanishes, without any feedback if all the given advice helped, or not, and how he solved his problem (or not). after wasting our time this is not nice behaviour. Tom -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedos 1.2 install
Hi, to reproduce this FIND problem, I tried to setup a new FD1.2 machine. what I did: download FD12LGC.ISO create a new virtual box machine with 512 MB disk use FD12LGC.ISO to boot the machine. boot machine. 'Unfortunately, this method of installation is not supported on this hardware platform. Please try a different installation method.' Welcome to the FreeDOS 1.2 operating system. now what? a hint to use the other .ISO would have been be helpful eventually I figured this out, and setup was successful. some remarks though: the setup results in FDCONFIG.SYS: 12:DOS=UMB makes virtually never sense. DOS=HIGH,UMB is always the better option. what purpose is SHARE supposed to have? SHARE is useful when the machine is running as a server, or with windows (or any other multitasking OS). don't install this. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] after find, Error reading from drive A: DOS area: general failure.
I could reproduce this. it happens in/after findnext() this error is related to the compiler. if the source is compiled using TurboC 2.01 the error occures. compiling the exact same source with TCPP the error is gone. try www.drivesnapshot.de/freedos/findtcpp.com and www.drivesnapshot.de/freedos/findtc21.com of course this can be a kernel bug, but as well a turbo library bug, or some sort of interference between them. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] after
Originally to: ALL I could reproduce this. it happens in/after findnext() this error is related to the compiler. if the source is compiled using TurboC 2.01 the error occures. compiling the exact same source with TCPP the error is gone. try www.drivesnapshot.de/freedos/findtcpp.com and www.drivesnapshot.de/freedos/findtc21.com of course this can be a kernel bug, but as well a turbo library bug, or some sort of interference between them. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedo
Originally to: ALL Hi, to reproduce this FIND problem, I tried to setup a new FD1.2 machine. what I did: download FD12LGC.ISO create a new virtual box machine with 512 MB disk use FD12LGC.ISO to boot the machine. boot machine. 'Unfortunately, this method of installation is not supported on this hardware platform. Please try a different installation method.' Welcome to the FreeDOS 1.2 operating system. now what? a hint to use the other .ISO would have been be helpful eventually I figured this out, and setup was successful. some remarks though: the setup results in FDCONFIG.SYS: 12:DOS=UMB makes virtually never sense. DOS=HIGH,UMB is always the better option. what purpose is SHARE supposed to have? SHARE is useful when the machine is running as a server, or with windows (or any other multitasking OS). don't install this. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedos 1.2 LSM files without CR
in the APPINFO directory, the LSM files are formatted UNIX style LF, and not DOS style CR LF btw: I'm no longer able to locate FreeDOS sources for FIND and it's maintainer from freedos.org. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Bug with FreeDOS 1.2 and "find"?
>> Am 16.01.2017 um 13:12 schrieb BlameTroi : >> I got this after a FIND command. >> >> C:\ELVIS\DOC>find /i "env" e*.htm >> file list ... >> Error reading from drive A: DOS area: general failure >> >> I've triple checked and I have nothing in my autoexec or config that >> points to drive A:, nor does A: show up in any of the environment >> variables. Of course, that drive is empty. > I can verify the problem in FreeDOS 1.2. It doesn’t happen in FreeDOS 1.1. > Look at the screenshot: > https://lazybrowndog.net/freedos/files/find-bug.png as stated elsewhere, the bug happens when FIND is compiled using TC 2.01 you have no drive in A: it's simply a bug in FIND Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedo
> Why not use the CHOICE option to let the user decide? because 99,9 % of all user have no need for SHARE. > I have a > menu system which is designed to be used on a network and requires share to > be loaded are really multiple machines accessing the same files at the same time? > IMHO this should be used of the FDNET option as well to allow users > to copy their specific packet driver to the /FDOS/NETWORK dir to > avoid an error msg after initial installation.. Tom > On Sat, Jan 21, 2017 at 6:21 PM, Jerome Shidel wrote: > Tom, >> what purpose is SHARE supposed to have? >> SHARE is useful when the machine is running as a server, or with >> windows (or any other multitasking OS). >> >> don't install this. > You are probably correct that it should load it by default. > I rem’d it out for future releases. > Jerome > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedo
Hello again, > Do you want to load FreeDOS High, UMB? there is no good reason (for normal use) to have ever DOS=HIGH,UMB disabled. if no HIGH or UMB memory is found, it is silently ignored. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] EtherDFS - a network drive for DOS
Mateusz, really cool. unfortunately I don't have a linux machine around, so testing must wait. may I suggest to use UDP/IP instead of raw packets? UDP/IP requires just a few bytes set up in the right way, and the calculation of the IP checksum; shouldn't be too much work. this would be much easier to use in multi-everything environments like linux or windows. specifically raw sockets are not available in standard windows many thanks anyway for starting this project Tom am 31. Januar 2017 um 10:19 schrieben Sie: > Hi all, > I write this short announcement to present an alpha version of a new > software I have been creating these past weeks. EtherDFS is an > "installable filesystem" for DOS. It installs a network drive that is > seen like any "normal" drive to DOS and its application, with the > exception that the actual data is located on a server. The server part is > called EtherSRV and currently only a Linux version of it exists. EtherDFS > uses raw ethernet frames to communicate with EtherSRV - this means only a > working packet driver is required, nothing else. > More information on the project's homepage: > http://etherdfs.sourceforge.net > I cannot stress enough the fact that this is an alpha version - it's in a > very early stage, and lots is to be done yet. It does work however, and > seems stable enough so it shouldn't make your PC explode. Its memory > footprint is quite huge for now, since its resident size is of 16 KiB. > Future versions will surely improve on that. Also, it *should* work with > MSDOS 5+, but I tested it only with FreeDOS so far. > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] bsum - compute BSD checksums of your files
>>> Unless I'm mistaken, conditional jumps on 8086 don't go beyond -128 .. >>> 127 (signed) byte range. Hence the billions of workarounds (TASM >>> "jumps", MASM "option ljmp", etc). right. >> I won't argue about what opcode is or is not available on 8086, since I >> did not bother decoding their exact meaning. meaning 'I am a lazy, clueless guy, but write anyway ...' >> I do see however that (NASM >> at least) can assemble JZ and JZ SHORT in two very different forms, JZ >> SHORT being significantly shorter. >> >> 5 B80100 mov ax, 1 >> 6 0003 48 dec ax >> 7 0004 746Ajz short gameover >> >> 5 B80100 mov ax, 1 >> 6 0003 48 dec ax >> 7 0004 7503E9DD01 jz gameover >> >> Of course NASM always uses the short form whenever it's possible, but >> when the jump is too far away it silently uses the longer form, hence the >> need to always specify SHORT if one wants to be sure what's going on. > AFAIK, meaning 'I am completely clueless , but offer my unfounded opinion anyway ...' > the longer one is 386+ only, hence not available with "cpu > 8086". Thus, if it still quietly assembles, that is a bug (but I > thought that was long-ago fixed/avoided). the longer one is 2 instructions instead, automatically generated by NASM because the intended jump goes farther then 127 bte c:\>debug -e 100 1430:0100 00.75 00.03 00.e9 00.dd 00.01 -u 100 1430:0100 7503 JNZ 0105 1430:0102 E9DD01JMP 02E2 Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Ynt: Y
From: Tom Ehlert > On physical machine any of keyboard layouts not work. In Virtualbox every keyboard layout is working. > > We think real machine memory side has a problem with loading keyb.exe. there is a tool called MEM.EXE where you can detect if KEYB is loaded or not. it may be as well that MEM gets loaded, but your BIOS or hardware does not behave as KEYB is expecting it. to debug your problem: reduce FDCONFIG.SYS to !SHELL=A:\COMMAND.COM A:\ /E:2048 /F /MSG /P=A:\FREEDOS\FDAUTO.BAT and FDAUTO.BAT to DISPLAY con=(EGA,857,1) mode con codepage prepare=((857) A:\FREEDOS\EGA.CPX) mode con codepage select=857 NLSFUNC /Y A:\DRIVER\COUNTRY.SYS KEYB.exe tr,857,A:\FREEDOS\keybrd2.sys /id:179 or possibly even KEYB.exe tr,857,A:\FREEDOS\keybrd2.sys /id:179 are you able to produce turkish characters? if not, you are runnning interesting hardware. no way to debug this over the internet, you have a real problem. you may try if MKEYB behaves differently. MKEYB GR should swap 'Y' and 'Z'. Tom -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Ynt: Y
From: Tom Ehlert Hello Salih, did you try to boot your image on real, but different hardware, like a standard PC? Tom -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Ynt: Y
From: Tom Ehlert as usual. urgent problem. even 'Solver of this problem will be rewarded with 500$.' a lot of more or less helpful messages exchanged. then all of sudden the original poster vanishes, without any feedback if all the given advice helped, or not, and how he solved his problem (or not). after wasting our time this is not nice behaviour. Tom -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Ynt: U
From: Tom Ehlert Dear Eric Auer, could concentrate ONCE on the problem at hand, and not on all this blablabla about file versions? the problem seems to be that this freedos.img, booted in VirtualBox, is able to generate funny characters (i without dot, C with hook, ...) and not on real hardware. now it would be cool if we had a screenshot (photo) of this iamge, booted on real hardware. btw: don't use EMM386 at all (for the moment), although I would not expect problems. now remove EVERYTHING not strictly necessary except keyboard.sys last question: do you have the problem on the command line as well, or only in VTUR? Tom am 10. September 2016 um 13:52 schrieben Sie: > Hi Salih, > thanks for sharing the 1.44 MB boot floppy image. It is correct that > you cannot send files to the list, but the config & autoexec easily > fits into a mail for the list by cut and paste: >> !DEVICE=A:\DRIVER\HIMEM.EXE > Supports options to manually select things but default should be okay. >> !DEVICE=A:\DRIVER\EMM386.EXE FRAME=d800 X=TEST > If you do not really need EMS 3 support, you should not force EMM386 > to provide a page frame. In particular, you should not force it to > use a hardcoded location which may or may not work on a given system. > You could for example try: X=TEST I=TEST NOEMS /VERBOSE >> !COUNTRY=090,857,A:\DRIVER\COUNTRY.SYS >> !SHELL=A:\COMMAND.COM A:\ /E:2048 /F /MSG /P=A:\FREEDOS\FDAUTO.BAT >> !DEVICEHIGH=A:\DRIVER\XDMA.SYS > XDMA is rather old. If you do not need it, you can skip it. >> !DEVICE=A:\DRIVER\SRDXMS.SYS > You may want to specify the size of the desired ramdisk here? >> !DOSDATA=UMB >> !DOS=HIGH,UMB >> !FILES=120 >> !BUFFERS=30 >> !LASTDRIVE=Z >> @echo off >> >> PATH=A:\;A:\FREEDOS;A:\DRIVER >> >> DISPLAY con=(EGA,857,1) >> mode con codepage prepare=((857) A:\FREEDOS\EGA.CPX) >> mode con codepage select=857 >> NLSFUNC /Y A:\DRIVER\COUNTRY.SYS >> KEYB.exe tr,857,A:\FREEDOS\keybrd2.sys /id:179 > Interesting that you specify a special variant of keyboard. > As mentioned earlier, you may want to use /NOHI for KEYB. >> VTUR > Your software gets started at boot automatically. > Finally, here is a full list of versions of used files. They > seem to be a bit old in general, but it is quite possible that > many files simply had no updates since then, as they already > had reached the desired state. > File sizes & versions root: >315 fdconfig.sys > 46685 KERNEL.SYS 2042 (build 2042 OEM:0xfd) [compiled May 11 2016] > 66945 COMMAND.COM 0.84-pre2 XMS_Swap [Aug 28 2006 00:29:00] > File sizes & versions freedos: > 233 fdauto.bat > 504 getargs.com reads memdisk command line > 510 hdd.bat textinst / postinst installer caller?? > 1024 xmssize.com 2005, checks free XMS > 1456 iniadd.com 2004, edits config > 1530 oscheck.com 2004, checks boot sector type > 2839 nlsfunc.exe 2004, version 0.4, /Y loads optional Y/N tables > 2977 append.exe 2004, appends search path for data files > 3657 DISPLAY.EXE 0.13b, loads custom fonts > 3759 localize.com 2003, shows translateable messages > 4149 choice.exe 2003, version 4.4, lets user make choices > 5861 DOSKEY.COM obsolete, command.com has functionality built-in > 6464 EGA.CPX from CPIDOS, with fonts 437, 850, 858, 852, 853, 857 > 11446 KEYB.EXE version 2.01 > 11681 sys.com version 3.6e > 13077 KEYBRD4.SYS keyboard definitions > 14395 VTUR.COM (your own software) > 16254 MODE.COM old 2005 version > 17049 USBKEYB.COM version 0.09 > 29722 KEYBRD2.SYS keyboard definitions > 30189 EDIT.HLP compressed help texts > 36640 KEYBRD3.SYS keyboard definitions > 40332 KEYBOARD.SYS keyboard definitions > 49264 srdisk.exe version 2.09 (Marko Kohtala's resizeable ramdisk) > 64046 EDIT.EXE (text editor) > File sizes & versions driver: > 1577 eltorito.sys version 1.4 > 2423 shsucdhd.exe version 3.01 > 2535 xdma.sys old version 3.3 > 2882 srdxms.sys version 2.09 (see above) > 3069 devload.com version 3.15 > 3745 xcdrom.sys version 2.3 > 4595 cdrcache.sys 2004 version > 5612 shsucdx.com version 3.03a (SHCDX33A) > 8058 himem.exe version 3.26, Aug 25 2006 > 15201 USBUHCI.OVL overlay for usbuhci > 16799 emm386.exe version 2.26, Aug 25 2006 > 20776 USBUHCI.COM version 0.14, apparently 2010 > 30250 country.sys data file for nlsfunc country specific settings > Maybe the others have additional comments on the used file versions! > Regards, Eric > -- > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/list
Re: [Freedos-user] How to
From: Tom Ehlert Kai, an amazing amount of effort to get a german keyboard driver :<< > Hi Eric, > thanks for the quick reply. In the meantime I found out that I can load a > German layout with just "keyb gr", just not the layout file itself or the > /E switch that is mentioned in that article. I assume the gr.kl is > embedded in the keyboard.sys file. > That's good enough for me. I don't need the Euro sign. I use FreeDOS > mainly on a USB stick for flashing bios and controller cards on rack > machines and my own workstations. And it drives me crazy if I have to > input some special characters like - _ / which commonly occur. Each time I > have to go by trial and error. And it seems you cannot type a ~ (tilde) at > all on a German keyboard under an en-us layout. > Now I can :-) > There is one thing still with keyb, though, that makes me wonder. > Shouldn't I be able to run it from autoexec.bat? I added "keyb gr" to it, > but it isn't executed (or it doesn't work at this stage). I have to run it > manually at the prompt. I'm also running keybw.com in autoexec.bat, right > before that. I don't know what that does. I just have it in there and > don't know if I added it some time ago or if it came with the first > FreeDOS configuration. Should I remove it? >> The KEYB layouts can be found here: >> >> http://www.freedos.org/software/?prog=kpdos > That's the point where the circle starts (and ends). There are no plain > keyboard layout files (.kl) in there, only the .key files. But these need > kc for compiling to a .kl file. And there's nowhere you can get kc from. in that case, KPDOS does not qualify as open source, and I recommend to remove KPDOS from future releases of FreeDOS > I don't need it now anymore it seems. But still wondering if it's really > not available from anywhere. >> Viel Spass! > Gleichfalls, von Berlin nach Berlin :-) > Kai instead I recommend http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/keyb/mkeyb/mkeyb041 zip and a command line KEYB GR (note: I'm the author) Mit freundlichen Grn#en/Kind regards Tom Ehlert +49-241-79886 -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to
From: Tom Ehlert Hallo Herr Kai Schaetzl, am 18. August 2016 um 15:31 schrieben Sie: > Tom Ehlert wrote on Mon, 15 Aug 2016 16:00:55 +0200: >> an amazing amount of effort to get a german keyboard driver > Not really once you know that you don't need the .kl file. > According to > http://help.fdos.org/de/hhstndrd/base/keyb.htm > you have to run (as an example) "keyb GR,,GR GR.KL /E". > You need the .kl file for this. > However "keyb gr" suffices. Just that it's not mentioned anywhere. As I > said I assume the GR layout is embedded in keyboard.sys, anyway. > With that in mind, it's the same as with your driver: download and run > "keyb gr". Anyway, just to see if there's a difference I changed now to > mkeyb. Both keyboard drivers work. > But I have the same problem with it. Adding "keyb gr" to autoexec.bat does > not run it. It seems autoexec.bat isn't executed at all. if something 'seems', add echo HELLO WORLD to the front of your autoexec.bat > Shouldn't it run > automatically once DOS is loaded? yes. as our clairvoyant has left us, how about posting CONFIG.SYS? > Thanks! > Kai Mit freundlichen Grn#en/Kind regards Tom Ehlert +49-241-79886 -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dma cr
From: Tom Ehlert > I keep getting the error-adma crosses 64k boundary when using tools > like rawrite3 or hard drive manufacturers tools floppy creation > software. I need to boot from Windows 98 bootdisk to get rid of it. > Please let me know if there is a way to get rid of this problem under FreeDOS. MSDOS redirects int 13 to an internal driver, detects DMA access crossing a 64k boundary, and avoids it. FreeDOS ddoes not do this; sorry. there was no need to do this so far; IMO rawrite3 could/should handle this by itself. of course, software is usually only tested against MSDOS, so there is little motivation to do so for rawrite3 programmers. I'm still surprised this comes up today, and not 15 years ago. do you have remarkable hardware? Tom -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedo
From: Tom Ehlert Hi, to reproduce this FIND problem, I tried to setup a new FD1.2 machine. what I did: download FD12LGC.ISO create a new virtual box machine with 512 MB disk use FD12LGC.ISO to boot the machine. boot machine. 'Unfortunately, this method of installation is not supported on this hardware platform. Please try a different installation method.' Welcome to the FreeDOS 1.2 operating system. now what? a hint to use the other .ISO would have been be helpful eventually I figured this out, and setup was successful. some remarks though: the setup results in FDCONFIG.SYS: 12:DOS=UMB makes virtually never sense. DOS=HIGH,UMB is always the better option. what purpose is SHARE supposed to have? SHARE is useful when the machine is running as a server, or with windows (or any other multitasking OS). don't install this. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] after
From: Tom Ehlert I could reproduce this. it happens in/after findnext() this error is related to the compiler. if the source is compiled using TurboC 2.01 the error occures. compiling the exact same source with TCPP the error is gone. try www.drivesnapshot.de/freedos/findtcpp.com and www.drivesnapshot.de/freedos/findtc21.com of course this can be a kernel bug, but as well a turbo library bug, or some sort of interference between them. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedo
From: Tom Ehlert > Why not use the CHOICE option-a to let the user decide? because 99,9 % of all user have no need for SHARE. > I have a > menu system which is designed to be used on a network and requires share to be loaded are really multiple machines accessing the same files at the same time? > IMHO this should be used of the FDNET option as well to allow users > to copy their specific packet driver to the /FDOS/NETWORK dir to > avoid an error msg after initial installation.. Tom > On Sat, Jan 21, 2017 at 6:21 PM, Jerome Shidel wrote: > Tom, >> what purpose is SHARE supposed to have? >> SHARE is useful when the machine is running as a server, or with >> windows (or any other multitasking OS). >> >> don't install this. > You are probably correct that it should load it by default. > I remrCOd it out for future releases. > Jerome > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user Mit freundlichen Gr|+|fen/Kind regards Tom Ehlert +49-241-79886 -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901) --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedo
From: Tom Ehlert Hello again, > Do you want to load FreeDOS High, UMB? there is no good reason (for normal use) to have ever DOS=HIGH,UMB disabled. if no HIGH or UMB memory is found, it is silently ignored. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901) --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] EtherDFS - a network drive for DOS
From: Tom Ehlert Mateusz, really cool. unfortunately I don't have a linux machine around, so testing must wait. may I suggest to use UDP/IP instead of raw packets? UDP/IP requires just a few bytes set up in the right way, and the calculation of the IP checksum; shouldn't be too much work. this would be much easier to use in multi-everything environments like linux or windows. specifically raw sockets are not available in standard windows many thanks anyway for starting this project Tom am 31. Januar 2017 um 10:19 schrieben Sie: > Hi all, > I write this short announcement to present an alpha version of a new > software I have been creating these past weeks. EtherDFS is an > "installable filesystem" for DOS. It installs a network drive that is > seen like any "normal" drive to DOS and its application, with the > exception that the actual data is located on a server. The server part is > called EtherSRV and currently only a Linux version of it exists. EtherDFS > uses raw ethernet frames to communicate with EtherSRV - this means only a > working packet driver is required, nothing else. > More information on the project's homepage: > http://etherdfs.sourceforge.net > I cannot stress enough the fact that this is an alpha version - it's in a > very early stage, and lots is to be done yet. It does work however, and > seems stable enough so it shouldn't make your PC explode. Its memory > footprint is quite huge for now, since its resident size is of 16 KiB. > Future versions will surely improve on that. Also, it *should* work with > MSDOS 5+, but I tested it only with FreeDOS so far. > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user Mit freundlichen Grn#en/Kind regards Tom Ehlert +49-241-79886 -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901) --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] bsum - compute BSD checksums of your files
From: Tom Ehlert >>> Unless I'm mistaken, conditional jumps on 8086 don't go beyond -128 .. >>> 127 (signed) byte range. Hence the billions of workarounds (TASM >>> "jumps", MASM "option ljmp", etc). right. >> I won't argue about what opcode is or is not available on 8086, since I >> did not bother decoding their exact meaning. meaning 'I am a lazy, clueless guy, but write anyway ...' >> I do see however that (NASM >> at least) can assemble JZ and JZ SHORT in two very different forms, JZ >> SHORT being significantly shorter. >> >> 5 B80100 mov ax, 1 >> 6 0003 48 dec ax >> 7 0004 746Ajz short gameover >> >> 5 B80100 mov ax, 1 >> 6 0003 48 dec ax >> 7 0004 7503E9DD01 jz gameover >> >> Of course NASM always uses the short form whenever it's possible, but >> when the jump is too far away it silently uses the longer form, hence the >> need to always specify SHORT if one wants to be sure what's going on. > AFAIK, meaning 'I am completely clueless , but offer my unfounded opinion anyway ...' > the longer one is 386+ only, hence not available with "cpu > 8086". Thus, if it still quietly assembles, that is a bug (but I > thought that was long-ago fixed/avoided). the longer one is 2 instructions instead, automatically generated by NASM because the intended jump goes farther then 127 bte c:\>debug -e 100 1430:0100 00.75 00.03 00.e9 00.dd 00.01 -u 100 1430:0100 7503 JNZ 0105 1430:0102 E9DD01JMP 02E2 Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901) --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS as a everyday/common-use system; Pros of making FreeDOS and Windows3 more compatible
> It's more possible than ever [0] to compile the kernel with GCC. 'This part of DJGPP is dedicated to the 16-bit tools that have been developed to assist in using DJGPP. Note: I lost interest in these projects before I completed them.' > Yes, it would be a large under taking but maybe a long term worthwhile Yes, as long as YOU invest YOUR time on this. > goal as OW has seem to lost a bit of steam. a reliable, proven compiler is all we need. we don't need a compiler with steam. btw, just in case you lived on a different planet for the last 10+ years, freedos also lost a bit (or all ) of steam, with the sole and remarkable exception of etherdfs, where some new, and even useful software was recently created. no, a new setup every 5 years doesn't count. > [0] http://www.delorie.com/djgpp/16bit/ Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] V8Power Tools -- Update
>> Hi Jerome, >> I've just tried your veach.com utility and it looks like it shall really >> come in handy! I was missing a program capable of appending a command to a >> sorted list (like a | in Unix ) . >> Nice job, and thanks for your effort > Thank you. > Just like you, I would find myself either doing some things the long way > because > there was just no easy way to do X on a list of things. Wether that list was > some > generic things I wanted to run through a program or something more complex. > Besides, what other utility will let suicidally run every program in a > directory with a > simple “veach /d *.* /c /x” command? :-) > I could have really used veach in FDI. But, I didn’t require it. With all the > ASCIIZ > string juggling and parsing it would need to do, I procrastinated making it. > But alas, > I finally got to it. veach /d *.bmp /x resize * /scale 50% is more or less the same as FOR %i in (*.bmp) do resize %i /scale 50% (use %%i when used in batch files) from a batch file, FOR has also lower memory requirements although this is most likely irrelevant for FDI unfortunately this turns up a bug in FOR: for %i in (*.*) do echo %i works as expected, also echoing the command itself. E:\FREEDOS\SRC>echo SOFTIC~1.IMA SOFTIC~1.IMA however for %i in (*.*) do @echo %i E:\FREEDOS\SRC>@echo SOFTIC~1.IMA Bad command or filename - "@ECHO". bug report filed Tom. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] New FreeDOSers Monthly Reminder
Hallo Herr John Price, can we please have this monthly remainder stopped? it is just unnecessary Tom am Mittwoch, 1. November 2017 um 07:00 schrieben Sie: > MONTHLY REMINDER FOR THE FREEDOS MAILING LISTS > Hello, and welcome to the FreeDOS mailing list! > If you have been a list member for some time, then you can skip this > as you should be familiar with the rules by now. > -- > The FreeDOS Project aims to create a free, complete implementation of > classic DOS. DOS is still a popular system, and plenty of people use > FreeDOS to play classic DOS games, run legacy software, and support > embedded systems. For more information about FreeDOS, visit: > http://www.freedos.org/ > We have only a few rules for posting to the FreeDOS mailing lists: > 1. Don't swear. We don't want this mailing list to become what Usenet >turned into. > 2. Keep posts on-topic. Remember, we set up this mailing list to >discuss FreeDOS issues. > 3. No flame wars. If you feel really strongly against what someone has >said, send a reply off-list. > Some suggestions: > ** Please send only plain text email messages, rather than messages >formatted in HTML. Plain text makes it easier for everyone to read >your posts. Above all, HTML email is particularly difficult for >some screen readers. > ** When replying to messages, please quote just the bit of email you >are replying to. Don't copy the whole conversation if you don't >need to. > -- > > > /* This is an automated message sent out to the mailing list at the > first of each month. It is automagically downloaded from > http://freedos.sourceforge.net/freedos/lists/remind.txt > Feel free to contact John Price if necessary by replying to this > message. */ > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Some driver updates
Dear Eric,
> Hi :-) Quick news from Jack's drivers: He has a closed
> source update for XMGR (more fail-safe 386 XMS move)
> and UHDD: The new UHDD has the interesting feature of
> read-ahead for cache sizes of at least 20 MB. It is
> a simplified version without I/O overlap and DOS RAM
> search table location and "/G" command line options.
> Sample copies can be requested from Johnson or Jack.
even closed, unfree, paid for software usually comes with a link so I
can find more description (rather then 'more fail-safe 386 XMS move'),
download it, see fee ( '25$ per PC'), limitations ('not for military'),
price and more.
but 'can be requested from Johnson or Jack', meaning
'on a good day, Jack might decide to send you a copy.
on a bad day, NOT.'
is the stupidest thing I have read for a long time.
this has no place on this list, and you should know that.
it's even stupider as most readers of this list have no email address
of Johnson or Jack.
just as a tiny side note:
I am only aware of 2 persons THAT CONSISTENTLY SHOUT.
Jack and the american president.
Tom
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Some driver updates
> Also, did you know that UMBPCI is actively maintained > and more reliable in finding out which areas can be > used for UMB etc. than JEMM / JEMM386? So it can be > a good idea to use explicit EMM options based on what > UMBPCI detected: This avoids more conflicts than the > easier method of letting JEMM / JEMM386 autodetect. interesting. can you try to contact Uwe Sieber if he would be willing to share his used memory detection logic. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Some driver updates
during the time that all these responses were written AND READ, competent programmers could -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Some driver updates
during the time that all the contributions in this thread were written AND READ, competent programmers could have ported the kernel to GCC, with some time left to save the planet, and fight for peace on earth. just my 2 cents. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Some driver updates
> What do these "Jack's Drivers" actually do? nothing as they no longer work on FreeDOS. btw: NEVER fullquote. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] SSH - unsupported remote protocol version
> On 12/31/2017 10:47 AM, Robert Riebisch wrote:
>> From SSHDOS source code:
>> ###
>>if(remote_major != 1 && remote_minor == 0)
>> fatal("Unsupported remote protocol version\n");
>> ###
> What a weird check. So version 2.1 would work? Shouldn't the check be
not only a weird and buggy check, this programmer could have given
some more - and helpful - information like
{
printf(
"Unsupported remote protocol version\n"
" this programm supports only SSL 1.0\n"
" the remote server requires %u.%u",
remote_major, remote_minor);
...
}
but he decided otherwise. May he live in peace and empty trash bins for
the rest of his life ...
Tom
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] counterproductive UPX usage for loadhigh display /maybe other drivers also/?
Hi,
> Hi, I just tried to 'lh display', but it always ends in conventional
> memory (code, codepages are perhaps in XMS):
...
> I myself explain this that the UPX-ed program is probably going to UMB,
> but after its decompression, its resident part will no longer fit there
> for some reason and is placed into conventional memory.
this is right. the .EXE header utility EXEHDR (there are many others)
reports (beyond other stuff) for the UPX'ed file
e:\>exemod y:\temp\BIN\DISPLAY.EXE
Microsoft (R) EXE File Header Utility Version 4.02
y:\temp\BIN\DISPLAY.EXE(hex) (dec)
.EXE size (bytes)E433651
>>>Minimum load size (bytes) 1F443 128067
Minimum allocation (para) 1E627778
after decompressing, minimum load size is much smaller
e:>upx -d y:\temp\BIN\DISPLAY.EXE
Ultimate Packer for eXecutables
Copyright (C) 1996 - 2017
UPX 3.93w Markus Oberhumer, Laszlo Molnar & John Reiser Jan 29th
2017
File size Ratio Format Name
-- --- ---
62535 <- 36515.84% dos/exe DISPLAY.EXE
Unpacked 1 file.
e:\ntsource\snapshot>exemod y:\temp\BIN\DISPLAY.EXE
Microsoft (R) EXE File Header Utility Version 4.02
y:\temp\BIN\DISPLAY.EXE(hex) (dec)
.EXE size (bytes) F447 62535
>>> Minimum load size (bytes) FEF7 65271
Minimum allocation (para) AD 173
fortunately, after recompressing with the current UPX, the minimum
required load size is only minimally increased, and still load high as
the uncompressed display.exe
e:\>upx y:\temp\BIN\DISPLAY.EXE
Ultimate Packer for eXecutables
Copyright (C) 1996 - 2017
UPX 3.93w Markus Oberhumer, Laszlo Molnar & John Reiser Jan
29th 2017
File size Ratio Format Name
-- --- ---
62535 -> 36435.83% dos/exe DISPLAY.EXE
Packed 1 file.
e:\>exemod y:\temp\BIN\DISPLAY.EXE
Microsoft (R) EXE File Header Utility Version 4.02
y:\temp\BIN\DISPLAY.EXE(hex) (dec)
.EXE size (bytes)E3B3643
>>> Minimum load size (bytes) FEFB 65275
Minimum allocation (para)F0E3854
> What is essential - if so, then this behavior should be IMO mentioned in
> the display documentation (or elsewhere).
wrong. this behaviour should simply be fixed, as the fix is trivial:
get a recent UPX.
decompress.
recompress.
wait for FreeDOS 2.0 to have this fix published.
some more remarks:
( I didn't look at the sources, so take this with a grain of salt)
12K resident is, even when loaded high, a significant number.
as the compressed .EXE size is just 3,5 K, the executable logic is
most likely ~5 KB size, and the other ~7 KB is buffer space to store font
information.
to move this font buffer to XMS memory shouldn't be a big deal, and
make up ~7 KB more UMB memory.
( in the good old times people would have killed for 7 KB memory :-)
as I have no interest in display.exe, I left this as an exercise to
the reader.
Tom
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] SSH - unsupported remote protocol version
> We did talk at length about it almost exactly a year ago. The tldr > version is that you would need ssh2d386 and you have to have access > to modify the ssh config on the server to support older ciphers. there are GOOD reasons to not allow outdated protocols to be used. on what planet have you been living the last years? > All my attempts to get a decent C coder interested in updating the project > have failed. > https://sourceforge.net/p/freedos/mailman/message/35629497/ I'm not surprised Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] You think BETA testing means you're brave?
> It's not FOSS but source is available here [0][1][2] for IMD. > [0] http://www.classiccmp.org/dunfield/dos/index.htm > [1] http://www.classiccmp.org/dunfield/dos/imd.zip > [2] http://www.classiccmp.org/dunfield/dos/imdsrc.zip besides other restrictions, this does not allow distribution. so this is not useful for FreeDOS, as FreeDOS is all about distribution. you should have read this BEFORE posting. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Now it gets odd Re: FreeDOS workaround for hidden IDE controller?
> I used CloneDisk to rip a RAW image of the booting DOM with > FreeDOS. Mounted that with Qemu. Booted Qemu with the FreeDOS > install image and installed FreeDOS to the image copied from the > DOM. Then I used CloneDisk to write that image back to the DOM. "Missing > Operating System". forget about this 'Install FreeDOS' thing. take the working DOM. delete 'SET LANG=FR' from config.sys and autoexec.bat replace command.com by the english version. this should at least still boot, and speak your language. everything else should already be in place as installed by your colleague Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Would you use a native 32/64-bit FreeDOS/BIOS system?
> There already is FD32 which puts FreeDOS and > a 32-bit DOS extender into the same file, I missed this. If you mean FreeDOS-32, they put 'FreeDOS and a 32-bit DOS extender' in the project name, but the source is unrelated to FreeDOS. If I'm wrong, please correct me. > but the improvements > compared to using a separate DOS extender (or just CWSDPMI) on > a normal 16-bit FreeDOS kernel seem to be limited enough as always said by these nasty experts... > that FD32 is still not nearly as popular as old FreeDOS afaik... if you are talking about FreeDOS-32, there has never been anything to download as a *user*. > I do appreciate having more 32-bit DOS extended DOS software, > but for 64-bit and multi core / multi CPU / > 3 GB RAM, you > would first have to suggest some really cool DOS use cases :-) whatever someone might suggest, 64-bit is simply not possible on top of a 16-bit OS Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Now it gets odd Re: FreeDOS workaround for hidden IDE controller?
> I used CloneDisk to rip a RAW image of the booting DOM with
> FreeDOS. Mounted that with Qemu. Booted Qemu with the FreeDOS
> install image and installed FreeDOS to the image copied from the
> DOM. Then I used CloneDisk to write that image back to the DOM. "Missing
> Operating System".
I just reread this post.
"Missing Operating System" is usually issued by the master boot
record, when no active partition is found.
is the DOM partitioned, or a raw ('superfloppy') medium?
Tom
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Trying to run a Dell bios update exe in FreeDOS 1.2
> Hi, > I'm trying to run a Dell bios update file for my Inspiron 7520. > I've created the FreeDOS usb stick, copy the bios update file to > it, can boot into it, return to DOS Prompt without installing, but > when I try to run the exe file all I get is (reproducing the FreeDOS screen > below): C:\>>7520A09.exe > Test. C:\>>_ > Nothing else happens! > What else should I do in order to run this executable? if you have trouble running a DELL executable, you should ask DELL support. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Trying to run a Dell bios update exe in FreeDOS 1.2
Hallo Herr Jim Hall, am Dienstag, 16. Januar 2018 um 22:17 schrieben Sie: > On Tue, Jan 16, 2018 at 3:10 PM, Mario Menezes wrote: >> >> I've to say that using a Windows PE iso (got from here >> https://toolslib.net/downloads/viewdownload/255-winpese-x64/) and LiveUSB >> tool (http://live.learnfree.eu/en/) to create the bootable pendrive I was >> able to run the firmware upgrade files. >> >> I'll still post to Dell community forums to have some official word from >> them with regard to DOS support as stated in their download page. >> Unfortunately, my notebook is quite old and its warranty has expired; so the >> community forums is my only way to contact them, I think. >> >> Once again, thanks for all your attention and help. >> >> Best regards, > Just curious: When you were able to run it, what was the output after "Test"? not so informative as the executable that runs from Windows PE is unrelated to the executable that runs from DOS (even if it is contained in the same .exe file). BTW: often BIOS updates require that no EMM386 (or similar stuff) is running. maybe just pressing F5 during boot, that 'skip config.sys processing' would have helped. but it's still a bug in the Dell executable to die silently without indication of the problem Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] (no subject)
> DOSEMU2 (Linux-hosted) is still being worked upon, and there have been > efforts to port the current FreeDOS kernel to GCC (with 16-bit support > patches). Since that (also) works on x64, the latest efforts should > again continue to prolong the lifetime of DOS programs, which is good > since even traditional BIOS/CSM will "probably" disappear by 2020. this is simply nonsense. a GCC compiled FreeDOS kernel will work *exactly* where the standard WatcomC compiled works; no more , no less (bugs aside). the GCC kernel is still 16 bit stuff, and requires a working BIOS. Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] [Announce]E100PKT 0.2 (stable)
Hallo Herr Seth Simon, am Donnerstag, 14. Juni 2018 um 03:27 schrieben Sie: > I've released version 0.2, which I consider stable, of E100PKT. > This version uses less memory, supports interrupt sharing, and > fixes many bugs. If you plan to upgrade from 0.1, please note > that version 0.2 cannot unload 0.1. > As always, more information and downloads are available at > gopher://sdf.org/1/users/sethsimon/e100pkt (or via > http://gopher.floodgap.com/gopher), as is a more detailed > changelog. Feel free to email me if you have any problems. for all of you who have no gopher client handy (as gopher is ridiculously outdated), try the public gopher proxy https://gopher.floodgap.com/gopher/gw?gopher.floodgap.com/1/world to access this gopher site and download the driver. shouldn't be necessary, but such is life Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] SLIP packet driver
Hallo Herr David McMackins, am Mittwoch, 1. August 2018 um 03:48 schrieben Sie: > Ah, it appears I should've looked past my nose. FreeDOS's own Crynwr > package has a SLIP driver. > Is using it as simple as just running SLIP8250.COM? If you don't know how to use a SLIP driver you most likely don't need one. I think that you are looking for something like ETHERDFS (easy copy files between 'server' and 'client') Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Memmaker
Hi Eric, >> 0aa5 10,464 (10K) IBMDSS14 device driver >> installed DEVICE=IBMDSS14 >> 0d34 25,824 (25K) IBMDOSCS device driver >> installed DEVICE=IBMDOSCS > What is the purpose of those? Are you sure to need them? how about googling this yourself? '31.03.2006 - The IBMDSS14.SYS, IBMDOSCS.SYS and DICRMU01.SYS files are PCMCIA Card and Socket. Services for the sample model IBM laptop.' >> Upper Memory is not accessible > I think it just falls back to loading low, but you can > explicitly change DEVICEHIGH into DEVICE to try out. it DOES fall back, no need to try. >> C:\WINDOWS\SMARTDRV.EXE /X > Are you sure that Windows SMARTDRV is a good cache for you? yes, absolutely. SMARTDRV beats all FreeDOS caches by a long shot. > It is not shown in your MEM output, does it fail to load? most likely because it refuses to work on FreeDOS ? >> Win /2 don't try to use WIN on FreeDOS; keep your working MSDOS. > So you use DOS only for Windows? Interesting. You > may want to check out the HXRT extender which can > run basic Windows software without needing Windows. AFAIK HXRT will run WinNT command line .PE executables; not WIn 3.1 executables. HXRT is not a WIN 3.1 replacement Tom -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] MS-DOS 1.1 and 2.0 ...now open source?
>> IIRC, the FreeDOS kernel is written largely in C, so the ASM source >> isn't directly usable. It may be useful to go spelunking for the >> algorithms used and how corner cases were handled. > It certainly can help to deal with issues that arise out of undocumented > features/bugs/issues, which in the past had to be re-implemented by > re-engineering or plain guess work... Frankly, not so much. the relevant facts about MSDOS like internal structures, memory layout aso. have been re-engineered/disassembled, documented and commented by Andrew Schulman, Mike Podanowsky, and MANY others, and merged in an almost complete (and almost correct) documented DOS API by Ralph Brown. thanks to them, and there is close to nothing to be learned by studying old MSDOS sources. there are not many 'algorithms' needed to implement xxDOS, and 'corner cases' (once you know there is such a case) are easily identified, and traced by either writing a small test program, or simply stepping MSDOS execution. Easier at least then trying to understand by reading MSDOS 2.0 sources. >> (Speaking personally, I'd love to see *FreeDOS* >> re-licensed under something other than the GPL.) > Now THAT is something I would agree with you, even if just to get rid of > Stallmanitis (thanks Tom! ;-) ) while I agree, this is not going to happen. a) there is no such thing as FreeDOS with a single license; even in my *really* minimum setup of kernel, command, himem you have 2 different licenses. b) even for the kernel alone, you have a dozen+ developers; at least one of them is dead. no way to have them agree to a different license. tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS on SSD
>> Can anyone recommend an IDIOT-proof method of installing FreeDOS 1.2 on >> a fixed SSD drive (with no OS) via one of several USB ports ? 1st, a fixed SSD behaves *exactly* like a ((fast) rotating disk. 2nd, I have no idea how much IDIOT you are, but most likely ANYDOS is not your best option to go. 3rd, I don't know if the freedos installation process is RAYMOND-proof, but it's the best we have to offer. > I don't have any SSDs, though, this might be true. > and you need an OS with "TRIM" support this is complete BS. (capital letters intentionally). (TRIM isn't useless, but it's not *needed* in any way) > It's just that overall DOS (sadly) has less hardware > support for such modern devices, and FreeDOS is no exception. SSDs don't need any support that is not already there: they behave like hard disks. Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS on SSD
Hallo Herr Raymond Bathurst, am Dienstag, 6. November 2018 um 09:51 schrieben Sie: > rufus will make a USB or a CF bootable with the PC (which has the > fixed SSD). The difficulty is making the fixed SSD bootable. The DOS > working files can be copied from a convenient USB stick. For some > applications DOS is far faster than the pixel-mapped systems. You > don't need a luxurious Mercedes to move a box of chocolates down the > road. Thank you for your comments. FDISKto create an active partition reboot FORMAT C: SYS C: Tom > De : Tom Ehlert > Envoyé : lundi 5 novembre 2018 20:31 > À : Discussion and general questions about FreeDOS. > Objet : Re: [Freedos-user] FreeDOS on SSD > >>> Can anyone recommend an IDIOT-proof method of installing FreeDOS 1.2 on >>> a fixed SSD drive (with no OS) via one of several USB ports ? > 1st, a fixed SSD behaves *exactly* like a ((fast) rotating disk. > 2nd, I have no idea how much IDIOT you are, but most likely ANYDOS is not > your best option to go. > 3rd, I don't know if the freedos installation process is > RAYMOND-proof, but it's the best we have to offer. >> I don't have any SSDs, though, > this might be true. >> and you need an OS with "TRIM" support > this is complete BS. (capital letters intentionally). > (TRIM isn't useless, but it's not *needed* in any way) >> It's just that overall DOS (sadly) has less hardware >> support for such modern devices, and FreeDOS is no exception. > SSDs don't need any support that is not already there: they behave > like hard disks. > Tom > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS on SSD
>> Trim sounds like the old standard "defrag program" which should >> be unneeded for flash since all bits get accessed at the same speed. >> No spinning disk to move around on. wrong. > Trim is used for equal usage of memory-cells. It is a mechanism to > support round-robin usage of those cells. wrong, too. the drives firmware is responsible to round-robin usage of those cells anyway. it works even on (almost) full disks, too. with an OS that doesn't support TRIM, after a while the drive thinks that all sectors are in use as they have been written at least once. TRIM (capital letters) is a way for the OS to tell the drives firmware which sectors are no longer in use. round-robin usage is made easier if there is more free space available, but works even on completely full disks as the disk always reserves some space for internal use that is not visible on the outside. lookup overprovisioning. Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Updates to FreeDOS wiki
> Not sure how to fold in the "16bit v 32bit" section or the "UEFI" > section, but I may add a section at the bottom of "Releases" that > talks about this (probably "Features" or "Assumptions") just to have > everything in one page. "16bit v 32bit": I took the time to look into what the night dos kernel group has achieved so far in the 3+ years that it exists. simple conclusion: this not going to be a DOS kernel. ever. what they describe as goal is some sort of OS/2, WINDOWS 3.11 for work groups, or similar. multitasking, DOS compatible (and redefine the desktop metaphor ;). at the same time all the source indicates that they are newbie programmers, and also completely new to 8086 assembler, but insist on doing all work in assembly. this project is not going to succeed, at least not with these people, and not in our lifetime. my vote: remove from road map. "UEFI": your argument is wrong. a BIOS emulator on top of UEFI is possible. this would load the FreeDOS boot sector, everything else as normal. practically people able to fulfill such (very advanced) stunt are usually not motivated to spend a year of their life on obsolete stuff. insofar my vote: "not going to happen unless a white knight in shiny armor shows up. don't hold your breath." Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Updates to FreeDOS wiki
Hi Eric, >> I took the time to look into what the night dos kernel... >> what they describe as goal is some sort of OS/2, WINDOWS 3.11 > While their goals are noble, I doubt that they will achieve good > compatibility with most DOS stuff. And I agree that they should > use more C in their code to avoid getting lost in details :-) >> my vote: remove from road map. > My vote: Treat as a friendly project, not part of a DOS distro. no. friendly projects should provide at least a little bit of 'good to know'. https://sourceforge.net/p/freedos/news/2018/08/night-kernel-development-effort/ "While Night Kernel is far from their goal, the project has been making steady progress." this made me interested in their status and progress, and I wasted some hours trying to locate this steady progress. just believe me: 'making steady progress' is only true if you take interesting drugs. don't get me wrong: it's absolutely fine to have 'programming operating systems in assembly' is your beloved hobby. but this doesn't qualify for 'friendly project'. Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] MKEYB 0.43 has been updated
MKEYB has been updated, the slovenian keyboard has been corrected and verified by Fritz. http://www.drivesnapshot.de/freedos/mkeyb.htm Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Using a timer with an ISR in watcom
> Just out of curiosity, if I write something for a DOS4GW 32bit > environment, would I choose the same way for having a timer or are there > better ways for having a timer callback function? the idea will be the same, the routines to use are different. > For a later experiment project I want to capture parallel port data on a > Pentium 3 which is very fast compared to a parallel port's speed. > I thought about having an ISR capturing the data being called at capture > rate, which should be something around 100kHz to 150kHz unlikely. expect *each* inp()/outp() operation to use O(500ns) there is also a notable delay between applying an input 0/1 voltage, and this voltage available as inp() usually people read until 2 readings are identical. try polling first to get an idea what input rate will be possible. > to get a hard > real time measurement. don't mix 'fast measurement' with 'real time, deterministic measurement'. DOS is anything but hard real time. > Are there any interrupt priorities interfering with this concept? in a DOS environment, the current interrupt will be served until finished. so any incoming interrupt (USB, keyboard, mouse) will defer your input routine until done. > There should be plenty of time on this machine to process data after > capturing from parallel port. yes. with real time linux. Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Agilent e5061a and e5071b...
Hi, > The Agilent e5061a belongs to the company I'm working for and is > only two channel. this mailing list is about FreeDOS, and not the Agilent e5061a or Windows 2000 support group. you may help him, but please do so on private channels; the FreeDOS community is not going to learn anything out of this discussion. thanks Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Windows 2000 fat32 and freedos...
> FreeDOS began as an effort to create an open source version of 16 bit > DOS, compatible with what Microsoft issued. It largely succeeded in > that effort. exactly. > Providing the support you want is serious system level programming. > The folks who *can* do that get *paid* for it. Tell me why anyone > might do it for free? > Unless you know folks who *can* do it who would be willing to > contribute it for free, or have the money (or know folks who do > willing to contribute it) to *pay* for having it done, I'm afraid you > face an uphill battle. actually there are (or were) some folks who *can* and do this for free. that's how freedos got here with only very few bugs left (lfndos doesn't count). now (most of) these folks went ahead to more interesting problems Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Windows 2000 fat32 and freedos...
> The two aren't currently compatible. Any chance of lfndos getting > the bugs ironed out? lfndos is known to be buggy. use doslfn http://sta.c64.org/dosprg/doslfn.zip instead. Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] New FreeDOSers Monthly Reminder
> I can't find an unsubscribe link to FreeDos. Could you point me at that, or > take me off of the list? not really your fault as https://www.freedos.org/lists/ has text that looks like a link (: Mail-archive http://www.mail-archive.com/freedos-user@lists.sourceforge.net/) und other fields that don't look like a link, but are. click the innocent looking Freedos-user http://lists.sourceforge.net/lists/listinfo/freedos-user and you land at the subscribe/unsubscribe page Tom > Thanks, > - Steve Owens > On Sat, Jun 1, 2019 at 1:01 AM John Price wrote: > > -- > We have only a few rules for posting to the FreeDOS mailing lists: > 1. Don't swear. We don't want this mailing list to become what Usenet > turned into. > 2. Keep posts on-topic. Remember, we set up this mailing list to > discuss FreeDOS issues. > 3. No flame wars. If you feel really strongly against what someone has > said, send a reply off-list. > > -- > /* This is an automated message sent out to the mailing list at the > first of each month. It is automagically downloaded from > http://freedos.sourceforge.net/freedos/lists/remind.txt > Feel free to contact John Price if necessary by replying to this > message. */ > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Find command and a drive
Hallo Herr Jim Hall, am 25. Juni 2019 um 22:16 schrieben Sie: > I don't see this bug reported in the bug database, so you seem to > be the first person to discover this bug? That's pretty amazing, > since the bug appears to have been in there since at least 2007 (latest > version). > https://sourceforge.net/p/freedos/bugs/search/?q=find > I can reproduce the bug this way: (default FreeDOS 1.2) > COMSPEC=C:\FDOS\BIN\COMMAND.COM > PATH=C:\FDOS\BIN whatever the reason for the bug is/was: just (re-) compiling find.com with Turbo C++ Version 1.01 makes the bug go away. strange enough, nobody ever tried to compile FIND from the source as the makefile requires some file lfnchk.asm that is neither there nor required. (but possibly in the io95.lib. I didn't check) when the makefile is changed to ignore this missing file, the resulting FIND.COM runs without (immediate) problems. both are available from www.drivesnapshot.de/freedos/find.zip Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] why isn't anyone answering my question?
> On 7/17/2019 4:41 AM, kaye n wrote: >> My apologies. Wrong choice of words. I am aware that this is not a >> paid support line. >> >> Anyway, here's my question. >> >> I have a desktop computer running a Linux distro. In this LInux distro >> I have installed VirtualBox, and in this VirtualBox I have installed >> Freedos. >> >> The virtual Freedos is running fine. However I can't figure out a way >> to allow the virtual Freedos to access the different partitions of the >> hard drive (for example an NTFS partition that contains my personal >> data), as well as any USB flash drive. >> >> Is this impossible if the Freedos installation is only virtual? > That is a VirtualBox issue, not a FreeDOS issue. V/B needs to provide a > pass-through to the partitions that you want to access. they have that for more recent operating systems like OS/2 or better. as VirtualBox is open source, feel free to provide a DOS client ;) > Beside that you > will have problems with accessing a NTFS partition of said pass-through > in a network-redirector way... why do you think that? this has clearly been done by a) network redirectors like LANMAN and b) MS VirtualPC even had a client for DOS, working flawlessly. Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] HP laptop touchpad
> I agree about trackpads, they’re awful. The only port this thing > has is a USB port and a usb mouse didn’t really fare any better than > the trackpad, and I don’t think cutemouse supports usb mice either. most likely your trackpad is connected to the motherboard via an internal USB port, just like your keyboard. this stuff is no longer connected through PS/2 ports. most 'modern' BIOS support 'legacy' support for keyboard, mouse, otherwise you wouldn't see any mouse movement at all. of course this doesn't help you :( Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] bugs in XDEL command included with 1.3 RC1
> I assume these are known problems with the XDEL command in version > 1.3 RC1, but this regards two situations: not at all. at least some of these problems seem to be introduced during port Borland C --> Watcm C (in 2005; XDEL seems to be not so intensly used) > 1) where you want to delete all files of the same extension that > exist one folder level down from where you execute the command. It > does not delete the files, at least in the situation where the > directory name contains an extension (ex: WPTAIL.UNI directory in > FreeDOS\AppInfo). To get around that problem I used the DIR /B /S > *.* > delete.lst command to create a barebones list of files to be > deleted using the '@' option. That did work. what is the exact command that fails? > 2) the next thing I tried to do is delete all the empty directories > with the .UNI extension using the command XDEL *.UNI /D. That does > not work as upon execution, the command always truncates the last > letter of the extension. So when it gets to deleting WPTAIL.UNI, it > reports that it cannot delete WPTAIL.UN (which does not exist). I > renamed directory to WPTAIL.UN thinking that will work but it > results in a report it cannot delete WPTAIL.U, and when you rename > by removing the extension entirely, it says it cannot remove the > directory name (which is finally correctly represented). caused by file[strlen(file)-1]=0;// remove final '\\' > Related to the first issue with XDEL is that when trying to delete > all instances of a filename in subfolders (using a wildcard), the > prompt does not come up until AFTER I hit enter or another key. In > other words, the action I take precedes the prompt and the command > terminates without the answer to the prompt being received by the program. it looks like Watcom buffers stdout, and Borland doesn't Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] bugs in XDEL command included with 1.3 RC1
> Example of the exact command that failed was "xdel /s *.uni\*.de": I located the original 22 may 2002 from original author even this can't XDEL /d *.uni and xdel /s *.uni\*.de > Definitely broken command, seems like. exactly. should be fixed by someone with more motivation then me, or removed from any distro. what exactly is the point to distribute broken, undebugged programs? Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Source code to Windows 9x and ME...
> Freedos should be capable of supporting Windows 3.1, at least in > standard mode. AFAIK it does (not that it was ever important for the developers). > Wouldn't it be great if freedos could support that better and 3.11 as well > along with a lot of programs from that era? just organize your millions of $, and we will organize the programmers ;) > Maybe source code won't help, but > the interfaces and other engineering information could be quite useful for > someone trying to support programs designed for Windows 16 bit. That said, > Win32 based programs are of interest to anyone who needs to run them in a > dos based environment. in theory, that's possible. there was a Win32S emulation layer for win3.11. in praxis, even more M$ required. this simply no going to happen. > There is a lot of industrial software that depends > on a combination of MS-DOS 6.22 and Windows 98 SE. definitively no. Windows 98 SE never ran on top of MSDOS 6.22. and even if it would: this software has run for 20+ years, and should run many more years. on of the best properties of software is that it doesn't rot. > There is also the potential that freedos can run this old > software on newer hardware that isn't 20+ years old. The biggest problem > with 98se/ME is that there aren't drivers for hardware that is newer than > the Pentium II pretty much. I simply don't know if Win98 requires any drivers for the CPU. but I do know that neither MSDOS 6.22 nor FreeDOS (or any other DOS) have any drivers for any CPU. so running FreeDOS on a I7-9060 doesn't help you a little bit with Win98 and your funny machine. > Getting an industrial PII on a single board for a PICMG 1.3 backplane or an > ISA backplane, that is probably the best bet for the pick and place machine > we want to get up and running. yes indeed. > The machine is worth $20k-$30k. Yes we > could pull the two heads and try a set of heads based on Windows 7, but > that is nearing EOL already. don't put your Windows 7 on the internet, and it will live happily for 20 more years. your Win98 machines are EOLed for 15 years, and nobody cared. > I'd say that my brother's > machine is worth at least $15k right now. As you say it, $15k sounds like much. translate this to programmers hours and it goes away fairly quick. Tom ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Source code to Windows 9x and ME...
> The comment that a pick and place machine designed around MS-DOS 6.22
> and Windows 9x/ME is a funny machine is a little disingenuous.
> Freedos didn't exist in a useable form back then and Windows 9x/ME in
> it's day was dominant.
I surely didn't want to insult your amazing machine; sorry.
I still wonder why you don't port the control software to newer
versions of Windows (should this be necessary)
> Does Microsoft
> Scandisk for Windows 98se work on freedos?
no. no MSDOS utility runs on top of anything else.
there is code similar to
if (GetOSVersion() != 6.22)
printf("wrong operating system");
exit(1);
in all utilities.
> I'm hopeful too that we can use at least Windows 2000 on the gui.
> There is no direct replacement for Windows 98/ME. These systems are
> very resource hungry and only moderately stable.
yes. there was a reason they went out of business.
Tom
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
