Re: [Freedos-user] error-message with the find command
Hello Jim,
thanks very much for your reply.
I see. Well, that´s good to know.
Not that it bothers me in any way at all. I just wanted to know if that
behaviour was to be expected (at least in version 1.2.)
I hope to be able to download FreeDOS version 1.3 soon.
I was looking around a bit on https://www.freedos.org/download/ and
found out that the live CD should be a 375//MB//download/.
/I hope this should be enough for taking the first steps as the Bonus CD
weighs in at about 621 MB.
Thanks a lot again for your kind help.
Many greetings from Rosika
/
> From Jim Hall://
//
/
/That was a bug in that version of FIND in FreeDOS 1.2. This was fixed
in FreeDOS 1.3. Here's an example showing that I really don't have a
floppy drive ("A:") so I get the error if I try a DIR but I don't get
the error with FIND. This uses FreeDOS 1.3: C:\>dir A: Error reading
from drive A: DOS area: unknown command given to driver (A)bort,
(I)gnore, (R)etry, (F)ail? File not found. - 'A:' C:\>find "hi there"
FDAUTO.BAT FDAUTO.BAT/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] error-message with the find command
Hi all, I have _*FreeDOS 1.2*_ running in a virtual machine (KVM/qemu). My host is Linux/Lubuntu 20.04.4 LTS, 64 bit. There´s one "mystery" regarding FreeDOS though. Here´s an example to demonstrate the "problem": I have a text-file, say "try.txt". What does work are the commands "type try.txt" and also "more try.txt". When searching for a certain word within the text (example: find "search-word" try.txt) it works as well. The instances of lines containing the search-word are displayed. However: At the end I get the following message: *"Fehler beim Lesen von Laufwerk A: im DOS-Bereich: Allgemeiner Fehler** **(A)bbrechen, (I)gnorieren, (W)iederholen, (F)ehler?"* The output is in German, so the English equivalent should be something like: *"Error reading from drive A: DOS area: general error** **(A)bort, (I)gnore, (R)etry, (F)ail?"* Trying to cd into A:\ yields the same message. My guess is drive A:\ doesn´t exist in my VM at all. My working directory is C:\ . So my questions are: Am I right in assuming that drive A:\ is non-existent ... ... and why is it that the find-command produces the error message but not the type and more commands ? Thanks a lot in advance for your help. Many greetings Rosika ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] FreeDOS in qemu: no internet-connection
Hi altogether, I want to get *FreeDOS* going within *qemu*. Quite a long time ago I downloaded the respective iso-file and the installation went well. In principle *FreeDOS* works fine with the exception of networking. I simply can´t get qemu to let *FreeDOS* connect to the internet. (Formerly I could; see below). My command-line is: qemu-system-i386 -m 32M -drive file=drivec.img,media=disk,format=raw -net nic,model=ne2k_pci -drive file=FD12CD.iso,media=cdrom -boot order=d According to the instructions on http://wiki.freedos.org/wiki/index.php/Networking_FreeDOS_-_Quick_Networking_HowTo I installed FDNET, mTCP and wget in FreeDOS. So things should work. Yet they don´t (any more). When starting FreeDOS everything looks right at first: QEMU network detected DHCP request sent, attempt 1: Offer received, Acknowledged Good news everyone! IPADDR = 10.0.2.15 NETMASK = 255.255.255.0 GATEWAY = 10.0.2.2 NAMESERVER = 10.0.2.3 LEASE_TIME = 86400 seconds That used to work in the past. But things seem to have changed as of late: When trying to use ping or the links browser internet connection doesn´t seem to be established: configuring through DHCP...failed configuring through RARP...failed error loading ... URL Host not found I dont know whether it has something to do with the fact that my means of connecting to the internet has changed in the meantime. I used to use a 3G-umts-stick (Huawei E 1550) , which was recognized as a modem and used "*ppp0*". My new 4G-stick is Huawei E 3372 and this one seems to work as a *router*; so my internet connection is recognized as *LAN* (wired) connection. I´m guessing I have to change some settings in C:\FDOS\WATTCP.CFG, but I´m not quite sure. Can anybody help me , please? Many thanks in advance. Many greetings. Rosika P.S.: my system (host): Linux/Lubuntu 20.04.4 LTS, 64bit FreeDOS 1.2 ___ 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, what kind of Dell do you have? Do you know their support page? There is a tutorial how to flash the Bios with FreeDOS or with a Linux system installed: https://www.dell.com/support/article/de/de/debsdt1/sln171755/updating-the-dell-bios-in-linux-and-ubuntu-environments?lang=en Hope it can help you. Best regards Christian -- 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] Catch "rd" order before command.com processing
Hey guys! >> Nevermind my answer. This may work directly from prompt but not from >> within my program. I guess I need to do it in command.com. So can you > >recommend any good documentation on how to compile freecom and maybe which source? > > Is this program something you wrote or somebody else? Is it closed source? Because this is really sounding like some extreme (i.e. not > recommended) workarounds for a flawed design. > > You can recompile FreeCOM, but I wouldn't recommend it. I'd suggest you fix your program (if at all possible). Of course, that may not be feasible. > Well there is really no way I can get the scource of this program. It was written before my time without proper version management and I only have got the newest scource and there is unfortunately no possibility to get the one I need... That's why I was looking for some kind of workaround but of course recompiling freecom was not the answer I was hoping for :). Anyway thanks for the helpful resources, I'll take a look! > I would seriously recommend against doing so. One typo, like an accidental space after the directory slash(es) and you wipe out far more than you intend, without any safeguard against it. It's pretty much like taking a shotgun with buckshot to shoot yourself in the foot. "Ab is' ab..." Thanks for your concern but it's only dispensable data and the automatic call through the program should not cause errors but you'll never know. Actually I found an additional protection in deltree which spoils unintended deletion of data from root directory. However as "alias" is only working in prompt it won't matter I guess (or maybe it will if I am going for the freecom compile...) -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Catch "rd" order before command.com processing
Nevermind my answer. This may work directly from prompt but not from within my program. I guess I need to do it in command.com. So can you recommend any good documentation on how to compile freecom and maybe which source? -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Catch "rd" order before command.com processing
Hey Louis! Thanks for your quick answer which helped me alot! Actually I just copied deltree.com to my C: directory and put in my autoexec.bat alias rd=C:\deltree.com /y Now when I do “rd C:\directory\directory2” it deletes the specified directory. I know it’s a pretty dirty solution (especially dangerous with /y switch) but I guess this works out for me :). Open for any suggestions! Regards Hans Von: Louis Santillan [mailto:lpsan...@gmail.com] Gesendet: Dienstag, 29. März 2016 17:40 An: Discussion and general questions about FreeDOS. <freedos-user@lists.sourceforge.net> Cc: Christian Koch <c.k...@scheerkoch.de> Betreff: Re: [Freedos-user] Catch "rd" order before command.com processing del C:\directory\*.* rd C:\directory Even that will fail, I think, if there are some hidden files/folders. Start with that and you can build it into an alias command in freecom. alias myrd="del %1%\*.* ; rd %1%" I believe that's the right syntax. -L On Tuesday, March 29, 2016, Hans-Christian Koch <hc.k...@scheerkoch.de <mailto:hc.k...@scheerkoch.de> > wrote: Hey all! Once again I am trying to run some old programs under Linux emulation DOSEMU which is making use of FREEDOS. In one of them you have the option to delete directories, it does it like this: del C:\directory\*.rec del C:\directory\*.dat del C:\directory\eti.bin rd C:\directory As “rd” only removes directories if they are empty the folder to be removed must only contain files of types .rec, .dat and a file eti.bin else it won’t be removed. My problem is that today there are some other files in this folder too so I can’t remove it from within my program. The appropriate way to delete directories would be ‘deltree’ I guess but that’s a standalone .com program while rd and del are part of command.com <http://command.com> . I tried to create a file rd.bat which should catch the call but if I do “rd.bat” freedos wants to remove the directory “.bat”. Is there any way to get a workaround to this or how can I compile my own version of command.com <http://command.com> ? Thanks Hans-Christian -- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos V2.0 - when will it be available?
Hi Alain, sorry for my late response. I downloaded your VM on the day you talked about it here on this list and tested it in VirtualBox. I found it really interesting. Thank you very much for your work. Lubuntu started very fast and the integration of Dosemu and FreeDOS looks interesting. Do you have any notices or tutorial how you adept your Lubuntu for your special distro? I have a similar project but I use a dual boot FreeDOS and TinyCore Linux and in TinyCore I use Dosbox to get access to the FreeDOS partition. After I saw your version I am thinking about to change TinyCore with your adepted Lubuntu. But I am not sure about the Linux kernel in Lubuntu because Canonical thinks about to use a 64 bit kernel only in the near future and some current kernel had problems with non PAE CPUs. Maybe Debian or a derivat like Knoppix is the better choice? But how I said I am not sure. And sometimes I am thinking about using a different OS than Linux, maybe FreeBSD with FreeDOS? ;-) Or ReactOS and FreeDOS, so FreeDOS can support ReactOS where it has problems and ReactOS can use 32bit hardware on the installed computer, if the Windows driver is working. We will see. Best regards Christian Am Mi. Dez. 30 19:33:39 2015 GMT+0100 schrieb Alain Mouette: > ??? > I just made this experimental in a VirtualBox VM and it arouse no > interest here... > > Alain > > On 30-12-2015 14:47, Aitor Santamaría wrote: > > +1 to this idea > > > > > > On 9 January 2013 at 20:54, Jim Hall <jh...@freedos.org > > <mailto:jh...@freedos.org>> wrote: > > > > >> A hypervisor that can run dosbox and make modern hardware work > > >> with old dos programs anyone? How about dosbox running on a > > Pentium 133 > > >> or a Pentium 166 machine with 16 megs of ram? > > > > > > Insufficient demand to justify the effort. > > > > > > There may not be a lot of demand, but I see it as an interesting hack > > for someone to try. > > > > Actually, I proposed something like that a few years ago: create a > > custom Linux "spin" (mini-distribution) that boots a minimal > > environment, and starts up DOSEmu on virtual console 1, immediately > > booting a copy of FreeDOS. Maybe you can even provide the option to > > start additional DOSEmu+FreeDOS instances on the other virtual > > consoles, just by connecting to them and "logging in" (probably by > > pressing Enter). > > http://www.freedos.org/jhall/blog/?id=20090422-143518 > > > > I don't know if it's possible to run multiple console DOSEmu instances > > on the same box, since I've only ever tried to run one (and XDOSEmu at > > that). Yes, that's overkill for booting DOS on a modern computer, but > > an interesting idea. > > > > > > -- > > Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, > > jQuery > > and much more. Keep your Java skills current with LearnJavaNow - > > 200+ hours of step-by-step video tutorials by Java experts. > > SALE $49.99 this month only -- learn more at: > > http://p.sf.net/sfu/learnmore_122612 > > ___ > > Freedos-user mailing list > > Freedos-user@lists.sourceforge.net > > <mailto: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 > > -- Gesendet von meinem Jolla -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] question ISO/DATA
hi everybody don t know if i m on right mailing list but i ll explain my trouble. i try to flash my bios on my Medion PC motherboard MS 7358 i retrieve the data on medion web site. so i made a freedos ISO with my flash bios data. i install : first i try to run on cd with prompt i launch my awardflash bios message : not enough memory well so i install FREEDOS after 10 attempts i did it (needed to copy command.com by myself from FDOS/packages to FDOS/BIN he never manages to install it). btw in the 10 attempts i kill my seven partition (don t know how but nevermind) so i copy the data from CDrom on my local drive and launch my award flash bios. it says to me file size do not match. so my question is : ISO file extracted are not same size as Data extracted ? for the answer : i ll try tonight or in the week to burn a cd with only my ddata in data mode and copy on my FREEDOS partition. if someone has the answer before i attempts something tha tkill my pc =) thanks -- Leborgne Christian -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] question ISO/DATA
Hi im usin imgburn ans ultraiso to modify m'y ISO. Le 19 oct. 2015 7:06 PM, Don Flowers <donr...@gmail.com> a écrit : > > When you are making the iso what kind of bootable image are you using? For a > blank CD, I use FDOEM.144 from here: > > http://www.fdos.org/bootdisks/ > > Then I add the drivers for the PC I want to be able to boot since so many new > PCs require different various drivers to boot into a DOS environment. Once I > am sure that I have the right startup disk, I create an image of the diskette > and use that image as my boot image when I create the ISO. For a BIOS update > you don't usually need a memory driver, you just want to boot successfully > into a FreeDOS environment. > > > > On Mon, Oct 19, 2015 at 8:16 AM, Leborgne Christian <flashouill...@gmail.com> > wrote: >> >> hi everybody >> don t know if i m on right mailing list but i ll explain my trouble. >> >> i try to flash my bios on my Medion PC motherboard MS 7358 >> i retrieve the data on medion web site. >> so i made a freedos ISO with my flash bios data. >> i install : >> >> first i try to run on cd with prompt i launch my awardflash bios message : >> not enough memory >> well >> so i install FREEDOS >> after 10 attempts i did it (needed to copy command.com by myself from >> FDOS/packages to FDOS/BIN he never manages to install it). >> btw in the 10 attempts i kill my seven partition (don t know how but >> nevermind) >> so i copy the data from CDrom on my local drive >> and launch my award flash bios. >> it says to me file size do not match. >> >> so my question is : ISO file extracted are not same size as Data extracted ? >> for the answer : i ll try tonight or in the week to burn a cd with only my >> ddata in data mode and copy on my FREEDOS partition. >> >> if someone has the answer before i attempts something tha tkill my pc =) >> thanks >> >> >> >> -- >> Leborgne Christian >> >> -- >> >> ___ >> 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] Is anyone installed FreeDOS from USB CD drive or other USB device?
Hi, just for correction: I have moved FreeDOSmultiboot.zip from Github to my web space and deleted the outdated Repo on Github: http://www.datenteiler.de/install-freedos-1-1-with-freedosmultiboot/ FreeDOSmultiboot can boot a FreeDOS Boot Disk, the FreeDOS Installation CD and Tiny Core Linux 6.4 from a pen drive. It should work with 486 PCs and greater. Best regards Christian Am Mon, 01 Sep 2014 13:07:09 +0200 schrieb "Matej Horvat" <matej.hor...@guest.arnes.si>: > How did you write the ISO image to the flash device? Maybe you can > try Rufus: > > http://rufus.akeo.ie/ > > Don't choose the FreeDOS option (that will only make a bootdisk with > nothing else), instead choose the ISO option and select the FreeDOS > installation CD image. > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > 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] Init: Coult not access packet driver at INT 0x60
Hi, I am using PCNET in Qemu. I start the VM with whis command: qemu-system-i386 -m 128 -hda 'qemu_freedos.img' -net nic,model=pcnet -net user,hostfwd=tcp::5554-:21 -localtime -boot c Among others I have these two lines in my "autoexec.bat" (pcntpk without LH): pcntpk INT=0x60 dhcp I use port forwarding with "hostfwd=tcp::5554-:21" to build a FTP connection between guest and host. If the FTP connection wit ftpsrv is established I can ftp'ing into the FreeDOS box from my Linux host with: $ ftp localhost 5554 Network and Qemu is a little bit tricky. To show this, I want to quote the QEMU Emulator User Documentation: "The QEMU VM behaves as if it was behind a firewall which blocks all incoming connections. You can use a DHCP client to automatically configure the network in the QEMU VM. The DHCP server assign addresses to the hosts starting from 10.0.2.15. In order to check that the user mode network is working, you can ping the address 10.0.2.2 and verify that you got an address in the range 10.0.2.x from the QEMU virtual DHCP server. Note that ping is not supported reliably to the internet as it would require root privileges. It means you can only ping the local router (10.0.2.2)." http://wiki.qemu.org/download/qemu-doc.html Hope that helps. BTW: I think the installation of FreeDOS with network support in VirtualBox is easier: http://freedos.sourceforge.net/wiki/index.php/VirtualBox Best regards Christian Am Mon, 14 Sep 2015 09:29:12 -0700 schrieb Louis Santillan <lpsan...@gmail.com>: > The qemu wikibook [0] also lists NE2000, Intel e1000 and AMD PCNET as > being optionally emulated. Drivers for those & the rtl8139 can also > be found here [1]. According to qemu networking setup wiki book [2], > the e1000 is the default. > > > [0] https://en.wikibooks.org/wiki/QEMU/Devices/Network > [1] http://www.georgpotthast.de/sioux/packet.htm > [2] https://en.wikibooks.org/wiki/QEMU/Networking > > > > On Mon, Sep 14, 2015 at 6:05 AM, Mateusz Viste <mate...@viste.fr> > wrote: > > The fact that your network card is virtualised doesn't matter, the > > guest OS doesn't know about that. You need to emulate a real-world > > network card, and find a packet driver for it, just like if it > > would be real hardware. > > > > "qemu -device ?" shows the list of supported devices. With a quick > > look I see a "rtl8139" position, and that's a card for which a > > packet driver exists. You can get it here: > > gopher://gopher.viste.fr/1/hardware/network/Realtek/RTL8139 > > > > You might want to test other options though, because the Realtek > > packet driver is quite RAM-hungry (26K). For comparison, the 3C590 > > packet driver from 3Com consumes only 11K. > > > > Mateusz > > > > > > > > > > On 14/09/2015 14:54, soko.tica wrote: > >> Hello list, > >> > >> I have installed freedos on qemu (both x86_64 and i386), but cannot > >> start the networking. > >> > >> C:\>dhcp.exe > >> > >> mTCP DHCP Client (by M Brutman ) > >> > >> Init: Coult not access packet driver at INT 0x60 > >> Could not initalize TCP/IP stack > >> > >> Since this is installed on Qemu, which is an emulator, I don't know > >> where to find the appropriate driver, or how to configure it > >> properly. I could not find the answer in the chapter Packet driver > >> installation > >> http://freedos.sourceforge.net/wiki/index.php/Networking_FreeDOS_-_Packet_driver_installation > >> > >> I have also tried to remove LH, so the line in autoexec.bat reads: > >> PCNTPK INT=0x60 > >> > >> In which case i get the message during boot > >> > >> Packet driver is at segment 03E4 > >> PCNTPK-DOS-015: Device not found. > >> > >> and the boot stalls at that point. > >> > >> > >> Please advise. Where to find the appropriate driver for a virtual > >> device? > >> > >> Thanks in advance. > >> > > > > > > -- > > ___ > > 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 -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS 1.1 Bootable USB Image
Hi Rugxulo, I am still a fan of a FD 1.1 bootable USB image. By this time I use Qemu to build one, too. It is much easier to make the image bootable with Qemu than with Grub4DOS or Syslinux. Today I wear an USB stick together with my key ring with a bootable FD 1.1 image. I have created this image with Qemu and use some stuff like FDNPKG, the latest MPXPLAY and ideas from METADOS for my FreeDOS to go. And if I need new things on this image I boot FreeDOS on the stick with Qemu. In this way I can use Internet to load new stuff over FDNPKG on the stick. Another possibility is to put the stick into the USB port of my Linux computer just to copy stuff on this stick with a terminal or a file manager. And to use FreeDOS to go I can easily boot the stick with a computer. For the near future I like to build a FD 1.1 emulator like the ready to use Raspberry Pi emulator package for Windows: http://sourceforge.net/projects/rpiqemuwindows/ So that you can easy run FD 1.1 with Qemu on Windows by executing a run.bat. For Linux users like me I would put a run.sh into the ZIP file, too, but Qemu executables just for the Windows users. :-) Kind regards Christian Am Wed, 10 Jun 2015 13:38:30 -0500 schrieb Rugxulo rugx...@gmail.com: Hi, I somehow stumbled upon this blog/website which seems to host a FD 1.1 bootable USB image (and tells steps on how to make/install it ... with screenshots!). http://joelinoff.com/blog/?p=431 Maybe I missed it, but I'm not sure if any of us directly discussed this before, so I'm mentioning it here, in case anyone else finds it interesting. I do vaguely remember Christian Imhorst discussing something similar a year or so ago. Lemme find the link [Freedos-user] Is anyone installed FreeDOS from USB CD drive or other USB device? (Sat, 23 Aug 2014) https://www.mail-archive.com/freedos-user@lists.sourceforge.net/msg15388.html I heavily prefer RUFUS (which is Windows only, IIRC), but it's still good to see an alternative. P.S. Should this .ZIP be mirrored to iBiblio for us? -- ___ 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
[Freedos-user] MS-DOS Mobile
Hi all, if you have a Windows Phone 8 by accident you may found the MS-DOS Mobile App interesting: http://www.windowsphone.com/s?appid=8573c4a8-b9df-4409-90a6-dad2dc0b6b26 Microsoft published this App yesterday on April Fools Day and it is really funny with loads of easter eggs. MS-DOS Mobile goes back to the basics of Microsoft. You have to type commands to the prompt to access files and folders. The main apps are located in C:\PROGRAMS\PHONE. The camera.exe is really cool, and there is an interesting game you can play: RPS.exe When you try starting it after typing RPS.exe to the DOS prompt you get an error message: Not enough memory, RPS needs 641KB conventional memory. And Cortana says: That's odd, 640 K ought to be enough for anyone To solve this you have to run MEM and highload mouse driver. :-) The promo is really funny, too: https://www.youtube.com/watch?feature=player_embeddedv=irJQDGw8Ptk It's a nice app for retro DOS addicted. ;-) Best regards Christian -- 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
[Freedos-user] FreeDOS article for freiesMagazin
Hi all, maybe you like to know that I wrote an article about FreeDOS Totgesagte leben länger for the current issue of freiesMagazin: http://www.freiesmagazin.de/20141102-novemberausgabe-erschienen freiesMagazin.de is a free - under CC-BY-SA-4.0 international license - online magazine for Gnu/Linux, Free and Open Source Software. But it's only in German, unfortunately. ;-) Best regards Christian -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Resize partition without data loss
Hi all, thank you very much for your great suggestions. Especially FIPS and Partition Resizer. I tried both, but I am only able to resize partitions with these programs and not to merge two partions to one. I'll try GParted and hope it will do it well. Thanks a lot. Christian Am 22.10.2014 21:01 schrieb Don Flowers donr...@gmail.com: DS: If I were trying to increase 500 mb to 4 gig I'd do it this way. I'd use Norton Ghost(2001) to copy the 500mb partition to a suitable formatted cf chip. In reality, here is what I do: My setup is a 320gb hd. 1st partition is 2.0gb for Compaq DOS 5.0 (all my machines are compaq sff desktops); 2nd partition is 9g, for FreeDOS, The rest of hard drive contains Ubuntu 14.04 LXDE. I boot to the LXDE (remove unwanted files-usually downloads and test installations of shareware that I dont't like, then I zip my dos systems, then boot into xfdisk and the boot manager, and reformat and then back to the LXDE to unzip my archived systems on the new partition. The final step is to update grub. I've done this several times with numerous drives and I''ve never had data loss . DF On 10/22/14, Dale E Sterner sunbeam...@juno.com wrote: If I were trying to increase 500 mb to 4 gig I'd do it this way. I'd use Norton Ghost(2001) to copy the 500mb partition to a suitable formatted cf chip. I'd then use fdisk to remove the old partitions and fdisk to make a new 4gig partition. Remember to make the partition active and to then run fdisk/mbr to get a fresh mbr then format the drive. Then I'd use Ghost to copy the cf chip back to the harddrive or just buy a cf adapter and run the cf chip instead of the harddrive. cheers DS On Tue, 21 Oct 2014 20:25:36 -0400 dmccunney dennis.mccun...@gmail.com writes: On Tue, Oct 21, 2014 at 7:07 PM, Ralf Quint freedos...@gmail.com wrote: On 10/21/2014 11:39 AM, dmccunney wrote: On Tue, Oct 21, 2014 at 2:22 PM, Don Flowers donr...@gmail.com wrote: Gparted will not do it properly. You will not lose data, but FreeDOS will not report the correct size of the new partition. I have found only one thing that works: Partition Resizer available here: http://www.opus.co.tt/dave/utils.htm The link from Dave's site is broken here. The direct link - http://www.zeleps.com/ - works. That's even worse, it redirects to an attack web site these days... H. I use Firefox, which uses a Google maintained list of attack sites. I had no problem accessing it the first time. But I run Firefox with the NoScript addon that blocks scripting unless the site is in a user maintained whitelist. With scripting off, there's nary a peep from FF. When I *enable* scripting, I get the warning screen, talking about tzdpc.com. PRESZ134.ZIP is available from a number of sources: http://www.filewatcher.com/m/presz134.zip.100192-0.html, so zeleps status isn't a problem. Ralf __ Dennis https://plus.google.com/u/0/105128793974319004519 - - Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user Map Your Flood Risk Find Floodplan Maps, Facts, FAQs, Your Flood Risk Profile and More! http://thirdpartyoffers.juno.com/TGL3165/5447bc84c20c23c844685mp02duc ** From Dale Sterner - MS organic chemistry http://pubs.acs.org/doi/abs/10.1021/jo00975a052 *** -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho ___ 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 -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Resize partition without data loss
Hi, I have a 500MB FreeDOS partition on a 4 GB virtual hard disk. The rest of the disk is empty. Is it possible to resize the 500 MB to the whole disk without losing data? Do I use FDISK for this or another program? Thanks in advance. Best regards Christian -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] MetaDOS floppy distro (was: Re: How do you transfer files to your FreeDOS machine)
Hi, thank you very much for sharing METADOS. To me it looks very interesting and I like the idea of having a FreeDOS live distro, too. VMDK files are nice but I am using Qemu mainly. Therfore I was delighted that METADOS is an IMG file. ;-) To complement your METADOS.TXT I use the PCNET driver to emulate the network card with Qemu 2.1.0: qemu[-system-i386] -fda metados.img -boot a -net nic,model=pcnet -net user The part inside the parentheses is optional (at least under Debian). And thanks for VISIT.BAT. It's quite revealing. :-) Regards, Christian Am 27.09.2014 um 17:00 schrieb Rugxulo: Hi again, Okay, I finally uploaded this (and nobody complained, so I guess it's safe to announce). Just to be clear: it exists, it's very small, it has full sources, it's publicly available. http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/unofficial/metados/ To me, I thought this would be a useful starting point to making other distributions, whether .img for floppies (albeit unpopular) or .VMDK (or whatever virtual hard disk images) for various emulators. Perhaps there isn't enough interest in making various DOS distributions with different focuses? Not enough time? Or too hard to gather sources? No common goals? Or do some of you only care about retro / native / real hardware? For instance, I still haven't really investigated, but I'm fairly certain that even a slim BASE wouldn't fit entirely in 1.44 MB (without a miracle). Not that two disks would be horrible, but again, it's probably a lot of work to double-check everything. Just for comparison, both FreeBSD (qcow, vhd, vmdk) and Haiku (vmdk) have virtual hard disk images readily available for download. I'm not saying FreeDOS proper must absolutely host such a similar thing, but it's a cool idea. I think having a proper installation (though not necessarily BASE only) inside a public .VMDK file might be nice. The problem is what to put on it. Maybe I'm asking a futile question. Maybe not enough people care. Or maybe Mateusz's FDNPKG .iso is good enough?? I don't expect to solve every usage scenario, but it can't be impossible to try, can it?? On Tue, Aug 5, 2014 at 6:21 PM, Rugxulo rugx...@gmail.com wrote: On Fri, Aug 1, 2014 at 7:23 AM, Mateusz Viste mate...@viste.fr wrote: How do you transfer files between your main computer and your FreeDOS-powered machine ? FYI Recently I did make an extremely minimal bootable 1.44 MB floppy .img. (.ZIP'd it is less than 400 kb.) It has almost nothing on it, by design, except just enough to enable simple networking (packet driver + mTCP's DHCP + FTP). The point was that you would grab (via network) whatever pieces you need. For lack of a better name, I called it MetaDOS, thus it's meant to build your own floppy (or even indirectly create a hard disk image: fdisk, format, sys), esp. for use with certain emulators, tested successfully (Win7 64-bit) with VirtualBox 4.3.x and (admittedly old) QEMU 0.9.0 and 0.13.0. Oh, BTW, I made a small VISIT.BAT that will anonymously connect to popular FTP (mirror) sites, e.g. simtel, garbo, x2ftp, sac.sk, djgpp, ibiblio. Lots of good stuff there. I don't think a full (FreeDOS) BASE will fit on a single floppy. But I also don't think it's obvious what most people want or need either. We do probably still need a public and reliable floppy .img for FreeDOS. (For pete's sake, QEMU still links to ODIN 2005. And Jim Hall recently removed all of the unofficial floppy images from iBiblio, ugh.) -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Reply:Re: Is anyone installed FreeDOS from USB CD drive or other USB device?
Hi, sorry I've forgotten to mention, that you have to adapt the config.sys file, too: device=grub.exe install=grub.exe shell=grub.exe But anyway. You need a bootloader to load the ISO file fd11src.iso from an USB stick. In my first example I have used GRUB4DOS as bootloader. But now in a second example I will use SYSLINUX as bootloader. I have built a boot image which one can write to an USB stick. You can download the ZIP file with the image from my githup repository: https://github.com/christianimhorst/FreeDOSmultiboot/raw/master/FreeDOSmultibootStick.zip After unzipping you'll get the file FreeDOSmultibootStick.img You can write this image to an USB stick with at least 256 MB. If your stick is larger than 256 MB you can format the empty space as FAT16 or FAT32 with GParted as second partition. When FreeDOS boots from the stick you can access the second partition as drive D:. To write the image to your USB stick you can use dd, but be careful, it will destroy every data on the stick. It is available on every Gnu/Linux, *BSD or MacOS X. If you are using Windows you can find a Windows port here: http://www.chrysocome.net/dd Alternatively you can use Win32 Disk Imager with Windows: http://sourceforge.net/projects/win32diskimager/ This is an example how to use dd in GNU/Linux: dd if=FreeDOSmultibootStick.img of=/dev/sdX bs=512k Replace the X in /dev/sdX with the letter of your real device name. After rebooting your computer from the USB stick you'll get this menu: ### - Press ENTER to boot FreeDOS, or choose from these alternatives: --- : fdos.. FreeDOS 1.1 : bald.. Balder 10 (a single-disk DOS utility distribution) : install... Install FreeDOS 1.1 : memtest... Run Memtest86+ V5.01 --- Example: To boot Memtest86+, type memtest and hit Enter. - THESE IMAGES ARE PROVIDED AS IS, WITHOUT WARRANTY! USE THEM ON YOUR OWN RISK! BE WARNED! - boot: ### Type install. Next choose Create Drive C: from the FreeDOS menu. Than select 2. Set active partition Instead of your USB stick choose the hard disk as your active partion. The hard disk needs a DOS partition table and it has to be formated with FAT16 or FAT32. Otherwise it won't be recognized by the FreeDOS installer. When this is done you can proceed with FreeDOS installation. Regards Christian Am 01.09.2014 12:46, schrieb DOSforever: *Hi, Christian * Thank you very much for your detailed reply, because I'm not good at using English, so I cannot too much to participate in the discussion. I'd like to try the method that you introduced. In other words, in short, There is no way to install FreeDOS through FreeDOS ISO installation file from the USB device dierctly. I hope the installer don't so smart and complicated, so that I can install it manually. Thank you again for your help. Regards ?2014-08-29,Christian Imhorst christian.imho...@gmail.com mailto:christian.imho...@gmail.com ??: -- *???:*Christian Imhorst christian.imho...@gmail.com mailto:christian.imho...@gmail.com *:*2014?08?29? ??? *???:*Discussion and general questions about FreeDOS. freedos-user@lists.sourceforge.net mailto:freedos-user@lists.sourceforge.net *??:*Re: [Freedos-user] Is anyone installed FreeDOS from USB CD drive or other USB device? Hi yes I have built an usb stick with FreeDOS ISO to install. I work with GNU/Linux and I have prepared the stick with one partition fdisk /dev/sdX and formated the stick with FAT32: mkfs.vfat -F 32 -n freedos /dev/sdX1 The letter X stands for your real path, probably it's /dev/sdb for the device and /dev/sdb1 for the partition. But yours can be different. Than I followed these steps: 1. I downloaded latest Grub4DOS from: http://sourceforge.net/projects/grub4dos/ 2. I unpacked the following files to the root directory of the usb stick: config.sys grldr grub.exe menu.lst 3. Than I copied fd11src.iso to the same location. 4. I edited the menu.lst: ### title FreeDOS map (hd0,0)/fd11src.iso (hd32) map --hook root (hd32) chainloader (hd32) boot 5. Under Gnu/Linux you can test the stick with Qemu: qemu -m 512 /dev/sdX Or you can plug the stick into your computer now to boot the FreeDOS CD 6. Wait until Grub4Dos is loaded. 7. From the Grub4DOS menu choose FreeDOS 8. Next choose Create Drive C: from the FreeDOS menu. 9. Than select 2. Set active partition 10. Instead of your USB stick choose the hard disk as your active partion. Now you can proceed with FreeDOS installation. Hope that will help you. Regards Christian 2014-08-24 3:27 GMT+02:00 DOSforever
Re: [Freedos-user] Is anyone installed FreeDOS from USB CD drive or other USB device?
Hi yes I have built an usb stick with FreeDOS ISO to install. I work with GNU/Linux and I have prepared the stick with one partition fdisk /dev/sdX and formated the stick with FAT32: mkfs.vfat -F 32 -n freedos /dev/sdX1 The letter X stands for your real path, probably it's /dev/sdb for the device and /dev/sdb1 for the partition. But yours can be different. Than I followed these steps: 1. I downloaded latest Grub4DOS from: http://sourceforge.net/projects/grub4dos/ 2. I unpacked the following files to the root directory of the usb stick: config.sys grldr grub.exe menu.lst 3. Than I copied fd11src.iso to the same location. 4. I edited the menu.lst: ### title FreeDOS map (hd0,0)/fd11src.iso (hd32) map --hook root (hd32) chainloader (hd32) boot 5. Under Gnu/Linux you can test the stick with Qemu: qemu -m 512 /dev/sdX Or you can plug the stick into your computer now to boot the FreeDOS CD 6. Wait until Grub4Dos is loaded. 7. From the Grub4DOS menu choose FreeDOS 8. Next choose Create Drive C: from the FreeDOS menu. 9. Than select 2. Set active partition 10. Instead of your USB stick choose the hard disk as your active partion. Now you can proceed with FreeDOS installation. Hope that will help you. Regards Christian 2014-08-24 3:27 GMT+02:00 DOSforever dosfore...@126.com: first all, I'm not good at english. I don't know if I expressed correctly. I burned fd11src.iso file to CD, insert the CD to USB CD drive, boot from the external USB CD drive. but after FDISK list my existing partiton table, the SETUP show the fellowing message: SETUP wasn't able to locate any disks to install FreeDOS 1.1 from. If I write image file to flash memory, the same phenomenon also appears. I built the same partition table structure in virtual machine, boot from VM's IDE CD-ROM, no problem. I don't know wether the problem is caused by USB interface? -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] How to install FA511 PCMCIA Network Card
Hi, I have installed FreeDos 1.1 on my Toshiba Tecra 8000. Now I try to get my NETGEAR FA511 32-bit PCMCIA LAN card working. I have copied FA511.COM and NET.CFG from the NETGEAR CD-ROM with drivers to C:\NWCLIENT together with some files who are needed to start networking. So I run LSL.COM from this directory and than I start FA511.COM. The latter one ends with an error message: FA511-DOS-104: No NIC found in the machine. I think my PCMCIA slot is not recognized by FreeDOS. What do I need to get my PCMCIA card working? Hardware is ok because it works with Linux. Best regards Christian -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to install FA511 PCMCIA Network Card
Hi, 2014-07-19 16:41 GMT+02:00 Louis Santillan lpsan...@gmail.com: What do your config.sys and autoexec.bat look like? You'll need to add your drivers somewhere in that mix. I have no idea what my or the driver for PCMCIA looks like. I have searched the Internet for a PCMCIA driver for DOS and Toshiba notebooks but I didn't find one. This is my AUTOEXEC.BAT: --- @echo off SET LANG=DE SET MTCPCFG=C:\FDOS\MTCP.CFG SET WATTCP.CFG=C:\FDOS SET PATH=%dosdir%\BIN SET NLSPATH=%dosdir%\NLS SET HELPPATH=%dosdir%\HELP SET TEMP=%dosdir%\TEMP SET TMP=%TEMP% SET BLASTER=A220 I5 D1 H5 P330 SET DIRCMD=/P /OGN /4 SET COPYCMD=/-Y if %config%==4 goto end SHSUCDX /QQ /D3 LH SHSUCDHD /QQ /F:FDBOOTCD.ISO LH FDAPM APMDOS IF %config%==2 LH SHARE LH DOSLFN REM NLSFUNC C:\FDOS\BIN\COUNTRY.SYS REM DISPLAY CON=(EGA),858,2) REM MODE CON CP PREP=((858) C:\FDOS\CPI\EGA.CPX) REM KEYB US,858,C:\FDOS\bin\keyboard.sys REM CHCP 858 REM LH PCNTPK INT=0x60 REM DHCP MOUSE DEVLOAD /H /Q %dosdir%\BIN\UIDE.SYS /H /D:FDCD0001 /S5 SHSUCDX /QQ /~ /D:?SHSU-CDR,D /D:?SHSU-CDH,D /D:?FDCD0001,D /D:?FDCD0002,D /D:?FDCD0003,D MEM /C /N IF NOT %config%==4 SHSUCDX /D GOTO END :END SET AUTOFILE=%0 SET CFGFILE=C:\FDCONFIG.SYS LH KEYB GR,,keyboard.sys alias reboot=fdapm warmboot alias reset=fdisk /reboot alias halt=fdapm poweroff alias shutdown=fdapm poweroff alias cfg=edit %cfgfile% alias auto=edit %0 echo Done processing startup files %cfgfile% and %0 echo Type HELP to get support on commands and navigation echo. echo Welcome to the FreeDOS 1.1 operating system (http://www.freedos.org) --- And this my FDCONFIG.SYS --- !COUNTRY=001,858,C:\FDOS\BIN\COUNTRY.SYS !SET DOSDIR=C:\FDOS !LASTDRIVE=Z !BUFFERS=20 !FILES=40 !MENUCOLOR=7,0 MENUDEFAULT=1,5 MENU 1 - Load FreeDOS with JEMMEX, no EMS (most UMBs), max RAM free MENU 2 - Load FreeDOS with EMM386 (Expanded Memory) and SHARE loaded MENU 3 - Load FreeDOS including XMGR XMS-memory driver MENU 4 - Load FreeDOS without drivers 123?DOS=HIGH 12?DOS=UMB 12?DOSDATA=UMB 1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG 2?DEVICE=C:\FDOS\BIN\HIMEMX.EXE 2?DEVICE=C:\FDOS\BIN\JEMM386.EXE X=TEST I=TEST I=B000-B7FF NOVME NOINVLPG 3?DEVICE=C:\FDOS\BIN\XMGR.SYS 3?SHELL=C:\FDOS\bin\4dos.com C:\FDOS\bin /E:1024 /P:C:\AUTOEXEC.BAT 4?SHELL=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT 12?SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT --- Best regards Christian On Sat, Jul 19, 2014 at 2:41 AM, Christian Imhorst christian.imho...@gmail.com wrote: Hi, I have installed FreeDos 1.1 on my Toshiba Tecra 8000. Now I try to get my NETGEAR FA511 32-bit PCMCIA LAN card working. I have copied FA511.COM and NET.CFG from the NETGEAR CD-ROM with drivers to C:\NWCLIENT together with some files who are needed to start networking. So I run LSL.COM from this directory and than I start FA511.COM. The latter one ends with an error message: FA511-DOS-104: No NIC found in the machine. I think my PCMCIA slot is not recognized by FreeDOS. What do I need to get my PCMCIA card working? Hardware is ok because it works with Linux. Best regards Christian -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Compile mode.com
Hello all, as I am trying to get a working serial port emulation under DOSEMU I would like to use the freedos version of mode.com . I need to remove the if clause that checks whether the serial port number is invalid (1 or 4) as I'd like to configure COM5. I found the code in mode.c and changed it but I don't know how to recompile. Makefile said something about nasm so I installed nasm on a virtual DOS machine and did nasm makefile but there were a few errors saying error: label or instruction expected at start of line. Seems like these lines were comments. Does anyone know what to do? Thanks, Hans -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Compile mode.com
Hello all, as I am trying to get a working serial port emulation under DOSEMU I would like to use the freedos version of mode.com . I need to remove the if clause that checks whether the serial port number is invalid (1 or 4) as I'd like to configure COM5. I found the code in mode.c and changed it but I don't know how to recompile. Makefile said something about nasm so I installed nasm on a virtual DOS machine and did nasm makefile but there were a few errors saying error: label or instruction expected at start of line. Seems like these lines were comments. Does anyone know what to do? Thanks, Hans -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Compile mode.com
Hi Dennis, thanks for explanation. I also had a compiler called djgpp installed but it seems like that isn't what I need either? Can you tell me where to get make / installation instructions? Thanks, -Ursprüngliche Nachricht- Von: dmccunney [mailto:dennis.mccun...@gmail.com] Gesendet: Montag, 16. Dezember 2013 19:06 An: Discussion and general questions about FreeDOS. Betreff: Re: [Freedos-user] Compile mode.com On Mon, Dec 16, 2013 at 12:22 PM, Hans-Christian Koch hc.k...@scheerkoch.de wrote: as I am trying to get a working serial port emulation under DOSEMU I would like to use the freedos version of mode.com . I need to remove the if clause that checks whether the serial port number is invalid (1 or 4) as Id like to configure COM5. I found the code in mode.c and changed it but I dont know how to recompile. Makefile said something about nasm so I installed nasm on a virtual DOS machine and did nasm makefile but there were a few errors saying error: label or instruction expected at start of line. Seems like these lines were comments. Does anyone know what to do? NASM is an assembler program, intended to produce object code from Assembler source files. When you said nasm makefile, you told nasm to try to assemble makefile. Because makefile isn't an assembly language source file, nasm had no idea what to make of it. Makefiles are instructions to the make utility. Make reads a makefile and performs the steps specified in it. The makefile defines what steps must be performed in what order to compile and build the program the makefile is for. Make will call nasm to assemble to assemble the appropriate assembly language file(s) specified in the makefile. Assuming you have make installed, go the the directory where the makefile is and just enter a make command. By default, make will look for a file called makefile in that directory, read it, and attempt to follow the instructions it gives. Hans __ Dennis -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Compile mode.com
Hey Eric, nice to meet you! I tried to find your Email on the web as I saw your name in makefile but I only found an old one. Thanks for your help, works very well!! -Ursprüngliche Nachricht- Von: Eric Auer [mailto:e.a...@jpberlin.de] Gesendet: Montag, 16. Dezember 2013 20:53 An: freedos-user@lists.sourceforge.net Betreff: Re: [Freedos-user] Compile mode.com Hi! To compile FreeDOS MODE, you need the following: upx (in any of your PATH directories) nasm (same) tcc (Turbo C 2.01, search in the Borland museum / ask Rugxulo) make (also the old Borland version, I assume) In theory, it is also possible to compile mode with OpenWatcom C, using wcl instead of tcc by editing the makefile accordingly. However, the makefile says that this has not been tested so far. FreeDOS also has some other MAKE tools around. You could indeed try GNU MAKE which comes with DJGPP. However, you cannot compile MODE using the C compiler of DJGPP itself. You need a compiler which can produce 16bit binaries, such as Turbo C or OpenWatcom. Once you have all ingredients simply run make in the directory where the source code is. You can even do without upx, if you comment out that part of the makefile, but then you get larger binaries in the end. Regards, Eric as I am trying to get a working serial port emulation under DOSEMU I would like to use the freedos version of mode.com . I need to remove the if clause that checks whether the serial port number is invalid (1 or 4) as I'd like to configure COM5. I found the code in mode.c and changed it but I don't know how to recompile. Makefile said something about nasm so I installed nasm on a virtual DOS machine and did nasm makefile but there were a few errors saying error: label or instruction expected at start of line. Seems like these lines were comments. -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Searching FDBOOTCD.ISO
Hello list, I'd like to boot FreeDOS from CD. Henc I'm searching FDBOOTCD.ISO - Google did not return any source and as far as I read the docs there is no such image as FreeDOS needs to have a writable drive. Am I right or just clumsy? Best regards Christian -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Searching FDBOOTCD.ISO
Hi Eric, I took a closer look and you're right, the 1.0-boot-CD fdbasecd.iso is there online - Blindfisch me! I downloaded the latest fd11src.iso version too and checked for a bootable dos-image. Again I'm about to be clumsy but within that more recent package I do *not* find some file that looks like a bootable dos-CD-image. Is there really an image ready to boot contained in fd11src.iso? And if so: Can you help me with the file's name, please? Best regards Christian -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] New release of DOSUTILS package
Indeed. Another interesting thing, though, is that in combination with my SCANCODE utility, it is actually possible to automate PRTSCR. Points for creativity, but you have to admit that actual support for command-line (or environment variable, script) driven operation of PRTSCR would be simpler, and would suffice in at least most cases. Regards, Christian -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] New release of DOSUTILS package
I meant that support for controlling PRTSCR in this way could be a part of the PRTSCR program, without requiring the detour via SCANCODE. Regards, Christian -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] mTCP 2011-05-20 Version
Now that mTCP is Free Software, I think the next version of FreeDOS should focus on getting basic networking abilities. Well, relatively free. A certain group of people are aghast that I used GPL v3 - apparently that is not free enough for them. I'm getting a good laugh out of that conversation though. Should you refer to me here (I highly doubt you do not) then please ensure not to misrepresent my opinion. I am not aghast at your choice of license. Though as has been stated it is true that personally I would have _preferred_ a license other than the GPL. It is obviously your choice. As I pointed out I appreciate your source code release nonetheless. If you want to further express your amusement at me please keep that to our forum. I will not reply to other posts about that on this mailing list. -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem with UIDE
You can also run JEMM386 LOAD at any time but that doesn't give you UMBs. A program modifying DOS's internal data which could effectively link in new UMBs is easy enough to write, provided that the kernel's handling of the UMA is compatible enough to that of the MS-DOS kernel. Regards, Christian -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] if not exist MD XXX
Hey, if not exist mydir/nul md mydir Doesn't work on XP (I think?), but that's the typical DOS way. This kept bothering me for some reason, so I checked now. It appears to work just fine on MSW NT command lines, executing the command after if not exist dir\nul if and only if that directory doesn't exist. In NTVDM, it does work as well (only?) using the COMMAND.COM supplied with NT; however, with other COMMAND.COMs (including FreeCOM) it indeed doesn't work: device names (such as NUL and CON) apparently aren't found. So while checking for a directory's existence with this method might work in non-DOS NT batch scripts, it can't be relied upon because the NTVDM's DOS interfaces appear not to find device names. Regards, Christian -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] if not exist MD XXX
Hi Eric, As far as I remember, the DOS findfirst API is supposed to find character devices (such as NUL) in any (existing) directory, so this would depend more on DOS than on COMMAND, but I am not sure. Without any further investigation, I'd say that's part of it. However, aside from the MSW program cmd.exe (which obviously doesn't use NTVDM-DOS's FindFirst) the NTVDM-COMMAND program (which at least partly works as V86-mode DOS program) does find the devices too. I guess it might not use the NTVDM-DOS interfaces internally and hence finds the devices. This would indicate NTVDM-DOS's FindFirst and FindNext are broken (incompatible) in some way as you suggested. I didn't get into the specifics earlier 'cause I didn't think it was necessary. Regards, Christian -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] No kernel sys
On Sun, 05 Dec 2010 14:13:15 +0100, Fabrizio Gennari wrote: Il 05/12/2010 13:25, Fabrizio Gennari ha scritto: Where do I download the new kernel and the new SYS? I guess that, after the download, it's a matter of unzipping in the right folder... Found the answer to that: http://ftp.gwdg.de/pub/misc/freedos/files/dos/kernel/2039/ Yes, for example. The kernel is also available from FreeDOS's SF.net project (http://sourceforge.net/projects/freedos/), and the software list contains a link to the ibiblio FreeDOS mirror (see http://freedos.sourceforge.net/software/?prog=kernel). Ask again if you can't get it to work with the updated SYS and kernel. Regards, Christian -- What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] location of autoexec.bat?
Oh, I thought that the liveCD would do something like look somewhere on the C: drive for a specific autoexec file and then execute that if it's present. I just assumed that it would have that capability. I can't say that I understand why it doesn't do this, but obviously there must be some reason for this restriction. Apparently no one saw a need for that. For symmetry, you would have to provide a writeable (FD)CONFIG.SYS file too (which is harder to accomplish). In both cases, these files should probably _replace_ the ones on the CD. Additionally, your drive C: could be some read-only device (or one you don't want to modify) too, or maybe there isn't a drive C:, or whatever. Even something as simple as saying that we always execute the file C:\FDOS\CDAUTO.BAT (for example) if it exists, does not appear reasonable to me. I'll just have to write my own batch file and remember to execute it manually on startup each time. That's the best workaround you'll get with the CD as is. Yes, it does need to run natively. It needs real-time access to the real hardware, and it needs to be in an environment in which nothing else is going to steal cycles. Then I suggest you install a whole FreeDOS installation (or only the boot disk of the CD, or only a small installation containing everything you need) on your R/W storage (hard disk) and boot that. The live CD isn't intended for this usage. You can update the writeable installation with newer programs then, too. Regards, Christian -- What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] No kernel sys
http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=General_Information/225 says obscurely a little tweaking (of the boot sector linear partition position / hidden sectors value) should make LBA booting on any drive letter possible, but it does not specify what to tweak and how. This is not related to your problem, unless your drive C: (atypically) is a logical partition. Primary partitions should work just fine. The mentioned tweaking is meant for developers. Make sure the file KERNEL.SYS exists in C:\. Update to kernel 2038 or 2039 (from the FreeDOS mirrors) and use the updated version of SYS in there to install that kernel. If that doesn't make it work, try using the SYS option to force the access method to LBA or CHS. You can also try the option that will hard code a BIOS drive number (usually 80(h) is the right for hard disks) into the boot sector instead of relying on the BIOS to provide the correct one. Regards, Christian -- What happens now with your Lotus Notes apps - do you make another costly upgrade, or settle for being marooned without product support? Time to move off Lotus Notes and onto the cloud with Force.com, apps are easier to build, use, and manage than apps on traditional platforms. Sign up for the Lotus Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Watch out for Windows 7
Seems like it's related to some new hardware stuff that broke floppy DMA. On some boards Linux is said to have similar problems. -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book Blueprint to a Billion shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem w/ CONFIG.SYS INSTALL
Maybe JEMMEX has problems with fragmented memory, did you try JEMM386? Maybe not..? The issue does not appear to be related to JEMM (as usual). The error itself does not tell much - GPF at a 64k segment boundary... Could mean that code jumped into an empty segment and fell of its end. It would appear so. It might be possible that DosComLoader tries to give the COM all available memory and unless you specify otherwise when going TSR none is left for others, but thats just guessing. Bret allocates other memory blocks, so he does resize the process first as necessary. (As an aside, such a situation should not make the kernel crash like that.) Is your TSR a COM or is it EXE? Does it keep handles open? Does it use environment variables or other PSP related data? Does it make a difference whether to INSTALL or INSTALLHIGH? Educated guess: COM, no (shouldn't matter though), no (except as allowed, before the TSR is resident), no (Bret said so). Regards, Christian -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem w/ CONFIG.SYS INSTALL
The TSR I'm working on can't be published just yet, so that's not an option right now. I thought so. It's also _really_ complicated, so I'm not sure anyone would want to mess with it anyway. You know me. I'm using an older version of the kernel -- I'm not sure exactly which one right now, but it's one from right after FreeDOS version 1 was released. I'm working with some other programmers who are using the latest versions of the kernel. I can find out exact details if it might help. Yes, details would help. I would strongly recommend you to update your kernel, that might fix the problem. Regards, Christian -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] internationalization ... KEYB bug? ... i18n-DOS ... Greek, Esperanto ... kernel 2039
That would suggest that you got some of the syntax or maybe order of loading things wrong - Can you try if it works with another kernel or other keyb versions? If it crashes, it's a bug, even if the wrong loading order or syntax was used. Maybe problems are limited to some versions. Yes, maybe the bugs are/bug is limited to some versions. which could then overwrite things in RAM, Which would be a bug. Jumping to 0:0 could mean a pointer/handler is used before being set. Good call. Regards, Christian -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] internationalization ... KEYB bug? ... i18n-DOS ... Greek, Esperanto ... kernel 2039
(Freedos-devel much?) Hi, It uses kernel 2039 and COUNTRY.SYS, and it more or less works ... except for KEYB. For some reason, every computer I try, every memory manager, even disabling certain things (CTmouse), it *always* dumps an exception when trying to load KEYB. In fact, KEYB never loads correctly. (Part of this was my confusion with trying to learn what Greek needs, 737? 869?) Whatever, but it's not even working as good as I previously confirmed (year ago?) with cp853 (Esperanto). I almost want to think it's a 2039 kernel bug, but I highly doubt it. :-( XMGR, HIMEMX - Invalid opcode (is that the kernel saying that???) Probably. Could be the BIOS, but I think the kernel installs a handler. JEMM386 - Exception at CS:IP : ... Press Esc. to quit. I'm just lucky it doesn't crash the whole thing, sheesh. It *does* crash the whole thing. You just had luck that during the crash it eventually encounters an invalid opcode somewhere. Just curious if anybody knows what's wrong, what to try next, etc. I think it would be nice to demo the i18n features of FreeDOS. (Maybe I should try putting the files on a more reliable medium like hard drive and see if that helps. I would definitely feel foolish if that was the solution. But anyways ) Could you send links to the necessary files (specific versions of KEYB, DISPLAY, MODE, CPIDOS, etc) to create that floppy, or to an image? I can try debugging it (need test cases anyway). Regards, Christian -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] svn failure
(Shouldn't this rather go to Freedos-devel?) Path 'C:\salami\src\fdos\mem\branches\mem14\...' is not in the working copyPath Anyone getting a similar error? No, I did not previously read about such an error. It might be helpful if you would rely more information to the list. Like, what program you are downloading and from which repository. From the message that you have shown, I would assume it's a problem with the file mem/branches/mem14/... (yes, it's named like that) in the FreeDOS SVN repo. (This file is shown by the SVN browse sf.net interface.) ... is not a valid file name for DOS or Windows file systems. Regards, Christian -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] LBA and clusters
I keep LBA disabled, for I partitioned the HD with 4-sector clusters. Clusters and LBA have nothing directly in common. Partitions are made up only of sectors. It's only subsequent formatting that gives birth to logical clusters, after the act of partitioning is over. LBA is about addressing sectors, regardless how formatting groups them or not. Right. Additionally, I want to clarify this: the FAT file system clusters should not ever be relevant to your BIOS in any way. The BIOS (in most or all cases) does not know anything about files, file system clusters, file systems or (MBR) partitioning beyond access to numbered sectors. Whether the sector numbering is LBA or CHS, or whether low-level translations such as 1 BIOS sector is 8 physical sectors are used does not in any way affect DOS in dealing with FAT file system clusters. The units of such low-level translations might be called clusters by your BIOS or hard disk vendor, but (by what you wrote us) I do not believe these are associated with the FAT file system clusters in any way. Besides, you don't have to turn on LBA. If CHS addressing works correctly and your entire disk can be accessed by it, it usually doesn't matter much whether you enable LBA. It would be interesting to know what size of these units are used by your BIOS and hard disk. When you say 1 logical block = 8 sectors, how large is one logical block and how large is one sector? When you say sector, do you mean the physical sector on the hard disk? Likewise, do you mean the unit accessible by software when you say logical block? Does this translation happen only with LBA access, or both with CHS and LBA access? It would be nice if you could find out more about this. Regards, Christian -- Virtualization is moving to the mainstream and overtaking non-virtualized environment for deploying applications. Does it make network security easier or more difficult to achieve? Read this whitepaper to separate the two and get a better understanding. http://p.sf.net/sfu/hp-phase2-d2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Fwd: File corruption
Sorry to sound dense but how do you change the kernel from 16 to 32 bits? Isn't there just one kernel and it works with a filesystem that is FAT16 or FAT32? Or are these kernels compiled with different memory models? There's one kernel that supports the FAT12, FAT16 and FAT32 file systems (called FAT32 kernel) and one that only supports the FAT12 and FAT16 file systems (called FAT16 kernel). I think this is what was meant here. As Tom said, the issue appears to be specific to the FAT16 kernel (i.e. the one that doesn't have FAT32 support). Besides that, there is (or was?) a kernel optimized for 386+ CPUs that is able to use 32-bit instructions (although it still executes from within a 16-bit memory segment as usual) and therefore might utilize 32-bit registers. This kernel only runs on 386+ CPUs. For kernels 2038 and 2039, such binaries currently ain't provided on the FreeDOS mirrors so you would have to compile such a kernel utilizing 32-bit instructions yourself to use it. Regards, Christian -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] file corruption
Some older machines (e.g. this) require an specific cluster size in order to use LBA. The BIOS doesn't know anything about cluster sizes. Maybe you mean sector sizes? Almost all floppy and hard disks have a sector size of 512 byte. Expect problems with hardware, firmware and/or software if that is not the case. Regards, Christian -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Processor overheating under DOS
This is just the opposite of what I expected. I always thought that it is easier for a processor to run DOS than Windows. In case you care about the technical background: DOS is dumb. When waiting for user input, it (all DOS versions I know) by default just loops forever until a key was pressed. This apparently was no problem at some time but now makes your CPU eat a lot more power and produce a lot more heat than is necessary. This design fault was and is inherent even in the BIOS servicing code for user input. As Mateusz said, using FDAPM APMDOS or a similar setting should cure the primary reason this happens. It does so by hooking the DOS and BIOS functions which are called by idle-unaware programs (90% of DOS software), and replacing the DOS/BIOS code with a loop that (a) calls a different DOS/BIOS function to check whether a key is currently available, (b) if no key is available, halts the CPU til the next hardware interrupt (usually timer or keyboard), and (c) otherwise gets the key from the flawed DOS/BIOS code. These won't unnecessarily stress the CPU if the key is already in the BIOS's buffer so it's okay to call them if you know that there is. Regards, Christian -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Processor overheating under DOS
What happened was, I had stopped using FDAPM with the portables after finding that it was interfering with Bret Johnson's USB keyboard driver. Hence the overheating. Did you report that to Bret already? Regards, Christian -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Processor overheating under DOS
All versions of DOS I know require the use of a TSR (like FDAPM, or MS-DOS's POWER) to idle correctly, or of a program that does the idling itself (I don't know any COMMAND.COM version that does so). However, as the flawed call usually will simply be called by idle-unaware software, an idle-aware handler of the call could provide correct idling. This particularly means that DOS can fix incorrect applications, if they call DOS, and that the BIOS can fix DOS (because DOS always calls the BIOS) and all applications that call the BIOS. Though I have not yet seen a BIOS that idles correctly (even on recent boards!), there might be some that do. Regards, Christian -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDos-user, SoundBlaster ?
Apparently, in the Windows partition there is an emulator. This direction does not get you anywhere, because the emulator's output is simply the Windows driver for your sound card. MPXPLAY is working great for music on FreeDOS, so the sound capabilities are there. This is better. Now learn to program in C and Assembly language and write a JLM Sound Blaster emulation driver based on MPXPLAY's drivers. Regards, Christian -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Processor overheating under DOS
Seems you're not old enough to ever have worked with one of the 5V Pentium CPUs (60/66MHz) for example... LOL I didn't really care at the time. I can assure you the AMD K-4 (~ 300 MHz) and Pentium II (~ 250 MHz) boards that I still regularly use do profit from idling too. But really, though I wouldn't recommend it, I don't care whether you let your CPU run at full workload either. Regards, Christian -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS USB Device Problem
I use a DOS USB Drivers from bretjohnson.us, someone here ever suggest this driver before on this list. However, I'm not familiar with this, I took steps and installed the driver but system will hang or tell me wrong IRQ. So could anyone show me an example to setup this driver? Please specify any exact error messages that appear and describe your system and relevant details. More importantly, tell us what executables you executed, and with which parameters. You may also want to report this to Bret directly, or on his forum, as he usually will tell you why the drivers might not work and assist you with technical problems. Or if there's another good choice, pls. show me an example about that. There are some other USB drivers floating on the net but I don't know any specifics any more. The one set worth mentioning is Georg Potthast's recent drivers but they have several practical disadvantages. Nonetheless, you are free to check them out on his site: http://www.georgpotthast.de/ Regards, Christian -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDos-user, SoundBlaster ?
Dosbox [...] goes one step beyond in that they added to the emulator a DOS-like interface that maps the native file system into the DOS system calls, as well as the remaining DOS and BIOS system calls. I might add that I would not generally recommend using the DOSBox built-in DOS for anything except games - the main DOSBox distribution is tailored to support DOS games so non-game applications might not work as well. (I.e.: they just don't care about any other applications and so their DOS partly is lacking.) Regards, Christian -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDos-user, SoundBlaster ?
- Remove the word DOS from the name (the thing is unable to boot into a PC, so it's not a OS and thus not a DOS) I don't think they use the term for it, sorry for confusing you. - Remove the DOS-like interface that maps the native file system (so turn it into a clean 80386 / 80486 / early Pentium PC emulator) No, the file system support is quite useful. Rather, remove the pseudo-DOS around it entirely - but retain the file system mapping as a file system redirector that would be installable in the emulated DOS (similar to *CDEX and other file system drivers). Regards, Christian -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Incompatible file system checking results
2. Why do FreeDOS CHKDSK and DEFRAG (as well as MS-SCANDISK) report so many errors while DOSFSCK does not, and in practice the disks seem to work well? CHKDSK and DEFRAG ain't that reliable really. Regarding SCANDISK, maybe you used an old version (MS-DOS 6.x) on a hard disk that's addressed using LBA? If your hard disk is larger than 8 GiB and the partition is partly or fully outside the first 8 GiB of the disk, then that might lead older SCANDISKs to work improperly. Regards, Christian -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Help: FreeDOS hangs when select memory management method
Could you tell me how do I modify this file? You have to save the JEMM386.EXE file somewhere on the image, then replace C:\FDOS\BIN\EMMM386.EXE in both lines it appears in with the path to and file name of JEMM386.EXE. The options (behind the EMM386.EXE path) should work with JEMM just as well. I would recommend updating HIMEM with HIMEMX (from the same page as JEMM) too. You have to do the same as with JEMM for that, just instead of EMM386.EXE replace the file name of HIMEM.EXE with HIMEMX.EXE. Regards, Christian -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Help: USB drivers for USB mass storage devices
Is there any good USB drivers for USB mass storage like USB flash disk? I hope the driver can support USB 2.0. There's currently two drivers under development: Georg Potthast's DOSUSB supports UHCI, OHCI (USB 1.x) and EHCI (USB 2.0) controllers and comes with some drivers (e.g. a disk driver, IIRC a CONFIG.SYS device driver): http://www.georgpotthast.de/usb A demo version (don't know about limitations) is available for free. Otherwise, see this site for licence/prices: http://www.georgpotthast.de/usb/licencen.htm Bret Johnson's USBDOS package currently includes support for UHCI (some USB 1.x) controllers only. This means it won't work with OHCI (other USB 1.x) controllers, and will only work at USB 1.x speeds with EHCI (USB 2.0) controllers if they have a companion UHCI controller. Most EHCI controllers either have UHCI or OHCI companion controllers. It comes with a disk driver TSR and some others. The programs and their entire source code is available free under a simple Copyleft-license (i.e. derivative programs have to use the same license) from Bret's pages: http://bretjohnson.us/ Regards, Christian -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] doing graphics
Has anyone used any of them in DOS? Yes. That is, I heard of people using them successfully. But I believe Yes is an adequate answer to your question. Regards, Christian -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Dualboot with Knoppix?
Has any FreeDOS user ever dualbooted with Knoppix (DSL)? No. Regards, Christian Masloch PS.: If using GRUB, instruct it to boot the FAT partition on which you installed FreeDOS. Or create a boot sector file of the DOS FAT partition with FreeDOS SYS then boot that. -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] very small FAT12 partition?
- a boot block (MBR) containing a valid description of the FS (number and size of FAT[s], CHS geometry, etc. - not all of which can be tuned using standard tools probably) - BIOS Parameter Block is what you want to look for (and compare against actual values in a standard size floppy image) The CHS information is usually ignored by the driver and might be bogus. It sure is ignored if the partition is accessed directly by the operating system (from a file or RAM or ROM). Note that the FAT file system internally uses a sector addressing scheme like LBA: there is a sector number that counts the sectors starting from zero. Nothing else. The FAT driver doesn't care about heads and cylinders that might be addressed at a lower level. The boot block is also called boot sector, but not MBR (Master Boot Record). The MBR isn't contained in any partition. - one or two FATs (starting with the magic code), big enough for your *data* blocks You certainly want only one if you have to utilize a very small partition. Regards, Christian -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] very small FAT12 partition?
Hi Stefan, My question is not exactly FreeDos related but I hope that you could help me anyway: For an embedded project I need to create a very small FAT12 partition. In a proprietary project I found a partition of 4KB size (which I can not reuse because of license issues) but could not manage to recreate a similar one. Therefore on Linux I tried mkdosfs -f 1 -F 12 -h 0 -S 512 -C partition.iso 4 but it fails with the error message that this partition is too small. The smallest I could build this way was 34KB in size. Could you give me any hint how to create a partition smaller than 34 KB? If there's no tool to do what you want, you might be able to create it yourself with an assembler. For this, I found a nice NASM (the Netwide Assembler, at http://www.nasm.us/) macro to create FAT12 images on this german blog: http://superschurke.wordpress.com/2006/06/09/mit-nasm-fat12-images-erstellen/#more-5 (Don't worry, you should be able to copy and read the code without problems even in case you don't speak german. Though if you need a translation, don't hesitate to ask me for it.) Regards, Christian -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Determining partition types (NTFS, etc)
PS: for what I know vfat in Linux is just the name of FAT32 ;) Then Linux is not correct, because VFAT is just an extension to FAT12 / FAT16 / FAT32 to allow long filenames: Ok, but most people should be aware that in the Linux literature (most google tutorials) the tem vfat is used liberaly. I've only ever heard it used to mean *all* file systems using the VFAT extension, i.e. FAT12, FAT16 and FAT32 file systems with long names. They probably call this the VFAT file system to distinguish it from their original FAT file system implementation which didn't support long names and the new file times. (BTW, the V stands for Virtual which at most fits into Microsoft's strange behaviour of calling everything related to Win386 virtual, and doesn't relate to what a VFAT file system is in any way. They probably only named their VxD VFAT, and with this implementation being the first one to support the new features, someone just called these features VFAT.) Regards, Christian -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedos - Modern sata dvd dual layer not found
First of all, what is AHCI? isn't that related to USB??? No. USB is related to the UHCI (USB 1.0), OHCI (USB 1.1), EHCI (USB 2.0), WHCI (Wireless USB) and XHCI (USB 3.0). AHCI is an interface for SATA controllers. Regards, Christian -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Odd behaviour involving mouse
Can anyone explain what IDLEHALT=1 does? It could be interesting to know this in more details for fure problems or even for general kowledge... IDLEHALT=1 halts the CPU (with a HLT instruction) before calling Int28, when the kernel is waiting for a key to be pressed. FreeDOS's default Int28 handler itself does nothing. FDAPM however might execute another HLT in its Int28 handler resulting in bad performance. You'll get the best performance with no HLTs at all, but one HLT before/in Int28 (IDLEHALT=1 but no FDAPM?) shouldn't affect performance badly either. That might be related to how exactly the application writes to the screen. Regards, Christian -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Fwd: DOSLFN discussion on FreeDOS user list
Hi Laaca, please consider registering yourself to the user list as well if you want to further discuss this or other issues there. The first issue probably arises from an incorrect check for LFN functions, or one DOSLFN doesn't support. (Does it work correctly in a Windows 4 DOS box?) The second issue (collisions handled improperly) is only RAR32's fault. Regards, Christian -- List, Below find a forwarded message Laace send to me. --- Weitergeleitete Nachricht --- Von: Laaca la...@seznam.cz An: cm c...@bttr-software.de Kopie: Betreff: DOSLFN discussion on FreeDOS user list Datum: Sat, 21 Nov 2009 12:44:14 +0100 Hi! I read the discussion about problems with DOSLFN in particular situations in FreeDOS. The described example is quite hard to reproduce but I know another one and much easier to track. DOSLFN doesn't work properly with RAR32 for DOS and OS/2. If archive contains long file names they are truncated into 8+3 names and the name collisions aren't properly treated. If you want to decopress such archives you have to use the windows console version which fortunately runs perfectly under HX. (Note that this trick fixes also another problem of DOS version of RAR - the unability to run on computers with 512 and more MB RAM) I am not registered to FreeDOS users list (I am only at developers list) so, please, forward this message into it. --- This e-mail has been sent via the forum (http://www.bttr-software.de/forum/). -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOSLFN and File Wizard
BTWW, King Udo (EDR-DOS maintainer) reportedly uses it and is happy (the only one user ???), possibly the problems occur with FreeDOS only, not with EDR-DOS. No idea why and no ambition to debug this type of problem :-| I'm using it too on MS-DOS (for both read and write access) and it didn't corrupt anything yet. The way DOSLFN is implemented however is messy; it depends on DOS's behaviour (it was developed on MS-DOS 6.22 and 7.10). Either DOSLFN depends on something it shouldn't, or the FreeDOS kernel fails to behave similar to MS-DOS somewhere. (Or both.) A FreeDOS kernel developer would have to work through the DOSLFN source to check this. Regards, Christian -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Question about ripcord
There is a simple int21h AH=33h AL=FFh call you can make (no program I know of off hand that does it but from debug you should be able to get it easy) to get a pointer to the version string displayed at boot. Something like (completely untested, possibly simpler ways) this in debug: a mov ax, 33ff int 21 enter on blank line t t r d value in DS:value in AX All it does is use a to switch debug to assembly mode, input the instructions to execute the kernel interrupt that returns the version string, then trace just those two instructions (do not run with g), display the registers so you can see the values returned in DS:AX, and then using those values display (dump) the data there. The pointer is returned in the DX:AX register pair, not DS:AX. With FreeDOS DEBUG, the registers can directly be used in the d command, too. These lines can be entered on FreeDOS DEBUG's prompt then: a mov ax, 33ff int 21 t t d dx:ax The first ASCII zero (00 in the hex view) ends the returned string. Enter a single q on DEBUG's prompt to exit DEBUG. Regards, Christian -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Reporting two tiny problems
1) When the CONFIG.SYS menu comes up, no matter how many options the menu has, I can only access the first three. I can move up and down with the arrow keys, but I can go no further down that to the third option. This happened from the moment I first installed it, with the default CONFIG.SYS, but I tried modifying it and the same thing happens Might be related to the fact that option #4 doesn't work since there's no line which uses option #4. If you understand the FDCONFIG.SYS menu structure, add some line which does nothing and is executed for all options. 2) If I'm running FreeCOM (COMMAND.COM) and I run an application with a command line and add a redirection operator, trailing spaces after the command line and before the operator will be passed to the application, often causing it to fail the purpose of the command. For example, if I type MYPACK myfile.dat result.txt, I may get a message like File not found: 'myfile.dat '. Or more common, if I enter EXTRACT thisfile.pak |more, it may come up with Invalid file name: 'thisfile.pak '. Extension should be '.pak' or '.zp'. Things like that I know I can easily avoid these instances, but in the event that they are easy to fix, it's something. This behaviour is consistent with MS-DOS COMMAND.COM's. Fix your programs to cut any trailing and leading whitespace (tabs and spaces) from the command line before using the filename. Regards, Christian -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Error loading OS: FAT32-LBA problem or something else?
Hi Jerry, After installing FreeDOS on a FAT-32 partition, I attempted to boot it in a couple of ways, each of which resulted in the message: Error loading OS immediately after all the BIOS blather. This message possibly isn't displayed by FreeDOS boot code. I think neither FreeDOS's MBR, boot sector or kernel contain this message. Thus I'd assume it's from the Windows MBR. (I'm using a localized Windows so I can't compare it to the message of its MBR.) a Western Digital 160 Gb disk, in the typical marketing way of using powers of ten, not two, so it really has about 149 Gb. Use binary prefixes then. I offer this info only to demonstrate that Grub had been capable of booting something beyond where XP was installed.) I'd created the FAT-32 partition from XP using the disk manager. Then you might have created a logical partition. You might not be familiar with the difference between logical and primary partitions. However, the default Windows and FreeDOS MBRs don't support booting from logical partitions (GRUB does), and that's most of the difference anyway. Even with GRUB, the FreeDOS kernel might not work when booted from a logical partition. Ask the kernel developers about that. GParted should display whether your FAT32 partition is a primary or a logical one. (Logical partitions are contained within extended partitions.) If you recreate the FAT32 partition with GParted, it should also allow you to select whether it should be logical or primary. (Personally, I'd prefer GParted over the Windows disk manager for most partitioning-related work anyway.) I made the FreeDOS partition active from XP, and tried rebooting. This generated the error message above. That Windows allowed you to make the partition active is strange. If it really is a logical partition, it shouldn't allow you to do that. If my assumption is wrong and the partition is a primary one, everything should work fine for you. Speculating the perhaps the installation hadn't installed a partition boot sector to the FAT-32 partition, I rebooted the FreeDOS CD, went to the C: drive, and issued the command sys C: which reported sectors/trk: 63, heads: 255 hidden: 78397200 FAT starts at 4AC3F10 + 26 (78397200 + 38) Boot sector load seg ... 60h The word hidden next to the number that curiously matches where FAT starts has me suspicious, for some reason. :-) Hidden sectors is the usual term for sectors in front of this partition, and was just abbreviated to hidden here. FAT starts means the first FAT's first sector, which of course is inside the partition. It's somewhat useless, but this message from SYS always displays the same number twice. Anyway the hidden number doesn't mean the partition itself is hidden at all (although I understand your suspicion). I found a prior article on the mailing list in which someone reported, around 2007, that FreeDOS had problems with FAT32, sometimes mistaking FAT32-LBA for FAT32-CHS, or something to that effect. It might be caused by this. You can update your SYS program with a version from kernel 2039 first, that could fix the problem already. This version of SYS also allows you to overwrite SYS's broken auto-detection (the only actual problem) using the option /FORCE:LBA (which isn't documented for some reason). The author indicated that there exists a Perl script (!!!) to fix this. Sounds adventurous. That might have refered to the Linux script which was written so a boot sector could be written to a DOS partition from Linux. This however is a SYS replacement, not a fix for the broken SYS. It won't help you if an updated SYS doesn't. Does anyone have insight into this? Is it the 1024 cylinder problem? If anything with cylinders is involved, SYS would have installed the CHS boot code (which can't work for your partition). With LBA, the boot code and kernel and operating system don't have to care about cylinders or heads or tracks at all. Is there a practical workaround besides using FAT16 (kind of ugly for an almost 1 Gb partition)? FAT16 possibly wouldn't help either. And I'd use it only for partitions up to 512 MiB anyway, anything larger than that is inefficient. Sorry for the long message. I'm never sure how much detail to include. I know that too little is pointless, since nobody can help if they don't have the facts. That's right. So writing a long mail is indeed better. You don't have to apologize for that, even if we don't need all information you sent. Regards, Christian -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference
Re: [Freedos-user] Booting without hard disk
Floppies are definitely NOT the most reliable DOS boot media. After a year or so of daily use, they will likely become unusable. So unless they keep a ready supply of spares, you're going to have some upset clients. I would go the cd-rom or HD route, because USB drives stick out and are easy to break off. Break how? Breaking off means falling out of the port or being disconnected by accident. I'd definitively prefer CD-ROMs or HDDs as well, simply because I won't depend on good BIOS USB drive support for DOS. As Eric mentioned, there are adapters which allow replacing HDDs with CF cards. There are also SD card adapters but these contain an actual chip and therefore usually cost more. (Both of these adapter types look to the BIOS and software exactly like a HDD.) Regards, Christian -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Malware5.
I just tried sending two versions to Pat, one the suspect tarball, the other an 'rar' type file; the gmail accepted the rar but rejected the tarball, saying; this file contains an executable and is not allowed; both the rar and the tarball contain executables? they both have them encapsulated in compression files, yet the gmail balks at one and not the other? --kurtwb2...@gmail.com. Gmail blocks executables, some archives with contained executables and some archives generally. This also depends on the archive type and encryption. (Even worse, incoming mails might be blocked without you or the sender being told.) Regards, Christian -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Disk checking and defragmentation
Hi, Thanks for your interest. Thanks for reporting to the list! One exception is DOSLFN, which I occasionally used in combination with the file managers NDN or File Wizard to decompress files with InfoZip. Whenever DOSLFN was used, CHKDSK would find dozens or even hundreds of damaged files. In addition, strange folders or files appeared which could not be deleted. To get rid of them I had to copy the usable files to a second hard disk and reformat the first. This happened three or four times, in two different computers. Did you use the latest DOSLFN version (from Jason Hood)? More importantly, notice that DOSLFN can be disabled or unloaded without rebooting. Did you disable it (or restarted the computer, without DOSLFN) before running CHKDSK? I'm uncertain about this, but enabled DOSLFN might cause weird CHKDSK (or DOSFSCK) behaviour. Disk-caching software such as LBACACHE or SmartDrive might also lead to problems (either stand-alone, or only in combination with DOSLFN). Do you use any cache? For instance, I have not been able to understand how to use the DOSFSCK with the -V perform a verification pass option. The logic behind it is clear: let's have a look at things before changing them. But when the program runs, it just writes: dosfsck 2.11.DOS3, 8 Aug 2007, FAT32, LFN Starting check/repair pass. Starting verification pass. c:: 33412 files, 42820/65505 clusters That confused me. Does it mean the disk is OK? Is there anything else to be done? Yes, such a screen means DOSFSCK didn't find any error either in it's first pass or in the verification pass. I usually run DOSFSCK with the -r and -t options too, which enable interactive operation (DOSFSCK will prompt you what to do on errors) and testing whether clusters are bad. Your appended NSSI report says there's no XMS (HIMEM) or EMS (EMM386) driver installed. Is that your usual configuration? This might cause problems. I think DEFRAG and software ported to DJGPP (such as DOSFSCK) might run better with XMS than with raw extended memory. Regards, Christian -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Over 4-GB for FreeDOS, Etc.
I have never seen a RAMdisk that was not file-based Maybe we have a misunderstanding here.. The driver itself is of course a file, but the disk is a DOS block device, so for DOS it is just a bunch of sectors. The DOS kernel will then use those sectors as a FAT filesystem which can contain files, sure, but the ramdisk itself has no idea what a (FAT) file is. It only needs to provide an initial state which looks like an empty formatted FAT filesystem. NO misunderstanding, and that is exactly what RDISK and other RAMdisk drivers do. After setting RAM memory to an initial state, a RAMdisk does memory-moves, not file transfers, with a one-to-one correspondence -- every DOS read or write to a RAMdisk causes exactly one XMS move request. Thus, one is better-off viewing a RAMdisk as a FILE handler, rather than a sector handler. Looking from DOS, the RAM disk is a block device. It doesn't handle data on a per-file basis; I don't understand why to call it a file handler then. It handles or provides sectors to DOS and that's it, so one is better off viewing a RAM disk as a sector handler. The Phantom RAM disk presented in the Undocumented DOS books was a file-based RAM disk: it hooked the redirector interface and provided the appropriate functions for each file. These files were stored in Phantom's own file system, in RAM. (Of course it makes more sense to use DOS's built-in file system driver, but the UDOS guys just did it to show how the redirector interface works.) Unless you recently changed RDISK to use the inferior redirector approach (that was a joke), it's still a block device as last time I looked at the source. What do you define as DOS read? Calling the Read from file DOS function? If that's the case then you're wrong, DOS usually calls block devices multiple times to read the FAT and the necessary sectors of the file's data to carry out such a request. If you meant DOS read as reading a single or some sectors from a block device, this is correct. Regards, Christian -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] RAM disks jokes (Was: 4 GB for FD etc.)
neither as any sort of insulting joke, nor otherwise! You found that joke insulting? If that's the case, I'm sorry. It wasn't meant as attack, neither against you nor your software nor anyone at all. If you meant DOS read as reading a single or some sectors from a block device, this is correct. Fine, Christian, that is EXACTLY what I meant! Thank you for clarifying this. Thus UIDE is a pure SECTOR handler and Couldn't care LESS about any DOS directory structure. Our whole point is: Except when the data is initialized, the quoted text applies for a RAM disk as well. I won't go into more details regarding file allocation tables, file systems or formatting now because it won't be worth my and your time. However there's something we can agree on: to the user, any RAM disk (whether using a block device or redirector approach) is made up of a drive letter possibly containing directories and files. Naturally, this explanation doesn't cover any technical details at all. I wish you Lots Of Luck dealing with those who MAY NOT be as forgiving of your jokes, Yes. I'll try not to tempt you with any more complicated phrasing. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Over 4-GB for FreeDOS, Etc.
JEMMEX could use big pages or PAE or both to access more RAM for various things, but this always leads to the question: How compatible will it be? At the moment, JEMMEX already is too fancy for many ancient DOS games which use pre-VCPI DOS extenders, I think any protected-mode memory manager (EMM386) disables ancient DOS extenders which have to start from real mode (i.e. pre-VCPI). so it is good that HIMEMX and JEMM386 are still separately available. Separately from what? Regards, Christian -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Over 4-GB for FreeDOS, Etc.
so it is good that HIMEMX and JEMM386 are still separately available. Separately from what? Separately from MS-DOS, FreeDOS, or other DOS variants, since few if-any of their EMM drivers are still under maintenance, and as some have never corrected BUGS! I support your intention (i.e. JEMM being the best available PM memory manager) but the answer doesn't fit what Eric said: At the moment, JEMMEX already is too fancy for many ancient DOS games which use pre-VCPI DOS extenders, so it is good that HIMEMX and JEMM386 are still separately available. Also, isn't JEMM actually FreeDOS's memory manager of choice? I suppose there was such a thing as FreeDOS EMM (that from which JEMM was created) but is it still maintained? Regards, Christian -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Whatever happened to freedos-32?
As far as I can tell, the last commit in the SVN for the project was in 2007, so it's either abandoned, in hiatus, or going so slowly that no commits have been pushed through in the last two years. I contacted Salvo a year or so ago and he said there's still work on a new version which will replace the current one. Here's what he wrote me: Salvo Isaja, 2008-05-27: Now proceeding with very slow pace and restarting since the very beginning, mainly due to licensing issues (i.e. the GPL is unadeguate). [note that the GPL is the license of OSLib, not LGPL] Reading some old mailing list archives I found, I think it's something about the licensing of OSLib. As previously discussed in the BTTR Software forum, DOS-C (The FreeDOS Kernel) possibly violates the GPL by allowing to load non-GPL DOS device drivers. Now in FreeDOS-32's architecture the native drivers and applications are linked into the kernel or something, so the OSLib guy said they all have to be licensed under the GPL too when using OSLib. Regards, Christian -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS-C and GPL (was Re: Whatever happened to freedos-32?)
With respects to DOS-C, if loading non GPL drivers really did violate GPL, then it would have never been released under GPL. The GPL's text is huge and complicated, if you weren't aware of a violation you might have released program X under GPL though it actually violated the license somehow. The comparison of drivers to OSLib is an apples and oranges comparison. I compared DOS device drivers to the native applications and drivers of FreeDOS-32. (OSLib only comes in as FreeDOS-32 is currently based on it.) A DOS loadable device driver is simply an executable that is loaded into memory that follows a certain calling convention. Depending on the executable type, it may be relocated by the kernel. FreeDOS, or any GPLed MS-DOS alternative, would be totally useless if it disallowed non GPL device drivers, since the vast majority of device drivers are non GPL. Of course. But please read that discussion first and then tell us it doesn't apply: http://www.bttr-software.de/forum/forum_entry.php?id=6796page=0category=0order=last_answer Besides, Richard Stallman is well aware of our project and would have contacted us if he felt we were doing something wrong. I wasn't aware Richard Stallman is a DOS internals expert. Please don't argue by showing me people which don't believe in something, rather, stay with actual facts about the kernel and device driver interface or the GPL. Regards, Christian -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS-C and GPL (was Re: Whatever happened to freedos-32?)
I have simply stated our position. I thought you wanted to discuss it since you even opened up a new thread for it. Regards, Christian -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] printing to USB
Well, 17 lines of Assembly and 5000 of C, It would interest me where he stated these numbers. He did not. I just did unzip -p the-sources.zip *.a* | wc :-) So you don't know how many of that 17 lines are commentary only or blank. This is something I'm interested in, so I wrote me a program that counts the total lines of NASM source files, but also showing how many lines contained nothing (blank), only a comment (with ; or as block with %if 0) or actual code (labels or instructions). Who will ever be able to understand and update Georg's host driver? Certainly not anyone except him, since it's closed source. The interface is well-documented and you write software for Windows, Linux, DOS without reading their source, too. And if the people that own the Windows source decide to abandon that Windows version, you aren't able to understand and update it proper either. (understanding means to understand the internal working, i.e. the source code's operation, because I write in response to your might not understand large project.) My point isn't not to write drivers for either software, it's that closed-source software is abandoned if the ones having the source don't update and support it. This doesn't affect users of the software or using it directly. I'm not interested about that. Even if Georg's drivers are faster, I trust Bret's work more Why that? As mentioned, I looked into some of his work. Plus I'm annoyed at how long it took Georg to understand a simple issue of his drivers I asked him to fix. What do you mean by compatibility? Support for most different USB controllers and USB devices. When Bret's finished with UHCI support, both drivers will support the same host controllers. Support for devices depends on which drivers are available for that host software. I think both currently support disks/drives, mice, keyboards and some ports. Apart from IRQ support (good idea) the modularity is similar in both. Are the host controller drivers modular too? This is the part of the host driver which interacts with either EHCI, UHCI or OHCI hardware. I think the 4DOS case was some sort of misunderstanding which later got clarified into a more universal license. Which didn't contain much of the FreeDOS exception stuff anymore I think. All of these programs, as well as their documentation and source code, are freely available to anyone who wants them. Maybe add BSD or Artistic license then :-) BSD doesn't have Copyleft, and it allows turning the program into commercial software. Which Bret doesn't want. Please read through the full reply and discard inapplicable answers then. You also cannot distribute the programs, documentation, or source code and charge (even indirectly) for their distribution. Similar to shareware days - do not charge for distribution. Only that shareware is different - it disallows charging because the author wants to sell it, and doesn't want to lose profit by others selling his stuff. The stack and some of the drivers ARE small because they ARE already written in ASM. I worry that Georg isn't really good in Assembly. Just some of the examples are in BASIC maybe because that could be easier to read. BASIC easier to read than Assembly or C? Than both the Assembly and C code must be obfuscated a lot first. How could BASIC be easy to read? Note also that the low-level calls to the API are almost inline Assembly anyway, working with specific registers and interrupts. Linking an external object module is much better if Assembly parts are required. Regards, Christian -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] printing to USB
Finally someone did the job: Code USB programs with assembly language. Well, 17 lines of Assembly and 5000 of C, It would interest me where he stated these numbers. who will ever be able to understand and update that code? Who will ever be able to understand and update Georg's host driver? Certainly not anyone except him, since it's closed source. I hope at least Bret still understands it :-). What's your point? Good code is easier to maintain than bad code, and by what I've read from him (I previously looked at some of his other programs, before he released the USB stuff) his code is very good, commented a lot and easily understood by anyone able to write in that programming language. I am really curious about performance and compatibility comparisons between the Bret Johnson USB drivers and the Georg Potthast drivers. I'm not interested about that. Even if Georg's drivers are faster, I trust Bret's work more and think he's faster and better regarding support. What do you mean by compatibility? If they both give access to the packet layer (the Georg Potthast one does, afair) through their APIs in some way, it should be possible to write a wrapper: Then you could use device drivers made for one of the 2 USB stacks with the respectively other USB stack :-). I would prefer if a single host driver would become a standard - making such wrappers, which could potentially cause a lot of bugs, unnecessary. By what I've read from Bret's documentation, the wrapper thing might be impossible anyway - Bret's host driver is designed for interrupt-driven background execution. (Since it's modular too, meaning that the main module only contains the host driver, the specific device drivers for things such as disks and pen drives have access to the USB packets using the API.) As said, the FreeDOS OEM edition of the G.P. drivers is free for any use with FreeDOS and has public domain device drivers but a closed source freeware USB stack, Last time someone provided a FreeDOS special licensing (I'm thinking of 4DOS) it wasn't really accepted. Why? Because FreeDOS seems to imply that it can be used on FreeDOS systems only, but not on those running MS-/PC-/DR-/EDR-/PTS-/RxDOS instead. (Whether a system is defined by the kernel only or by a set of distributed programs doesn't matter in this case, it's bad either way.) while the B.J. drivers are completely source available but I could not find the license details for that one. Read the documentation. It doesn't state that it has XYZ's license, but the provided explanation clearly states how the programs are meant to be used. I'll cite USBINTRO.DOC a bit: All of these programs, as well as their documentation and source code, are freely available to anyone who wants them. Should be less difficult to understand. You can use the programs without restriction, but you cannot directly or indirectly use the executable programs, documentation, or source code to create or distribute new programs that are not also freely available. It contains some sort of Copyleft. You also cannot distribute the programs, documentation, or source code and charge (even indirectly) for their distribution. From this, and what I've read from Bret elsewhere, it seems that you aren't allowed to sell the program/documentation/source itself, but usage in a business shouldn't be restricted. (Just ask Bret if in doubt, it's his work.) Note that the cited parts aren't the full license as stated in USBINTRO.DOC. There you'll find some more text with clarifications and such. Essentially, the license is mostly similar to the GPL [version 2] (with emphasis on the mustn't-sell-it-itself point) but MUCH shorter and easier to understand. Regards, Christian -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] update: dos extenders=HX.
Decided to try the minimum functionality of HX; the 'stubit.exe' failed, complaining that the djgpp executable being processed was not PE; I believe that a dj exe always has an 'MZ' stub, and I will verify that. Does this mean that stubit only *checks* the validity of a PE stub and does not make the conversion? I am a bit thick sometimes, but I didn't seem to see anything in the HX package to make that conversion. If it complains that it needs PE executables, it's from the HX DOS extender to run Win32 programs in DOS. To run DJGPP executables, simply use HDPMI32 (which is part of the full HX DOS extender, but acts as stand-alone DPMI server too). There's some way to stub that directly into your (DJGPP) executable as well, or to replace the loader that searches for CWSDPMI.EXE by one searching for HDPMI32.EXE instead. Read the HDPMI/HX documentation, I think it tells you which files contain what type of loader. Regards, Christian -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/blackberry ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Two non-bug reports.
Users apparently don't want technical details on the Freedos-user list however. I don't think so: some want, some do not. The question is that currently there's no way to know about it. So I am almost decided to create that freedos-basic list, so that technical details can run here as usual. The solution is much easier - discuss technical details on freedos-devel and basic things on freedos-user as usual. Maybe recently more people discussed technical details on freedos-user because there is more activity there than on freedos-devel? Of course this should not be a reason to migrate threads or even start yet another list... ;-). Often threads started normal on Freedos-user but the discussion got technical later on. I don't want to be accused of geekifying anyone's list, so I'll simply stop writing any answers here that might be useful to developers for fixing the problem. Good that I'll never have to provide a user mailing list for my software. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Two non-bug reports.
First non-bug: LFN-EN utilities don't work with my FAT32 partition under FreeDOS. After examining the source code, it turns out that the logic was coded in 1999 when the only DOS that could handle FAT32 was MS-DOS. When run under FreeDOS, the utilities assume no FAT32 support, so they misidentify the partition as FAT12. For test purposes, I made a version that accepted the vendor byte FD (FreeDOS) instead of FF (MS-DOS) and it worked, but anything used in production would have to use a different method to determine whether FAT32 is supported (FreeDOS comes both ways, and there are several DOSses today that support FAT32.) There is similar logic that determines which versions of DOS require volume locking (MS-DOS 7 or later.) Fortunately the LFN-EN utilities are open source, so someone could fix this. A reliable FAT32 test method is to check whether a common subfunction of Interrupt 21h, Function 73h (FAT32 extensions) is supported. I disregard any method that works per DOS version. Users apparently don't want technical details on the Freedos-user list however. Regards, Christian -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Minor nit: Norton Utilities slow with FDAPM APMDOS; FDAPM APMOFF fixes.
Norton Text Search (ts.exe) prints about four characters a second when FDAPM APMDOS is running. Setting FDAPM APMOFF fixes this. This may also affect other Norton Utilities. I suspect it's because FDAPM hooks an interrupt for power saving use that Norton was already using for something. Try FDAPM APMBIOS. Does it still affect the program's performance? APMDOS hooks too many interrupts. Regards, Christian -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Fwd: Announcement: New DOS USB Drivers
Anyone these days using UHCI? Yes. PCs are randomly distributed as UHCI and OHCI, acording to chip-set manufacturer. Plus, EHCI (for USB 2.0) coexists with UHCI/OHCI. Older USB drivers usually work with USB 2.0 hardware as well, just not as fast. Regards, Christian -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Incompatibility with EMSDSK #3
DEVICE=C:\DEVS\RDOSUMB.COM #19 * DEVICEHIGH=C:\DEVS\JEMMEX.EXE A20METHOD:FAST FRAME=E000 VERBOSE NOE801 NOE820 NORAM D=0 VCPI DOS=UMB,HIGH DEVICEHIGH=C:\DEVS\EMSDSK.EXE 4364 /c02 ... 6 file(s)101,406 bytes 0 dir(s) 325,632 bytes free Note the reported free value. ... It seems that FreeDOS does not work well with real-mode UMBs, since EMSDSK no longer shows any problems if I rem the first line in CONFIG.SYS and change the NORAM option to RAM. Looking into UMBs (when they are real-mode), I found command.com there, possibly overlapping the EMS frame area. If any UMBs (provided by RDOSUMB) overlap the EMS page frame, this is a certain source of errors. Using your current configuration, inspect which areas of the UMA are provided as UMB and whether any of these areas contains or crosses segments E000h to EFFFh (where the 64 KiB large EMS page frame is). One of the MEM options might show you the (hexadecimal) segments and their size. (If you don't know how to look at the segment and size values, send a list of your UMBs with these values to the list.) If I omit the FRAME option in CONFIG.SYS, then I see thismessage during boot: *** EMS RAMdisk v1.9I (FU - 08/98): ems get frame error and EMSDSK does not install. The memory map in this caseshows no EMM0. Note that EMSDSK might be able to work without page EMS frame, giving you more UMB. Apparently not. You might of course try FRAME=NONE first and see if EMSDSK shows the same message. However many other EMS programs don't work without page frame anyway so I won't recommend running such a system. If you don't use any other programs that require EMS, a better option might be to disable EMS completely (JEMM option NOEMS, and remove FRAME=) and replace EMSDSK by XMSDSK (or the open source RDISK, which also runs with XMS). Regards, Christian -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] USB Question
I haven't tested, but actually *used* these. Several 100's PC's in 20 years ? Hope at least one was from 1990 and also worked :-) Of course PCs from 1990 don't support USB. How do you know? From your probably buggy 6 PCs? So I should throw them all away and buy 1 or 6 new ones ? With EFI instead of BIOS, so very helpful for DOS USB support ??? These are representative statistics, of course. Link please. Otherwise I'll stay with existing hard facts: - From 6 PC's I tested all 6 failed (2 attempted and failed, 4 didn't even try) - There are 1.6 guys reporting to have it working ;-) From what time are your 6 PCs? Any 2004+ mainstream PC I've seen contains a BIOS version which I know supports booting from USB (since I tested these BIOS versions on some PCs). BTW, no 2004+ mainstream PC I've seen (except x86 Macs) contains EFI. Some of the BIOSes require the boot media to be formatted with MBR (as that HP bootable flash format tool creates) but some require super-floppy format instead (no MBR, a single partition). Or exactly: Current DOS versions require this, the BIOS just provides the storage as either Int13 disk *below* 80h (floppy) or *above*(/equal) 80h (hard disk with MBR), and since now I've seen no DOS version to provide any kind of auto-detection, or a manual override to disable/enable the partition table parsing for the boot drive no matter which Int13 unit it is. (Guess to what DOS version I'll add at least the override option ;-D ) Regards, Christian -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] A windows 9x replacement...
and - BTW - FreeDOS does NOT want to be a Windows 9x replacement. Of course not. It wants to be a MS-DOS replacement. The initial question wasn't to transform FreeDOS into a GUI magically but to create a new project for a GUI running on FreeDOS. -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] A windows 9x replacement...
development has been to at least support the versions of Windows that ran on top of dos. This violates the GPL. That sounds interesting. Completely implausible, but interesting. In what way does it violate the GPL? -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] A windows 9x replacement...
What are you talking about? ReactOS is not about Windows Me The request of M.R. (NO, I don't understand it well ... or at all) Yes, it seems you don't understand it, or at least not the same way I do. I don't see where he mentioned Windows Me at all. And Windows 3.x/9x is no DOS GUI from what point of view? They were sold as OS (what they aren't either) back then ... Yes, but everyone technically experienced could tell they weren't and aren't. (Windows 9x arguably tries more to work without DOS, but if it would have been a stand-alone operating system, why boot it from DOS? Because of the compatibility and to give customers a free MS-DOS with the new shiny Windows? You don't say.) Japheth writes on his site that HX's source code is about 100,000 lines of code When in doubt download it and recount :-D Sorry, my little (C) program to automatically count lines only works with NASM source code ;-) Regards, Christian -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] UIDE.SYS
Adding block-device support would take a LOT more code A ramdisk is often a tiny driver. To give block device access to UIDE disks, Okay.. you only need a partition table parser Yes, which would reside in the temporary (discarded) part of the driver. Of course that won't decrease it's size on disk. and a driver similar in size to a ramdisk. No. I haven't asked for adding block-device to UIDE, just non-BIOS disks support... Support means you access them somehow - just adding them to int 13 will not give them drive letters, only lowlevel access. Although it is *obvious* at this time, why not use Int2F.0801 (Add new block device [to the default DOS block device driver]) to add the drives after enabling the Int13 access? The only notice here is that some DOS versions use varying layouts (i.e. MS-DOS 7.10+ with FAT32 EBPBs, and I hope FreeDOS with FAT32 uses the same layout) so such a feature would have to be configured carefully for different versions and code is required to tell them apart. After all, that installation code (which leaves only the actual UPB (DDT) in memory) could easily be moved into another program. It could use a specific UIDE backdoor (or access UIDE's data, or do something else) to get to know which Int13 units are provided by UIDE exclusively; or a generic API could be written which could also process added Int13 drives provided by different drivers. Then the installation program would read from the provided unit to decide whether the first sector is the MBR, or a partition boot sector. It would parse the MBR (if any) and then add block devices for each DOS partition. Regards, Christian -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] A windows 9x replacement...
There is no reason for an MSDOS Windows replacement to be MSDOS compatible. Except to run on MS-DOS as well. As said, it's Microsoft's method to write programs such that they only run with other Microsoft programs although there's no good reason why they shouldn't run with other vendor's programs as well. Freedos doesn't need to be munged to do those things that MS-DOS did that don't make sense. I don't see where it currently does any such things, even in the WINKERN version. Sharing the System File Tables with all other virtual machines (DOS boxes) makes perfect sense because the DOS file I/O needs to be serialized anyway. Need I remind people, you cannot legally run MS-DOS anymore. Get an old MS-DOS or Win9x license and you have your MS-DOS to run legally. It's not something you can legally install to a system that never had MS-DOS. Uhm, why not? Regards, Christian -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] A windows 9x replacement...
HX DOS Extender does support VERY basic Win32 applications, but it is somewhat of a hodgepodge. It's basically using the Windows NT form of Win32 as its base. If that could be refitted to work with Wine DLLs then it would make a lot of the work needed go by a lot faster. Then we would just need someone willing to write the user apps included in Windows 3.11. Either I've missed that HX now supports loading all Windows VxD drivers, or it still doesn't. Regards, Christian -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] A windows 9x replacement...
I try to ask what is going to get done in the next release or when XYZ is going to get fixed and I get attacked. YES, but is cloning of Windaube ME on-topic here at all ? :-D What are you talking about? ReactOS is not about Windows Me at all, because Windows Me is effectively part of the Windows 9x line (and it's the best version of Windows 9x, except dropped DOS mode support). I agree here. A new GUI should not run exclusively on FreeDOS, because that's the Microsoft approach. Ideally, all programs should run on MS-DOS (or DR-DOS FreeDOS + EDR-DOS + RxDOS + ... And create a DOS GUI, rather than a ME or NE clone ... And Windows 3.x/9x is no DOS GUI from what point of view? I would recommend to program your GUI in a way which makes in run on any DOS, using exclusively normal int 21 calls for which you can easily get documentation by reading a MSD INT $21 doesn't provide any GUI ... so you will need VESA + VGA BIOS (+ VGA ports) or VGA + PCI ports + some mouse support (INT $33 is unusable, so a new mouse driver standard) Int21 doesn't provide any multitasking and file sharing stuff or patching of the system to do certain things like writing (virtual) machine IDs into SFTs. All found on Int2F, readily usable if you plan on writing either a Windows replacement (use 2F.16, 2F.1605 as call-out) or a generic multitasker (use 2F.16 except the call-out, there use a 2F.4B multitasker instead because you can't load Windows VxDs) for MS-DOS 5+. Regards, Christian -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] A windows 9x replacement...
probably (correct me if I'm wrong) even more challenging than writing a dos kernel. I think you're right on that. For example, Japheth writes on his site that HX's source code is about 100,000 lines of code, whereas the current RxDOS kernel Assembly source code is only around 35,000 lines (with 10,000 lines of that being only comments, assembler directives, blocks commented out with #IFDEF (NASM %IF) and such). So, ignoring which is more difficult to write, a full Windows replacement will certainly take much more work, just for the typing! And FreeDOS's kernel has been in development for much longer than 2 or 3 years and still isn't 100% compatible to MS-DOS. Because that's not the goal of the kernel. Regards, Christian -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] A windows 9x replacement...
Theoretically, freedos could support an open source replacement. And in my opinion, the only involvement FreeDOS should have is to ensure that any such open source project would have access to whatever they need to run, just like any other DOS application. That is, it should be a separate project. I agree here. A new GUI should not run exclusively on FreeDOS, because that's the Microsoft approach. Ideally, all programs should run on MS-DOS (or DR-DOS or...) as well, or failing that there should exist an adjusted version or a driver that makes the program work on the other DOS versions. I think asking the FreeDOS (kernel) developers to provide technical information about DOS, while not tying the program to FreeDOS specifics, would be most useful to achieve this. Speaking of a Windows replacement, it could be handy to use some of the Windows (3.x) support already embedded into MS-DOS (this is all undocumented by Microsoft, but became documented undocumented by UDOS, RBIL and other sources). Regards, Christian -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Basic sound access in DOS.
Linux has supported ac97 soundcards for years, why can't dos have a .sys driver that can be loaded at boot time to do the same thing? there's a *lot* of motherboards that have ac97 support these days, well over 50%, and having a .sys driver to handle these kinds of boards would add a great deal of usability to dos apps, especially ones that already work directly with sb compatible cards. The problem is that apps working with SB cards usually do this by accessing hardware ports directly (in/out instructions). You can't hook ports as easily as interrupts, so a driver which would provide other sound cards to work as SB would require protected mode. It has been suggested to write the driver as Jemm Loadable Module (JLM) to do this. This could only be loaded by the Jemm386 memory manager. Regards, Christian -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Basic sound access in DOS.
[...] would add a great deal of usability to dos apps, especially ones that already work directly with sb compatible cards. You talk about old apps that make hardware calls. Also would be interesting a standar sound library for new DOS apps. Yes, I talked about old apps, replying to the previous mail. Regarding sound libraries for new apps, I heard there are some around. Maybe someone else can recommend you some of these. Regards, Christian -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] jam
Now JAM loads but takes ca 32kB of RAM, wow. According to the documentation that's Minimum! ;-) (Your drive apparently uses 8 KiB clusters. With 4 KiB clusters or smaller, JAM uses just 24 KiB.) The FAT32 problem is that JMOUNT needs the raw location of the diskimage file represented in 16bit clusters... FAT32 aware kernels (says the RBIL) do not keep a 16bit cluster number in the SFT even for files on FAT16 disks. Where does the RBIL say that these kernels don't set it for FAT16 disks as well? Ok, it's true, but I had to verify it on my machine because RBIL doesn't state this clearly. Anyway, I think it won't hurt FAT32 DOS programs that much if DOS would actually provide the starting cluster in the SFT for FAT16 drives only. JAM.DOC about the DOS OEM/version problem: Incorrect DOS OEM number. Origin JAM.SYS Explanation Your computer has a DOS with uncommon OEM number. JAM device driver accepts any MS-DOS-compatible Operating Systems with version 3.30-7.0 and with the following OEM signatures: 00h - IBM 01h - Compaq 0Dh - Packard-Bell 0FFh - Microsoft If you have received this message, you should contact us for upgrade information. Did anyone try to contact them already? Even if they don't want to release the program or its source for free, maybe they could update it so that it would work with FAT16 drives on FAT32-aware kernels? (Or even with FAT32 drives, but I assume that would take more work.) Regards, Christian -- Register Now Save for Velocity, the Web Performance Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
