Re: [Freedos-user] Installing FreeDOS on the second partition of the disk
On Sun, Apr 21, 2013 at 1:32 PM, Aleve Sicofante asicofa...@gmail.comwrote: 2013/4/21 Felix Miata mrma...@earthlink.net On 2013-04-21 18:19 (GMT+0200) Aleve Sicofante composed: Felix Miata composed: Because the first isn't a bootable OS anyway, I would definitely choose #1, the simplest. If the OS that needs access to the first is old and unsophisticated, another solution might be needed for it to maintain access to it. OK, but even if I choose #1 I'll need a boot manager, right? Wrong. With only one bootable OS installed, and only one HD in the system, there's no compelling reason to have any boot manager. Well, the definitely compelling reason is that the system simply will not boot. That's the whole reason I started this thread. It will boot fine if I install on the first partition, but not at all if I install in the second partition. No other differences involved. GRUB will do? If you want one, sure. Syslinux is another option. And AiRBoot. And others. I'll try GRUB, since I'm an Ubuntu user and I'm already familiar with it. But I'm definitely curious about what would prevent the system from booting if only the second partition is used. There are two different issues here. 1) The hard drive's master boot record (MBR - 1st sector where the partition table resides) must have bootable code installed. If you later intend to boot an OS from the 1st partition then installing a boot manager is a good idea, otherwise you can use the default boot code. You may need to add that code, as depending on how you partitioned the drive it may or may not have been installed. Fdisk /MBR (check the help before blindly doing it though) can do this in FreeDOS or MSDOS. Alternately installing GRUB or SYSLINUX or whatever to the MBR will place its specific boot code there. For the standard boot code you will also need to ensure the 2nd partition (the one with FreeDOS) is marked active (other boot managers may call it make bootable or startable). From FDISK there is an option to indicate the active partition. 2) The default MBR will then load the boot code from the active partition [aka the volume boot code]. This is where the choices 1-5 come into play. You want to choose option 1 to install the FreeDOS boot code to the 2nd partition. Before running sys (here option 5 may be the better choice) make sure that you are running sys to correct partition. The kernel will treat the boot drive as C: Since you are familiar with GRUB, the simplest is to use it and have it chainload the kernel.sys. If you still have problems then I can setup a test computer and send you better instructions for running fdisk and sys, but the combination of those two should get you booting. Jeremy -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Copy from network drive
On Dec 13, 2012 3:34 PM, fav...@mpcnet.com.br wrote: Hi Tom, others, I tested again the copy from network drive. There were about 15 files in the server, to be copied to the client, about 8 MB altogether. Results: - xcopy (FreeDOS): Copied only 3 files before getting stuck and abandoning the task with the error message: unimplemented internal dos function INT2F/120A cannot open source file - xxcopy16 (Pixelab): Missed about 5 files, with same error message as above, but went on and copied the others. Couldn't gather more details because had only 10 minutes to do the tests :=( Regards, Marcos It looks like a critical error is occurring (the retry, ignore, or fail message would probably be displayed if the indicated function was implemented - it is documented as an internal call used when executing an existing dos function). I am not sure the cause of the critical error. It might be an easy enough function to implement so the critical error details can be retrieved. Possible errors could include locking violation, sharing violation, read faults, drive not ready ... Jeremy -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Re : Support for 4k byte sectors
Improved support for sectors other than 512 bytes has been committed, I am still working on it, default support will still be for 512 bytes (currently not while testing). I have tested 256, 512, 1024, and 2048 byte sectors with tdsk (currently my only way to test). Using max sector size higher than 3KB sizes corrupt memory chain during init (haven't tracked down yet). Constructive comments welcome. Jeremy -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS 1.1 boot process ends with interrupt devide by zero and system halt
On Jan 15, 2012 6:04 PM, Ralph Deffke ralph_def...@yahoo.de wrote: Thanx all, but as I said its impossible to figure out what driver is causing the problem, the sequence doesn't seem to be logical to fix the problem. it crashes AFTER the boot has finished. I installed version 1,0 ( 0.87 beta ) with no problem. tx ralph Maybe I missed it, could you describe your computer a little? Real or vm, how much RAM, and any other factors you feel may be important. Thank you, Jeremy -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Re : Support for 4k byte sectors
At this time there are no plans to explicitly support 4K block sectors directly in the kernel. The kernel itself does not support any block devices directly, it relies on the BIOS interface, though additional drives or support may be added through device drivers. I would like to review the FreeDOS utilities to ensure we are optimally using 4K sectored drives when emulation is being used (i.e. 4K aligned read/writes where feasible), but can not provide any specific timelines as I still need to figure out how 4K sectors effect the various utilities and how best to handle them. In your specific case, given that USB support is not directly in the kernel I would need more information about which USB stack you are using to access the drives. Assuming the driver is providing BIOS LBA based extended read/write functions and get device parameters reports sector size of 4K then it may be feasible to update the kernel to support such a device - at least via a kernel provided translation (512 byte emulation) - for data purposes. The boot code is currently limited to 512 byte sectored devices, but actually 4K sized sectors could be supported with a different boot sector if the computer's BIOS would support booting such a device. I would need to research the code and other issues before providing a good response. Its been a while since I read the cluster to sector code, I believe since DOS works at cluster level primarily, accessing 4KB drives is feasible without breaking too much compatibility assuming minimal of 4KB cluster size; though for many DOS programs 512 byte access is expected and would either need to be provided via some emulation or simply indicate such programs are not supported with 4KB sectored drives. Note: I am not sure any current drives/BIOS combinations will actually provide correct sector size of drive. Sorry it has taken a while to respond, I follow the list fairly often but not on a computer and I find it tedious to to reply on a tiny touch screen. I also get automatically emailed for most sourceforge bug issues though I only respond when I have something useful to add. Jeremy -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Weird UIDE.SYS (FreeDOS 1.1 Test) behavior under VirtualBox
On Sun, Jul 17, 2011 at 11:13 PM, Juan Castro jccyc1...@gmail.com wrote: The first line (starting with UIDE.SYS) stays there for 19 seconds. Then the second one (starting with IDE0 Controller) stays there for 49 seconds. Then I get that error message. In a real machine, UIDE loads lightning quick. Screenshot: http://i.imgur.com/7rI2X.png Juan In your Virtualbox configuration (only tested with just released 4.1, but may also work with older releases) make sure under System-Motherboard both ICH9 and Enable IO APIC are selected. This will allow UIDE to load almost immediately same as in VMWare. Note: the IO APIC may not be needed, but Virtualbox won't allow selecting ICH9 without it. I am not sure what this actually changes with the emulation, but does stop the long delay. Also even with the 4.1.0 release, UIDE still displays the EDD error for C: and D: drives (BIOS drives 0x80 and 0x81), but I believe this is another Virtualbox error - haven't had the time to study Virtualbox's source to see what is wrong (I had hoped 4.1.0 would fix it since there is supposed to be a fix with the checksum). Jeremy -- Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos 1.1 distribution...
On Sun, Nov 1, 2009 at 4:38 AM, Michael Robinson plu...@robinson-west.com wrote: The newest kernel 2039 seems to fix a lot of problems. Is there ongoing kernel development? ... Yes, there is ongoing kernel development; but with a low frequeny of updates. Jeremy -- 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] Booting without hard disk
On Sun, Oct 18, 2009 at 4:36 PM, Marcos Favero Florence de Barros fav...@mpcnet.com.br wrote: I built and support a DataPerfect database with 8 computers networked through MS-Client. Since this network is completely dedicated to the database (i.e., it needs not run any other software), I decided to get rid of the ... (1) Which is the best approach to booting client computers without hard disks? This largely depends on the computers and environment they are in. CD-ROM and Network based booting will both be similar in that the commonly (and probably easist) method involves copying a floppy image to RAM and then booting DOS from there with DOS thinking its booting from a floppy. In both cases there are generic drivers that allow access using the BIOS services for the remaining CD-ROM data or Networking respectively, though it is best to load device specific drivers when feasible and continued access is needed. The CD-ROM and USB based booting both require that users not remove the disk, though given you already boot them from floppy this probably isn't a problem in your environment. Most current PCs can boot from USB, CD-ROM and probably Network if its built in to the motherboard, but you need to consider if all will have a CD-ROM drive, if the nic supports network booting and what method [PXE or older technology - for addon nics does it have a ROM chip installed, usually they are sold with a socket that can be used to enable network booting but no chip], and is the USB slot in a good location physically to ensure no one accidently or otherwise removes device/blocks access to other ports in cases where drive is bulky. For less than a dozen computers the cost of USB drive (assuming flash based) is probably not an issue but could be in the general case, wherease CDRs are low enough to not be. For a small LAN there should be no issues with speed/reliability of network, but the server may need to have additional services added if not already, eg DHCP server and TFTP. USB booting may have quirks depending on BIOS, but I've found drive access to generally be reliable (perhaps slow). Anyway from a DOS standpoint, any should be fine once setup. CD-ROM booting is going to be the simplest, its just a matter of taking your current floppy, make an image, use something like ISOLINUX with MEMDISK or even your CD recording software's basic CD boot by specifying image, burn the disc. I recommend the ISOLINUX/MEMDISK approach as it is reliable but also provides a writable drive (though edits don't survive reboots) which can be handy as software often opens files R/W and enables using pipes at the command line (type XX.TXT | MORE); you may not need this in your case. (2) Where do I find the relevant instructions? I am just typing this up real quick so don't have a good answer, but I recommend you check out SYSLINUX's ISO and PXE variants. A google search should find several methods to make a bootable USB disk, but basically depending on if your BIOS expects it as a floppy or hd determines whether you format it as a floppy (1st sector is start of FAT) or hd where you need to FDISK it and then format (1st sector is partition table). Thanks, Marcos Florence Sao Paulo, Brazil Probably didn't answer your question, but if you have a specific question I will do my best to help answer. Jeremy -- 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] translation
On Sun, Jul 12, 2009 at 11:56 AM, Anonym Anonymsenmie...@hotmail.com wrote: Hi! I am very interested in this operating system, and I would like to contribute. I can help by translating the operating system to Norwegian. I have started translating the DEFAULT.LNG from FreeCOM. How do I upload the file to Sourceforge? How do I test it? It will probably not be perfect and complete, but a start. Anyone here that can help? Translations are always appreciated. One of the other developers may have a more updatd reply; its been a few years since I have had time to work on FreeCom and I have not yet set up my computer to do daily builds of it again yet [should be available again in the coming months]. To get you started and for testing it may help to try http://fdos.org/AutoIndex/index?dir=kernel/file=cmd8086.HEAD.ENGLISH.zip This is a special build (a bit old now unfortunately) that includes the language neutral part already compiled and the tools/docs to add a translation. Basically run fixstr lang.lng and copy /b command.bin+lang.dat command.com. which can then be tested (run it and make sure the output is what you expect). As I said its been a while so there may have been some changes to the current default.lng that mean this build is too old to use with your current translation. To have the critical error messages translated does require building command.com from source; which I do not recall off hand the details needed; please send a message to the freedos-dev list if you want to build command.com from source and need help. I lost almost all my access; however if you send it (and any updates) to me privately I will commit them to the SF svn repository for FreeCOM. If you start working on FreeCOM and want write access to the svn you will need to request it from one of the FreeDOS admins. Jeremy -- 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/Challenge ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS boot sequence and sys.com workings
On Sun, Jun 28, 2009 at 11:44 AM, Simon Atkinsonsimonatkin...@operamail.com wrote: Could somebody please point me to site/article that describes the FreeDOS boot process. And I'm interested in finding out more about what sys.com does/how it works, when copying The FreeDOS kernel ..kernel.sys. Does sys.com change the code in the MBR of a hard disk or only the volume boot record on, say on the first partition of a disk? Other than the documentation in the kernel describing usage there is no other documentation than the source itself that I recall off-hand. The simplist and common case of sys consists of sys copying the source files to destination location, this is functionally equivalent to you doing a (replace X with destination drive) COPY KERNEL.SYS X:\KERNEL.SYS COPY COMMAND.COM X:\COMMAND.COM and then depending on options it will update the 1st sector of the specified partition (note: partition not disk, so the MBR is unchanged by sys, only FDISK and similar change the MBR) with the boot code. The sys program contains several forms of the boot code compiled as binary blobs and writes the one for the file system it detects in use (FAT12/16/32, LBA/CHS, etc) and may patch small portions - it actually reads the current boot sector then overwrites only a portion so existing geometry information (as created by the format process) is not modified. The boot sector may instead (or additionally) be written as file, this allows chain loading FreeDOS from boot managers. Currently, once sys has been run (or a equivalent action that writes the boot code), FreeDOS kernel can be updated/changed with a simple file copy command - there is no requirement it be located at any location (other than in root \ directory) on the disk or have any specific attributes (Hidden/System/Readonly). The kernel generally doesn't care how or who loaded it (there may be some issues with the default drive depending on how loaded, but otherwise it will run even it it can't find any drives, just not very useful) only that the complete KERNEL.SYS file is loaded (by default to address 0x60:0) and jmp'd to. The boot process is identical to every other OS for IBM compatible PCs; the BIOS determines the drive to boot from, loads the 1st sector, passes control to it - which is either the boot code sys put there (such as a floppy) or it does something (like display a menu, read the MBR partition table, etc) and loads the 1st sector of the selected parition (repeat ...) until finally our boot code is loaded. Once the FreeDOS boot sector is loaded, it reads from the default drive (as passed from BIOS or hard coded, usually either 0x80 for 1st hard drive or 0x00 for 1st floppy drive) to determine location on disk of KERNEL.SYS (name is actually stored in boot code so can be any 8.3 name) and loads this file, then jumps to it. The kernel does its init logic and passes control to the shell. Where you get the friendly prompt. The above is from memory, but should be correct. If you have specific questions feel free to ask, I will need to look at the source but can answer any specific questions. The current sys source has not yet been merged into svn trunk but that should occur later this week along with ensuring latest country, share, etc are there. The FreeDOS sys has additional code to set and/or view the configuration options that effect the kernel. The latest release has some additional compile time selected funtionality as well. Jeremy -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Incompatibility with EMSDSK
On Sun, Jun 21, 2009 at 2:14 AM, jasse...@itelefonica.com.br jasse...@itelefonica.com.br wrote: FreeDOS (kernel=2038fat16, freecom=082pl3) reports a wrong (about 10% actual) size for a EMS ramdisk created with Frank Uberto FU_RD v.19i. ... documentation says both have just one FAT. I set them with same size and number of sectors/cluster. JAS Does this happen for any size or what size do you create? Thank you, Jeremy -- Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Freedos Future
Norbert Remmel wrote: ... And I think none of you will say that qhimem is a bad product and because of this Jack's memory manager has the right to be a part of freedos, again, closed source or not. That really doesn't matter. ... The flamewar aside I wanted to make a correction to this; Jack himself requested his programs not be part of FreeDOS; it just so happens that his earlier ones with sources are under a license that allows them to continue to be distributed anyway. The other major issue is that for all FreeDOS programs,utilities,etc. source is a very important component; I mean there are tons of good to excellent DOS programs out there, but without source or permission to include they do not belong as a part of FreeDOS [the distribution, not the community]. So regardless of technical merit or not, it really does matter. Jeremy - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] OpenGEM 5 freezes/hangs/locks on FreeDOS 0.9 SR2
Shane M. Coughlan wrote: John Hupp wrote: In the course of off-list discussion, I tested this problem much more extensively than I reported here. My own conclusion was similar to your Situation #3: HIMEM and EMM386 are not at issue, and OpenGEM has one or more incompatibilities with the FreeDOS kernel. But I found further that the problem appeared on FAT32 partitions and not on FAT16 partitions. Perhaps that will further narrow the inquiry. John did indeed debug this quite extensively in a three-way conversation with Eric and myself. The results were: PRELIMINARY CONCLUSION: FreeDOS FAT32 support in FreeCOM/Kernel (wherever that support is located) seems to be the problem. It is [...] interesting that not all GEM apps trigger problems under FAT32. Fgdoodle seems to be the worst, and then the other freehand drawing apps Draw and Paint. So graphical rendering methods connect those. ... Could you (off list if you want) send me a more or less detailed description of which files to get and run and I will see if I can find the kernel issue. Two questions though, did you try with 4DOS or MS Command.com to rule out FreeCom issues (not sure why it would cause it, but I do know it sometimes causes weird issues) and was this with dev kernel, stable kernel, or both? Thanks, Jeremy - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Unable to use Windows for Workgroups with FreeDOS
Blair Campbell wrote: You need to download a special unstable kernel for Windows enhanced mode to work. Also, you never told me whether getting that other kernel I pointed you to fixed the FreeCOM redirect on ramdisk problem. Please do tell me. also be sure to load FD share prior to attempting to start Win3 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] SYS A: C:
Gerry Hickman wrote: Hi, Today I did this from a FreeDOS bootable CD; 1. Use FDISK to delete all primary partitions, but leave MBR 2. FDISK /PRI:2000 (2Gb FAT32 Ext13) 3. FDISK /Activate:1 (boot to first primary at next HD reboot) reboot 3. FORMAT C: say yes to confirm I now have an empty working C: drive with FreeDOS boot sector I insert an MS-DOS 6.22 system floppy into A: and type SYS A: C: (I want to install MS-DOS boot-sector, IO.SYS and MSDOS.SYS to C:) What happens next?? It installs FreeDOS boot sector, and kernel to the C drive!! That's not what I told it to do... Where (what drive) are sys, kernel.sys, io.sys msdos.sys on? Or more clearly is kernel.sys and sys on the same (current) drive and the MS-DOS files (io.sys msdos.sys) on A:, so instead of looking at the source drive sys appears to be using the kernel from the current drive? or are all three on the same drive, in which case you must specify using the /OEM:MS (I think) option so that the FreeDOS kernel is ignored, as default search order [which you may have found a bug in] will assume you want boot the FreeDOS kernel before any other DOSes (unless sys is compiled for Enhanded DR-DOS, in which case it flips FD with EDR kernel names in its list). Also please let me know which version of sys you are using. Thanks, Jeremy ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FDISK bug (sorry I don't know how to use bugzilla)
Johnson Lam wrote: Hi, Actually it's not a BUG, FDISK always FORGET to write the Master Boot Record to the hard disk, just test 2 hard disk this afternoon. That's why the original hard disk still boot up showing LILO. Hope someone can patch the FDISK, it should be easy to fix this minor problem. Rgds, Johnson. Assumming I recall correctly, this is by design, if the MBR is considered non-empty then it is not overwritten on purpose (also only the MBR on the primary drive is ever written to). The purpose behind this decision is to not overwrite LILO or any other multi-boot program or whatever program you have installed on your MBR; to forcefully overwrite use the not so documented /MBR switch (or one of FreeFdisk's other similar options) or clear the MBR prior to fdisking. Jeremy ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dual boot XP/FreeDOS DJ mechanism problem
Robert Ralston wrote: ... But with kernel 1.1.35w Build 2035w-unstable from the 1440 ODIN distribution, everything works with a laptop *if and only if* there is a floppy drive present. If there is a floppy drive either in a bay or connected via USB, then the FreeDOS partition boots normally. However, if that floppy drive is missing, then we consistently get the message, after FreeDOS starts to load: Error in the DJ mechanism. IO error: cyclinder 1023. Bad or missing Command Interpreter. Enter the full shell command line: command.com /P /E:256. There was a recent fix to the unstable kernel to better support floppyless systems. If possible please try a current 2035w from http://www.fdos.org/kernel/ and let me know if that makes a difference. Note: -W is the development [UNSTABLE] kernel branch (more features but less tested). There are also builds of updated stable (release branch in cvs but not versioned releases) kernels here as well you may wish to try. At first I thought maybe there is something wrong in the MBR. Used ... QUESTIONS: What distribution had kernel 1.1.34 on it? Is that distribution still available? I don't recall, probably original Beta9 or Beta8; all distributions from Alpha5 are still available so yes it is available; however, it sounds like all you need is the kernel, so I would recommended instead of downloading the whole distribution to check the FreeDOS sourceforge site and just download the kernel directly (easiest way to get a particular released kernel). Any suggestions about what I may be doing wrong. I'm not a DOS expert by any means. sounds like you hit a kernel bug, testing to see if it is fixed in current kernels would be of great help Thanks in advance for any suggestions. Robert Jeremy --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] daily kernel builds WAS: Re: dual boot XP/FreeDOS DJ mechanism problem
Johnson Lam wrote: On Sat, 11 Mar 2006 08:20:30 -0500, you wrote: Hi Jeremy, There was a recent fix to the unstable kernel to better support floppyless systems. If possible please try a current 2035w from http://www.fdos.org/kernel/ and let me know if that makes a difference. Note: -W is the development [UNSTABLE] kernel branch (more features but less tested). There are also builds of updated stable (release branch in cvs but not versioned releases) kernels here as well you may wish to try. I got the latest kernel (386), and surprise that the date is MARCH. Are you using CVS auto build or manually compile? cvs auto build, or more specifically I have a computer set up that once a day (usually around 3pm my time assuming I'm not using the computer for some other purpose that prevents this from running) does a cvs update and compiles the kernel and freecom and uploads these builds along with source archive. This is automatic [batch file based via an NT scheduled task], it cycles through using various compilers and a few different options (8086, 186, 386, Turbo C, OpenWatcom, ...). I do this so anyone can test the latest development kernel and obtain the most bugfixed stable kernel between releases (which are far between and few currently). I haven't figured out (nor looked very hard) an easy way to determine if cvs update changes any files and thus a new build is actually required or not, so the date will reflect when built not most recent changes (currently mid Feb for cvs kernel). Within the test directory are the kernels from one of my various local trees that I manually compile. My various local trees contain my in progress or stalled work including the int13 work, ms/pc dos config syntax compatibility, isolinux/memdisk option retrieval, no fnodes, increased windows compatibility, fd specific ifs stuff, fat+, or generally stuff I'm working on that is not ready for general usage. Also is there any change log? there is the history file in the docs subdirectory, but I'm bad about maintaining it, before [version not year] 2036 I will try to ensure its updated. The best way to view changes is to watch the [archived] freedos-cvs mailing list which shows all commits (or via cvs log). Thanks. Rgds, Johnson. Jeremy --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] DOS dialup
Jose Antonio Senna wrote: On Sun, 12 Feb 2006, dima wrote: Long time I used dosppp and lsppp while had real IP the address. Recently ISP has placed the users behind NAT and now users have grey IP addresses. The problem since then has begun - dilal-up connection is established, ping - is present, but TCP connection can not be established: lynx and arachne do not load any web pages. Advices are welcome. What is NAT ? (At least this is what I generally see it referring to) Network Address Translation, commonly seen in home/small office type broadband router/switches [e.g. Linksys, Dlink, Netgear, Belkin products], it allows multiple (usually private) IP address to masquerade as a single (usually public) IP address by mapping the outgoing/incoming ports to appropriate computer. From what you said only, it seems the problem is in WATTCP. Regards JAS As for the actual problem, I have no idea, been far too many years since I setup dialup, so all I remember is once connected, authentication had to occur to allow general IP traffic. Jeremy --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Linux Tools and FreeDOS Dual Boot LiveCD
... The image is about 32.5MB. Does anyone want to try this image? The directions I have available use the same programs and are quite close. You could install FreeDOS using this in two reboots and burning only one CD. I can send you a very detailed PDF procedure. ... I have uploaded fdinst09.iso, an ISO image combining the GParted 0.2 Live CD (with fdisk added), odin1440.img from odin 2005, and the GAG boot loader image. You select at the BOOT prompt which you want to run. This will allow installing FreeDOS in three reboots (sorry I said two earlier: 1. Boot LiveCD to shrink NTFS partition, create new one and add the type. 2. Boot GAG to install the new boot loader 3. Boot ODIN to allow you to SYS the appropriate drive and copy the necessary FreeDOS files). The procedure on it has not yet been updated to reflect this and still refers to the Mutagenix LiveCD and burning your own GAG and FreeDOS images. The beta procedure is available in the DOC directory. Everything is GPL, properly attributed, and I am releasing the composite under the GPL. I will probably use a Creative Commons Attribute/Share license for the procedure when I get around to that. ... I have not had a chance to test yet, but for those wanting it sooner rather than later, I'm hosting it for Mark on my fdos site. Download as http://odin.fdos.org/dual/fdinst09.iso I also extracted the documents from the image and placed at http://odin.fdos.org/dual/doc/ if you want to read them prior to downloading the full CD ISO. Will probably mirror onto ibiblio when I get a chance (sooner if this is really popular :-) Jeremy --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] re: Maybe stupid question (LBA48)...
... and Arkady's FreeCOM. ... What changes are in this? and where is it? curious, Jeremy --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Soundblaster setup
[EMAIL PROTECTED] wrote: I've managed to install the mwave drivers with the MS boot floppy and there is no error messages while loading the drivers. But I can not test the sound because every applications which use sound says that there is no enough memory to run. I've setup the MS config.sys on floppy to load DOS high, but it doesn't help. What should be the next step? How can I adopt the drivers to FreeDOS? If they aren't already, copy the mwave directories to your FD drive, then copy the entries added to your config.sys autoexec.bat for MSDOS to your config.sys autoexec.bat for FD (adjusting paths as needed). See if the driver loads ok. If it does then hopefully you will also have enough free memory to try and use the sound. If it doesn't then your options are either not use FD with sound or work with me running a bunch of tests to help track down the incompatibilities hopefully leading to a fix. Jeremy --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Soundblaster setup
Blair Campbell wrote: 1/That isa card don't work at all or 2/ I need to enable in in BIOS by assigning some system resources to it, but I don't have any documentation for Usually you must set %BLASTER% to the resources (IRQ...) of the sound card. If it is not a sound blaster, you also need a driver. Since you say it is a sound+modem card it is possible they share hardware, in which case it most likely will not work without associated software driver (an example would be mwave that was used in older IBM Thinkpads). Of course it could simply be a an ISA-PNP [plug-n-play] card you may have to configure the resources the card uses; some BIOSes may do this, but usually a program accompanies the card and will do this for DOS, alternatively the ISAPNP program may work (a real mode DOS version is on darklogic.org somewhere or a DJGPP compiled DOS version is available from the maintainer's site, sorry I don't have the url handy). I'm sure you have, but be sure if you want to play CDs directly (as opposed to an audio file like a VOC or WAV) that you have the cable connected from the CD-ROM to the proper input on the sound card (some have multiple ones). Sorry, but without knowing what exact card you have I can't provide any good advice. Jeremy --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Windows 3.x and FreeDOS kernel
To avoid sending a bunch of updates and annoying those who don't care about Windows 3.x support please see link below for detailed information and any updates. Quick summary, the FreeDOS kernel is mostly compatible with Windows 3.x, including full screen and windowed DOS boxes and enhanced mode. There are still a few glitches, closing a DOS box tends to kill input for remaining open ones. Most of my testing done using himem included with Win and 4DOS instead of FreeCom. This may be a symptom of incorrect instance information or ??? http://wiki.fdos.org/Main/Windows has all relevant details. If you are interested and/or have Windows 3.x please test the kernel and add your experiences to the wiki. Thanks. Jeremy --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] re: DOS Boxes working!!!
Eric Auer wrote: Hi all, thanks to Blair for telling me about HXRT and big cheers to Japheth for his HXRT DOSX variant :-). So yes, DOS boxes work in WIN /S (only full screen DOS boxes, which are suspended while they are not the foreground task - classical WIN /S style imho) with his DOSX in FreeDOS :-). Note that SHARE must be loaded. ... Should also work without replacing DOSX, at least latest dev kernel does for me (haven't done much testing though), assuming share is loaded. Jeremy --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
sys Was: Re: [Freedos-user] FreeDOS FDISK issue with Windows Build
Johnson Lam wrote: On Thu, 18 Aug 2005 21:59:00 +0200, you wrote: Hi Bernd, In sourcecode, SYS v3.6 is still under development :) If you didn't write here, I don't even know there're hidden switch, how can I test? It is documented, within kernel source doc directory and at http://freedos.sourceforge.net/kernel/docs/sys.htm Without enough testing, more delay to an official release ... this function may help to installing a stupid WinXP which SEEMS to check the bootsector. Same for SYS: an option to keep using the MS bootsector instead of installing an (not always working) FreeDOS replacement bootsector for MS system files. /OEM:Auto means FreeDOS? /OEM:XX where XX determines which DOS you want to boot; it chooses/alters the bootsector to be compatible with the given DOS. For FreeDOS all that is really required is passing boot drive in BX and loading full kernel (Enhanced DR-DOS is similar, except uses DX), and MS/PC DOS have a heap of expectations (less so in newer releases). The AUTO option (which is the default) determines based on which files are present (with a hard coded list, the order of which determines the one selected should multiple kernels be present); however due to the similarities, EDR-DOS will be used instead of PC-DOS so PC-DOS must always be manually selected. Rgds, Johnson. Jeremy --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: sys Was: Re: [Freedos-user] FreeDOS FDISK issue with Windows Build
Bernd Blaauw wrote: Kenneth J. Davis schreef: It is documented, within kernel source doc directory and at http://freedos.sourceforge.net/kernel/docs/sys.htm Strange that it says WinME is unsupported, and doesn't mention if Win9x FAT16/32 bootsector works or is (still) broken. somewhere 'segent' -- 'segment' WinME is special since MS partially crippled it. I'm not sure if it works asis or only if you use the emergency boot disk version; from sys' standpoint it is treated as Win9x (has same boot requirements), but there is no intention to add any special code for it. But yes the Fat16 bootsector is still broken (I think I need to drop about 9 more bytes from my current shared Fat12/Fat16 all DOS bootsector [patched by sys with specific instructions to fit the selected DOS]. Technically Fat12 is broke to, but because the FAT is small enough it still works. looks like I confused SAVEBS with BACKUPBS, my apologies. :-) I added them and I still have to look them up I need to verify that the description for /RESTORBS is correct (does not modify it only writes it to disk. Which if that is the case then I need to add another option, perhaps /UPDATEBS which will take a bootsector supplied by the user same as /RESTORBS, but will update the geometry information in the BPB. [/RESTORBS may do that, in which case it will need changing to reflect the documentation and new switch added]. To summarize for all those wondering about these switches, /BACKUPBS indicates that when sys works as usual, it will save the existing boot sector prior to any modifications that would occur /DUMPBS does the same action as /BACKUPBS, but exits without doing the normal sys actions (ie just save current boot sector to a file) /RESTORBS reverses any actions sys did to the bootsector by restoring the bootsector saved by either /BACKUPBS or /DUMPBS to be added /UPDATEBS would take the bootsector as saved by /DUMPBS or possibly /BACKUPBS and adjust its geometry information to match to drive applied to; so in theory you could apply vendor X's boot sector originally saved from disk A to disk B and it would boot [where disk A and disk B are do not have identical geometry]. Regarding the MS install issue, one could do something like format with FreeDOS format, then use FreeDOS sys to install MS-DOS files/bootsector via its /UPDATEBS (and obtained by its /DUMPBS, winimage, any other bootsector extracting program, or even from a disk image), etc. /OEM:XX where XX determines which DOS you want to boot; it chooses/alters the bootsector to be compatible with the given DOS. For FreeDOS all that is really required is passing boot drive in BX and loading full kernel (Enhanced DR-DOS is similar, except uses DX), and MS/PC DOS have a heap of expectations (less so in newer releases). The AUTO option (which is the default) determines based on which files are present (with a hard coded list, the order of which determines the one selected should multiple kernels be present); however due to the similarities, EDR-DOS will be used instead of PC-DOS so PC-DOS must always be manually selected. /OEM:AUTO usually will mean FreeDOS is preferred, yes. When you want to force writing a FreeDOS bootsector , use /OEM:FD /OEM:MS and OEM:W9x are difficult to use, as you cannot determine in batchfile or commandline when looking at the system files which operating system is used. Only thing you can determine it's Windows instead of MSDOS is if you see IO.SYS on a fat32 partition. does this imply you think an /OEM:?? that indicates generically MS DOS (version 6 or earlier and win9x DOS version 7+)? What two letters abbreviation would you suggest? I'd prefer not removing W9x and merging them both into MS; but will if the consensus is this is preferred (since the filenames are the same it is unlikely for both to be on the same disk; but if they were using alternate names how would a user select the correct one?) Bernd Jeremy --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS FDISK issue with Windows Build
Gerry Hickman wrote: Hi Kenneth, can't work out how these numbers relate to the directory listing on the fdos.org/kernel website. 4 different versions, 2034, 2035, and 2035a are on sourceforge file release page, cvs kernels are the ones (either stable, eg 2035a-cvs or devel 2035w-cvs) on fdos.org I'm currently looking at this page http://fdos.org/AutoIndex/index?dir=kernel/ But I can't see anything that says 2034, 2035, 2035a. Can you advise which file I need to download? Sorry if it's obvious! To get 2034, 2035, 2035a, or any other released version, please see http://sourceforge.net/project/showfiles.php?group_id=5109 as all releases are available on Sourceforge, only cvs builds [unreleased daily builds of current source; no version] are available on fdos.org, ie pre-release (stable series) and development builds only). Sorry, again I don't understand. I don't see anything called 0.84pre on the fdos.org/kernel page or directory listing? it is the cvs one, cmdxms.*.zip or similar; or any other than the one named command.com (which I think is the last officially released one). 0.84 will be released soon, I'm looking at the page now, but all the cmdxms.*.zip are saying they are HEAD, and I believe I need the unstable branch to test this... FreeCom only has one branch that I touch (HEAD is just cvs terminology for the primary branch); though other branches do exist (state unknown and/or already merged into HEAD). I updated the descriptions a little, so hopefully it is clearer which are the recommended versions for more general testing/use. Jeremy --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Bulding FreeCOM? Where is suppl.zip?
[EMAIL PROTECTED] wrote: Hi all: I don't see an obvious problem with FreeCOM's delete function. I also won't be able to build a meaningful test case using Open Watcom. So, I need to build FreeCOM with some debugging code. The build instructions reference a precompiled SUPPL.ZIP file which I can't find. Where can I get this? Mark A variant is included within FreeCom cvs, it is built as part of the normal building process (though precompiled version can still be used). I forget the exact url, but check out Steffen site, most FreeCom links should still refer to it. Jeremy --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] More FreeDOS FDISK tests - failure is repeatable
Michael Devore wrote: At 04:01 PM 7/21/2005 -0500, I wrote: When you invoke FDISK without arguments, it goes into the Interactive_User_Interface() routine. That, in turn, asks about FAT32 support, via Ask_User_About_FAT32_Support() function. OK so far. After that call -- without any further prompting -- FDISK calls the Create_MBR_If_Not_Present() routine. NO. Please, no. You should never write to the hard disk for low-level stuff like partitions and master boot record data without warning and giving the user a chance to abort or decide not to do it. Second related issue...the Create_MBR_If_Not_Present() routine receives an error code if Read_Physical_Sectors() routine fails, but the error code is not checked. Consequently, should the routine to read physical sectors fail for any reason and return an error, the following occurs: The buffer which was not loaded by the read is still tested for valid values and if they fail to match what was expected (as they likely will) a new MBR is written. That is probably the wrong approach to handling an error on the low-level disk read. Particularly at startup. I have a work in progress towards fixing these issues of fdisk, to try my current build - http://www.fdos.org/kernel/test/fdisk.exe Currently I have it so it delays actual writing of MBR to disk until just before program exit (so if you reboot or in advanced mode abort your changes, the mbr=CHS(0,0,1) should be unmodified). It also now aborts on read error with a message. Note: fdisk may still write to other sectors than mbr during use, eg boot sector of partition. This build also has a pause and message that shows the disks the MBR is being written to. I'll continue working on this a little while longer, but this build is here for feedback. Jeremy --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] More FreeDOS FDISK tests - failure is repeatable
Anyone know if Brian is on fd-user list? or otherwise been notified of these issues? I don't think it will be too difficult to correct (warn/abort at least) so maybe if I get time after work tommorrow I'll make a patch available to make fdisk safer to use. Thanks for reviewing the code, Jeremy (hoping Brian is still around...) Michael Devore wrote: At 04:01 PM 7/21/2005 -0500, I wrote: When you invoke FDISK without arguments, it goes into the Interactive_User_Interface() routine. That, in turn, asks about FAT32 support, via Ask_User_About_FAT32_Support() function. OK so far. After that call -- without any further prompting -- FDISK calls the Create_MBR_If_Not_Present() routine. ... --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] re: FreeDOS kicks some serious Ass!
(this message just appeared, else I would have answered sooner) Gerry Hickman wrote: Hi Eric, you should try ODIN or the bootdisks on fdos.org (fdos.org/kernel/ also has the newest kernel and shell versions, More zip files, more URLs! http://fd-odin.dosius.com/ (says it's the primary but I get DNS lookup failure) this is the original site where the Odin distribution was published http://odin.fdos.org/ (this one seems to work) http://www.ibiblio.org/ (who knows?) http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1disk/odin060/ these are mirrors of the Odin distribution, though now seem to be the primary locations (the fdos one also has the old versions) http://sourceforce.net/ (various) http://www.fdos.org/ (says it's a mirror but looks different) it is both; it mirrors the main freedos.org site, visit http://www.fdos.org/freedos.html or for the Spanish (little outdated) http://www.fdos.org/es/FreeDOS.htm the rest of the site is where I post my FreeDOS related stuff, or anyone else who has expressed an interest but doesn't have hosting abilities; in particular, official distributions would be here first then I'd mirror to ibiblio, I have boot disks (trying to get people to use alternate disk images than the install one), and currently where I upload near daily cvs builds of the kernel freecom. http://www.freedos.org/ (seems to be down right now) probably visited during the move? Then they all have links to even more links, and some go round in circles, way too much information for my type of brain. :-) Your not the only one, but some days its fun just following them, even revisiting old information I'd forgotten In short, ODIN has the very strange property of defaulting to F5 style boot. But it has lots of software included, while the fdos.org boot- disks are very bare :-). I generally have more to do than I have time, so I try to setup builds available on my sites to be automatic; periodically checking on them. So the fdos.org ones are generated from a script, shortly it will be easy for me to add other FreeDOS programs and ensure they are updated. Presently only the kernel umbpci are easily updated, but with upcoming changes, I will be able to automatically update multiple locations (disk images, iso, downloads) by a single commit of updated sources. I can detail my work in progress for the curious, but that's a separate thread. I think that's what I need, the bare boot disks. I didn't find them while browsing www.freedos.org, but I'll check the other sites. I found http://www.fdos.org/bootdisks/ the official CD-ROM image and FDos1440.img files were too complicated, but I understand some people want installable versions that automatically detect hardware. ... (of course you can also work without any UMBPCI/EMM386... I prefer the usbaspi4 and aspidisk drivers for USB, by the way, even DEVLOADable well) These are news to me! Do you ahve URLs? I'm having problems with USB on machines that don't support it in BIOS properly such as ASUS A7V333. I believe aspidisk is included with ASPI drivers; I know source to a basic one is available with Adaptec's ASPI sdk, but I don't recall any exact links offhand. A couple USB [for DOS] sites (mostly contain duplicate information, a few links no longer work, and it should be noted I haven't tried any of them, not using USB myself): http://www.stefan2000.com/darkehorse/PC/DOS/Drivers/USB/ http://www.computing.net/dos/wwwboard/forum/13288.html ftp://ftp.pierskalla.com/pub/dosusb/installing_windows_using_usb_con.htm http://groups-beta.google.com/group/alt.os.free-dos/browse_thread/thread/ca7e1c4a17c8 http://www.bootdisk.com/usb.htm http://www.georgpotthast.de/usb/index.htm http://www.lvr.com/usb.htm http://www.usb.org/ --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Can FDISK destroy partitions using the examine partitions option?
[EMAIL PROTECTED] wrote: Hello, all: I just suggested that someone who was having trouble with NTFS4DOS not recognizing an NTFS partition run fdisk with the development kernel. I requested that he enable large disk support and use option [4], List Partition Information. This appears to have removed the partition information from the MBR. Are you sure fdisk did this and that wasn't his problem to begin with? or something else related to his problem caused the error? Anyone have any ideas about this? Is FDISK so dangerous that even using it to examine partition tables is a bad idea? Thanks. Mark Bailey I haven't looked at fdisk's code in a while, but from my usage, I have never seen it alter the MBR/partition table without issuing a command that involves such a change (ie option 4 never made any changes). And a brief reexamination of the code seems to confirm this (it has checks for changes so only writes if a change has occurred). Brian could tell you for sure (or anyone who wants to read the sources), but I feel pretty confident in saying that using (Free)Fdisk to examine the partition tables should not cause any harm -- but not a method I'd recommend (users can do some funny things), so a tool designed just to display the partition tables would be better. Jeremy --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Turbo C++ 3.0
Michael Devore wrote: At 04:08 PM 6/30/2005 -0700, GNU_manwrote: I just wanted to report that the Turbo C++ 3.0 IDE crashes under freedos :( Believe that was an open Bugzilla item (hard to check right now), but the original person reporting the problem didn't list a way for a non-owner of TCPP 3.0 to get a copy to check it out. Until/unless a downloadable TCPP 3.0 version is available, the bug report will wait for a TCPP owner who is also a motivated FreeDOS developer with the opportunity and ability to fix it. Not a great chance of that happening soon. I have TC 3 (installed from years ago), but I don't have the time just yet to look into it. It's somewhere on my todo list... On the other hand, if someone else has time and wants to track down the problem contact me privately and I can try to find originals of one of my copies. Jeremy --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freecom compile errors
Tom Lee Mullins wrote: Hello All, I am trying to complie the freecom source using all the tools given by them on the site but i am receiving the error.. no such command or file as make i have turboc 1.01 and nasm and all the things given by the site.. i also have installed the latest freedos on my hard disk.. Please help thanking you Maulik Is his config.mak setup with the proper paths? It may help to ensure the borland tools are also in the PATH environment variable. Also, is he using the source straight from cvs or from the archive at fdos.org? (Depending on the branch) the source as is in cvs will not compile, at minimal you need the suppl library and a dummy file (or minimal implementation) as it appears to have not been committed -- I forget which, but check out the patch file included in the source archive of FreeCom on fdos.org/kernel/ [it also contains some additional fixes, so I recommend it over straight cvs source using the head branch] (if he needs further help, you may want to suggest the FreeCom mailing list, FreeDOS-FreeCom) Jeremy --- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61 plasma display: http://www.necitguy.com/?r=20 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Re: [Freedos-kernel] freedos
Geraldo Netto wrote: Hi folks, Some updates Some Eric's comments/suggestions: Hi, could you tell all lists that the discussion / saga continues on freedos-user? I am on freedos-user, freedos-devel ... what discussion? I'm on all the lists except maybe the doc one (though I haven't switched all them over to my more reliable account) and don't have a clue what this is in reference to. have no dedicated doc workers right now (except maybe Johnson I suppose I should check out the doc list one of these days... and Fox) and because Steffen cannot do much for FreeCOM at the moment either. Only few people, like Erwin and Jeremy, can compile FreeCOM at all. it is actually quite easy to build, the real trick is getting the right suppl library, which a minimal version is in cvs now [except the one in cvs was committed in ASCII mode so is an invalid archive]. If you really want to build it, I recommend using the archive on fdos.org/kernel/ as it includes a valid minimal suppl archive (an early release that Steffen sent me) and some small changes that are not yet in cvs. Somewhat off this topic, but anyone want to direct me to the specification / description / or at least basic layout of descript.ion files. Thanks. Jeremy --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedos
(please disregard my last note asking what the discussion is about, as this message finally found its way to my inbox :-) Geraldo Netto wrote: hi folks, ... where is bart, lucho, john elliot, jason hood, imre leber, daniel nagy, steve nickolas, steffen kaiser, joe cosentino and even where is Pat Villani? ... I can't really say, I know some prior developers have moved on to other projects (or back to their primary focus), others perhaps busy with life, and some only seem to pop up occasionally. support pcmcia driver - why develop an pcmcia driver for dos? ... this would be nice, though I'd rather see usb support; I think PC-DOS had some card wizard or such support bundled (been a while so I may be confusing this with other software from work) either way, a project for someone else luchojack (udma driver rules) --- what happened?(if you allow me to know, of course) ... I believe your answer lies in the mailing lists archives, but I hope they continue to check in occasionally internationalization/docs - ... I would like our docs to be the best possible, but it really does take work and time (which is a scarce resource) to prepare the docs irc people ... I'm just not the irc type, I prefer email (allowing me to reply in my own time if and when I get time), but good to know some FreeDOS regulars are available there kernel development -- what about stop development for a time and revise code before release FreeDOS 1.0? I would like to do more development with the kernel, but alas I have very little free time. For the 1.0 release, the stable kernel is in good shape, but some more merging from the development kernel needs to be done. I have a few things on my todo list for the kernel, though most aren't urgent and may not be complete for FD1.0 (which is no big deal). I think that we are near and far at the same time of FD1. ... still plenty of fun work ahead and yet usable as is :-) distribution ... with some interesting softwares so this is my list: ... I'll have to look into some of them (most I'm aware of, but some are new or at least new urls to me) on one hand it would be nice to include a lot of useful software, but on the other many people just want a simple boot environment (and tiny download); if we had the manpower, an ideal situation would be multiple distributions maintained (boot disks, minimal, medium - like what we have now, and fat - with a whole set of useful programs). I think Bernd (and Jim in the past) is doing a great job with the distribution (its more work than one would think). misc i think that freedos need a plan, please note that i'm not saying that freedos is not structured, i'm just saying that it is important to plan something(please, don't not define time to make things it will just disturb the development) I wouldn't say FreeDOS is structured, but as far as plan goes, I think the 1.0 todo list and post 1.0 list along with the manifesto are sorta the plan. Other than that, I think each developer has his (?are there any hers here?) own ideas for future development [at least I have plans, probably more than I will ever have time to implement...] is possible to implement a virtualfilesystem layer on freedos kernel? ... I think Tom answered these pretty well on fd-kernel. it is interesting to make freedos portable to others architectures To be honest, I would rather see the kernel less portable, targeting just OpenWatcom, but that's something I won't ever do. To a certain extent the kernel code is still portable (from its roots), but making it compatible is a higher priority for most users. i like arkady's optimization but i think that first we need to revise the kernel code before sending to arkady, ok for you, arkady? what sort of revisions would you like to see? michael does a nice job with emm386/himem and martin stromberg did a nice job too a long time ago... now, what about both working on emm386/himem? I'm not touching this issue with a ten foot pole ... again, Thanks for this incredible piece of software! and keep this good work :) Regards, Geraldo Thanks, Jeremy --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: Re: [Freedos-user] HTML address for new Help file.
Bernd Blaauw wrote: Basil Holloway schreef: Got this reply on forum and have not be able to locate the new Free Dos 9 help file ... Can anyone please advise download web address. I have the fixed program, but will not redistribute it until next FreeDOS distro, as I need to provide proper credits to the patcher. If anyone feels like creating a diff file, go ahead. ... I will put together the necessary changes and upload to ibiblio along with a compiled version by tommorow (as I already said I would). For reference, help mirror on ibiblio is at http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/help/ Jeremy --- This SF.net email is sponsored by Microsoft Mobile Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) Windows Mobile(tm) platforms, applications content. Register by 3/29 save $300 http://ads.osdn.com/?ad_id=6883alloc_id=15149op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
WordPerfect file format Was Re: [Freedos-user] Re: Question
Wesley Parish wrote: ... In relation to that, does anyone know where I can find the specifications of the native WordPerfect file format? And suchlike? I know O'Reilly's had something of the sort, and there might have been something similar published somewhere else - but I don't know where to get copies. Thanks Wesley Parish Corel publishes a WordPefect SDK, it might have the spec or at minimal will help in understanding the file format. You should look at libwpd, it is a library (unfortunately uses GSF which is GLIB based) for reading Word Perfect files. (It is used for AbiWord, and OpenOffice as well.) It mostly supports WordPerfect 6 through 11, though it does have some support for WP 4 5. See http:/libwpd.sourceforge.net for more/better information, their link page includes the url for the Corel SDK. Jeremy --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] XMS Manager on '286
... Anyway... I'm surprised that it is so uncommon to run FD on an old PC. IMHO it seems ridiculous to install FreeDOS on your P4 side-by-side with Windows XP like so many other people do. I mean what DOS software is going to run properly on a 3Ghz CPU? Besides, what else are you going to do with your old PC's? They would bog down to a crawl even on early versions of Linux or FreeBSD, but FreeDOS is perfect. the problem is that older equipment is harder to come by if you don't already have it and it does eventually stop working (I still miss my ps/1 286 with its huge 2.5MB of RAM :-) so for me a 486 is about the oldest computer I test on that still has a fully working hard drive. This may be off the original topic, but I have to comment that the FreeDOS CD installer is HORRIBLE. It's so bug-ridden that it only works on newer systems, I've run it on eight different PC's and only Pentium II's and above don't crash the installer. Older PC's don't even get past the CWSDPMI mode switch without causing an exception trap. I am making my own batch file installer for floppy systems right now that doesn't require a CD-ROM or a 386, but I am hoping that someone will replace that installer in the future... I assume you are referring to the GUI based installer, have you tried the text based one? (select monochrome mode to use it). I'm not the best person to comment here as I presently have FreeDOS installed as the only OS on my amd64 computer. Thank you for the information, I was not aware it was such a problem, as in the past I tested on my 486, but lately have been using my newest one. (The GUI installer was both a requested feature in the past and contributed program, but perhaps we should reconsider its use?) Jeremy --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Edlin 2.4 italian binary
... then it can end up in a binary compiled from CVS: http://fdos.org/AutoIndex/index?dir=kernel/file=cmdxms.HEAD.NLS.zip Does this includes ITALIAN.ERR also? Ciao Yes, although it may not be clear from the log (because the main binary is the english build), I actually completely rebuild for each language, though only the two criters (which I believe use the .err strings) and strings.dat are included (as %lang%.dat) for the other languages in the archive. If there is demand, I can adjust my build to upload additional archives (one for each language) instead of the current setup which includes all languages [split into main binary + strings to reduce size]. Jeremy --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Creating custom bootable DOS CD's under Windows XP
[EMAIL PROTECTED] wrote: Good day, all: I have come up with a procedure to create a bootable custom DOS CD, with a 2.88MByte boot sector, strictly under Windows XP. A ... I could use some help in describing how to tailor this to FreeDOS and how to set up the CD drivers to use the rest of the CD. If you are interested, drop me a line and I'll send you the MS-DOS draft. Mark You may also wish to check out http://www.fdos.org/bootdisks/#bootCD which is my framework to create custom DOS bootable CDs. If you use VFD, version 2 is really cool, as it added support for 360KB and other sizes, and Daemon Tools is excellent freeware to test/extract files from ISO images. Please send a URL to obtain your complete instructions or send them to me privately and I can post them on my site (when ready). Alternatively, if its not too large, you may want to add the information to the Faq. :-) Jeremy --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Re: problem with Pictview under FreeDOS
Pictview 1.94 should work now with the latest development kernel (the 1.95 preview version works correctly under both branches already). Based sorta on Eric's patch email, basically the kernel is now a lot more picky about what it considers a search for VOLUME LABEL. If this breaks a program anyone is aware of, please send to me [name of program and where I can get it if possible] privately or on fd-kernel list so I can add to my list of programs to check. Thanks. I still need to do some comparisons about how other DOS versions treat the search attribute, specifically what they do when the vol bit is set, and how they treat the 2 reserved high bits (which are used by some versions of DOS). Jeremy --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Borland C++ 5.5 compiler freeware?
Eric Auer wrote: .. tells me that the compiler of BC++ 5.5 is available as a free download. What does that mean? Many people seem to use the non-free BC++ 3.x, so is this really the BC 5.5 one (without the IDE), or is it just Turbo C or Turbo C++ 5.5? Does it include TASM? Does it compile some typical DOS programs for which Turbo C 2.01 - THE classic - is not good enough? ... It is for Win32 only, both in what it generates and what it runs on. Also availabe is turbo debugger (again for Win32, though its interface is almost the same as the DOS version). With both installed you get (all command line only) compiler (bcc32), resource compiler (brcc32), grep, incremental linker (ilink32, instead of turbo linker tlink), impdef (for generating dll import libraries), make, turbo debugger (td32), tdump (for displaying some info about object/exe files), librarian (tlib), touch, and trigraph. It also includes a c library, platform sdk, help, and examples. No assembler and no IDE. So its kinda like Turbo C for Windows, but uses the Borland compiler names. It does a good job compiling simpler DOS programs under Windows (where more complex ones would require rewriting to use the Win32 API instead of direct access, video, direct DOS calls, etc). I lost a lot of respect for for Borland when they released the 5.0 version (it was very buggy when initially released). Jeremy --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS in the news
Steve Nickolas - Using Windoze wrote: [EMAIL PROTECTED] wrote: Sory for this extremely late answer, but what i meant was: when did the FreeDOS spec get changed? Imre Such a change would be news to me. To my knowledge the standard is still Borland C++ 3.10 and TASM, or Turbo C++ 1.01 and Arrowsoft ASM for a lower denominator that's freely downloadable at least. -uso. I don't recall if the change was ever formalized, but there is a general shift away from Borland and T/Masm to OpenWatcom and Nasm. I know there was a discussion on the lists about making a change in the spec, but would have to look over the archives... That stated, in the end it is the person doing the work that gets to decide what tools are used, though using ones that are not [easily] available to others then you are less likely to get any help (occasionally it does occur :-) and if/when you no longer feel like maintaining it, then it will be more difficult for future work [though once a tool reaches a certain point, there may be little need of further modification]. The kernel for example is now primarily using OW and Nasm (though Borland still works, Masm syntax is no longer used for the asm portions), but FreeCom is still built using Borland's tools, and a good chunk of the utilities haven't been compiled in a long while so remain with same dependencies. I believe the shift has to do with several advantages OW has over Borland tools: - it has a largely compatible (depending on how dependent a program is on Borland's details of course) - it can be freely distributed (so in theory we could provide self hosting distributions) with source [subject to the terms of its license of course], whereas Borland is free, but lacks source and should be retrieved from Borland [or like myself use copies that were bought a while back for releases] -OW is still under development, Borland's is not, in fact their help support does not even know that their DOS compiler exists (at least last time I called). -OW does a good job optimizing code and supports 386 whereas I do not believe the Borland downloads support 386; plus once you get used to it, OW's #pragma functions/inline asm are really cool Personally I think Tasm is better than Nasm, but Nasm is freely available (Tasm is not available for download legally, and Masm dl ver 6/7/8 is for Win32 or Masm 5 dl is limited to OS/2 developement) with source and still being developed. The above is just what I recall so take with a huge grain of salt. Jeremy --- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588alloc_id=12065op=click ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Shsucdx ATAPICDD.SYS
Bernd Blaauw wrote: ... You need to specify DEVICE NAME. ATAPICDD.SYS assumes some strange name, but definately not FDCD000x batchfile (cd will be drive X:): @echo off devload atapicdd.sys /D:FDCD0001 shsucdx /D:FDCD0001,X depending on which version will determine what the default name is (and other options for that matter), but think all public alphas support the /D:name option. various names have been ATAPICDD and FDCD The next release will be using the same name as shsucdx as the default so a simple load without options and running shsucdx without options will work. [The release is held up as I'm working on the kernel and a tool for my own use to simplify boot disk creation and so I can play with FATs/LFNs without screwing up the kernel.] Jeremy --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047alloc_id=10808op=click ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] announce: pdTree v1.02
Not overly big news, but I've updated tree. From a DOS perspective, the only noticeable change is the addition of an initial /P to pause implementation. And the addition of a Latvian translation from Kristaps Kaupe. It includes a minor fix that allows it to continue processing subdirectories on certain errors. The win32 version now supports the /S (short filenames only) option (in DOS version it also disables the use of the LFN api). The win32 version properly detects console window size and will disable (ignore) the /P option when output is redirected, but the DOS version assumes 80x25 screen and will still prompt (but to stderr so you can see it) if /P and redirection are used. URLs: home: http://www.darklogic.org/fdos/projects/tree/#pdTree lsm: http://www.darklogic.org/fdos/projects/tree/pdTree/pdtree.lsm source: http://www.darklogic.org/fdos/projects/tree/pdTreev102.zip (also available on ibiblio) (pdTree is the recommended version of tree to use for those who ever use a Win32 system, aren't overly concerned about file size, or have a Pentium or higher class computer. Those on 8086 systems should stay with tree 3.7x, but can use any of the cats message files tree.%lang% from newer releases of pdTree. Presently this is just english, spanish, and now latvian.) Please let me know if you find any bugs. Still to do is query screen size for DOS and add support for sorted output. Thanks, Jeremy [EMAIL PROTECTED] --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
