Re: [Freedos-user] FreeDOS on Virtual PC 2007
Hi Mike: I use "VFD" to do this under Windows. (It's easy under Linux). See http://chitchat.at.infoseek.co.jp/vmware/vfd.html. You can mount the image as a floppy drive and copy files to/from it, format it, etc.. The other programs I know about cost money... Good luck. Mark Bailey - Original Message - From: "Michael Horvath" To: freedos-user@lists.sourceforge.net Sent: Saturday, March 21, 2009 12:31:51 AM GMT -05:00 US/Canada Eastern Subject: Re: [Freedos-user] FreeDOS on Virtual PC 2007 [...] If so, can anyone recommend software to create floppy images without needing an actual floppy drive? Thanks! -Mike -- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS USB installation
Will the EEEpc boot from a USB flash drive? If so, install FreeDOS on the USB flash from another computer, boot it on the EEEpc, and install FreeDOS "normally" on the EEEpc. Many (probably most) computers with modern BIOSs will recognize a USB flash drive if it is installed at boot time. This allows installation of FreeDOS normally on the drive and booting it when you are done. I have installed FreeDOS on USB flash drives. With a modern BIOS and a floppy drive, that's trivial. Slightly harder booting from CD since you have to create the CD. Mark - Original Message - From: "Braden C. Roberson-Mailloux" To: freedos-user@lists.sourceforge.net Sent: Sunday, January 25, 2009 12:13:59 AM GMT -05:00 US/Canada Eastern Subject: [Freedos-user] FreeDOS USB installation Hello; I've been scouring the internet to find someone who has installed FreeDOS from a USB flash drive. I've found no one, thus far :(. Why would anyone, like me, want to do this? I have an EEEpc :) and want to run FreeDOS on this nifty little piece of machinery and start banging some bits! Does anyone have some advice or sugghestions? Thanks; Braden. -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Poll and ideas compressed filesystem
-- Original message -- From: Michael Reichenbach > Michael Robinson schrieb: [...] > > The advantage of supporting NTFS is that freedos could be > > used as a tool potentially to work on and repair a modern > > NT based Windows system. > > Yes. > There is another real advantage to supporting NTFS file systems. Those of us running legacy DOS applications would really like to be able to read and write files from NTFS filesystems. Imagine booting FreeDOS from a CD and being able to run applications from and save files to a WindowsXP NTFS file system! :-) The legacy applications I am running need direct access to twiddle bits on parallel ports with rather exact timing, for instance, so running in a virtual machine isn't a good option. What I do now is dual-boot, which is trivial once you introduce a FAT partition for DOS to do file accesses - which I currently have to have anyway. I have not been able to get NTFS4DOS to work reliably. Mark Bailey -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dual boot part 5.
-- Original message -- From: "kurt godel" <[EMAIL PROTECTED]> > Eric, > actually, I tried to put the 98 on top of the FreeDos *both ways*, once from > FreeDos, and another time with a > bona fide 98 floppy boot image, which I had put on a cd (iso image, etc.). > The latest thing I tried was to first > load the fdos to 'c', reboot, then reboot again off the 98 cd boot cd. Then > I xcopied the works to the 'd' > logical drive, reformated the 'c' drive, installed 98 to that, then from 98 > copied the works(fdos) back onto 'c'. > Of course, the same result: could not load the cd driver, since the drive > letters get bumped making the par- > titions. I'm going to try again with 98, then fdos, and going to windows > with sys c command. TNX, kurt. > <[EMAIL PROTECTED]>. Hi Kurt: I've been following this thread with some interest. I think it's simpler to just install FreeDOS in its own partition. You can use a boot manager to select which OS to boot at startup. My favorite, because it is very easy to install and configure, is GAG (gag.sourceforge.net). Eric disagrees of course. :-) You could create three primary partitions and install FreeDOS, MSDOS, and Windows98. Let me know if you have any questions. For partition fiddling, I usually use a Linux LiveCD and a program called gparted (see www.sysresccd.org if you are interested). Good luck. 73, Mark, KD4D - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] virtual OS/bootdisk?
Hi David: It is straightforward to create a bootable FreeDOS CD. I think the easiest way to do it is to take a floppy disk image and boot that from the CD. This restricts the boot image to 1.44MBytes (or 2.88MBytes if you get tricky). However, you can add a CD-ROM driver and then add a lot of files. Some years ago, I spent a while learning how to dual-boot FreeDOS and Windows. As part of that work, I developed a lot of bootable CD's for MSDOS and FreeDOS. I did this from Windows computers, some which lack floppy drives. For a detailed description of how I did this, including the free tools I used, see: http://k1ea.com/hints/Creating_a_Bootable_DOS_CD_V%201.5.pdf This is one way to do it - I think about the easiest if you are creating the CD's from a Windows computer. Let me know if I can answer any questions. Mark -- Original message -- From: david lowe <[EMAIL PROTECTED]> > > I am wondering if it's possible (and allowed) to burn the FreeDOS OS on a cd, > instead of preparing to install it to my hard drive. I want to use it to use > it > primarily as a bootdisk and to scan and repair for errors. I don't plan on > installing just yet, because I > need to do a major overhaul on my system. I've found trojans in my _Restore > database, and I can't view more than three windows in IE before it crashes. > WinME has poor support online. > - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Install Win95 from freedos
-- Original message -- From: "Robert Riebisch" <[EMAIL PROTECTED]> > Michael Reichenbach wrote: > > > He said he has no floppy anymore. So this is a bit more complicated. > > Where exactly? I only see "without owning DOS on floppies", which is > something completely different. > > Nevertheless he could buy (or borrow) a USB floppy drive. I prefer NEC here. > > Robert Riebisch > -- If the lack of a floppy disk is the only issue, it is easy to create a bootable CD from a floppy disk image. Most BIOS's will boot a CD. Doing this doesn't require a CD ROM driver. Mark - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Boot FreeDOS from secondary HDD
Hi: Most boot loaders will allow you to do this. I like GAG because it is GPL and easy to set up. See http://gag.sourceforge.net for more information. I always have to read the manual to use grub, but it is also capable of doing this. There are many others. Mark Original Message Subject: [Freedos-user] Boot FreeDOS from secondary HDDDate: Thu May 15 16:44:15 EDT 2008From: MegaBrutal To: freedos-user@lists.sourceforge.net;Hi all, I've installed FreeDOS a half year ago. I chose the option to update boot.ini for Windows XP, so the FreeDOS boot sector is stored in "freedos.bss", and I could chose FreeDOS from Windows XP's boot menu. Since that, things have changed. I've got a new hard drive, and made it to be the primary HDD (IDE master), and my old HDD is now the secondary one (IDE slave). Of course, drive letters have changed. My old C: drive became J: - then I thought it's ok to add this line to my actual boot.ini: J:\FREEDOS.BSS="FreeDOS" But it doesn't work, FreeDOS won't boot. Well, it would be nice if I could keep my FreeDOS on the old HDD, and I wouldn't need to reinstall it to my new one. So I'd like to use my old FreeDOS installation. Any ideas? Thanks, MegaBrutal - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Docs for installing Freedos onto a USB drive
-- Original message -- From: Eric Auer <[EMAIL PROTECTED]> > > Hi Carlos, > > > only one question, where is the equivalent to > > "dd of=/dev/sda bs=1M" in MS-DOS/FreeDOS or Windows > > environment? > > You probably mean "dd if=dosdisk.bin of=/dev/fd0"? > You can use FreeDOS DISKCOPY for "diskcopy dosdisk.bin a:" > which should even work when you use it in common versions > of Windows... :-). If you meant something else, let me know. > > Eric > How about DD for Windows? dd if=\\.\a: of=image1.img bs=1k count=1440 See http://uranus.it.swin.edu.au/~jn/linux/rawwrite/dd.htm Mark - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] usb stick
There MIGHT be an even easier way. With some newer BIOS's, you can boot FreeDOS (from CD or a floppy) with the stick plugged in and the stick will be mapped to C: or D: by the BIOS. If that happens, you can use FreeDOS to write the boot sector (SYS C: or SYS D:) and install it directly from FreeDOS. This seems to work on newer computers more often than not. It's a lot easier than dealing with the HP Tool. Mark -- Original message -- From: "Florian Xaver" <[EMAIL PROTECTED]> > 2008/1/17, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > > > How did you install the boot sector? > > Did you just write a freedos 1.44MB image to it? > > I have a 256MB pen drive that I would like to make bootable if I can use > > the whole drive. > > No - there are two ways - one for linux (Eric wrote a script) and one > program for Windows from HP: HP USB Disk Storage Format Tool > > I used this program for writing the bootsector and formating of the > usb-stick (FAT32). > It works like a big floppy (I have 256MB-USB-Stick) now. After that I > installed many useful tools and programs... > > Bye > Flo > > PS: In the FreeDOS-Wiki is un article about this topic. > > -- > Club Dr-DOS Wiki http//www.drdos.org > private page http://www.flox.at.tf > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] OS selectors
I use GAG for doing this. It's easier to configure than GRUB and will boot DOS or Windows from any hard disk and partition. I find it easier to keep each operating system totally separate and not to modify the Windows boot.ini files. GAG is under the GPL and can be downloaded as a floppy disk image or bootable CD image from gag.sourceforge.net. I don't know if GAG will work for your particular application, but it is a very flexible boot manager. Mark -- Original message -- From: Vytautas Rakeviius <[EMAIL PROTECTED]> > GRUB works fine for Linux, FreeDOS and windows from my > experence I can say this. And maybe for others too. > Add this in menu.lst: > > title FreeDOS > root (hdx,y) > savedefault > makeactive > chainloader +1 > > And x is hdd number is only one hdd then 0 > y is partition number first is 0. > > - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How can make a bootCD
Hi Juan: One way to get a bootable CD is to use a combination of isolinux and memdisk to boot a floppy disk image. I BELIEVE that this is the method most compatible with different computer BIOS's. What I do is boot the floppy disk image (1.44 MBytes typically) and, if I need more storage, configure a CDROM driver to access other files on the floppy disk. I wrote some notes on how I create bootable DOS CD's from Windows XP. This can be done without a floppy drive using free tools. If you are interested, see http://k1ea.com/hints/Creating_a_Bootable_DOS_CD_V%201.5.pdf I know of several people who have successfully created FreeDOS and MSDOS bootable CD's using this writeup. If you have any questions, let me know. Mark -- Original message -- From: "Juan Matias Granda" <[EMAIL PROTECTED]> > (first sorry for my english :) ) > > hi! me again, i want to create a bootCD with a custom installation of > FreeDOS, because i want use this in a couple PC with cdrom but without > Hard Disk. > i need: > * install FreeDOS (done) > * install Lanman from M$ (done) > * configure the network (done) > * create some shared folder (done) > * put everything to BootCD (FAILED :P) > > Grettings > insulae > > -- > Juan Matias Granda > http://www.insulae.com.ar > GPG FINGERPRINT:459C 4A2D 330C CB8C 0C44 0C3A 572C CBCA 5457 508B > > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] collision between emm386 and memdisk
-- Original message -- From: "m4mach" <[EMAIL PROTECTED]> > hi > [...] > > I use CD-ROM drivers, but don't know how to add programs from CD directory > to PATH variable. (to search for CD label?) > [...] You can specify the drive letter that will be used for your CDROM drive in autoexec.bat. Using shsucdx, you can just assign the starting drive letter as "X" and then use X:\FDOS or whatever in your path statements. See http://help.fdos.org/en/hhstndrd/shsucdx.htm for the "drive" parameter: drive The first CD drive will be assigned to this drive letter, then subsequent drive letters will be used for any other CD drives that are detected. Mark - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Installed on top of WinMe: system unusable.
Florian Xaver escreveu: > > Why does most people like GRUB? I don't like it. :-) I think, there are > > many better boot-managers. >I can answer for myself: I don't like it, I just have in in my machine ;-) > >Let me explain: I use Mandrive Linux which just give me 2 choices: Lilo >or Grub. Unless I were willing to spend a lot of time learning to >install something else and never use the crash recover capabilities, I >am stuck with it. > >I just could not find in LILO how to change active partition at boot >time (for Fdos/win98 boot) and swap partitions (needed for WinXP). > >So I am stuck with GRUB, which BTW works just fine and the later version >has a better look :) > >Alain Hi Alain: The Linux installers I've used have an option to install their boot manager (either Lilo or Grub typically) in the "/" partition instead of the MBR. If you install them that way, you can use any boot manager in the MBR and that boot loader starts GRUB or LILO. This is what I do on my machines that boot Linux. I use GAG installed in the MBR as the boot manager and GRUB is started from the "/" partition. I find configuring GRUB just too much trouble! GAG is open source (GPL) and available from gag.sourceforge.net. Mark - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Installed on top of WinMe: system unusable.
I like the open source program GAG for this. It doesn't require a partition and I find it MUCH easier to set up and configure than GRUB. It isn't quite as pretty, but you only see it for a few seconds. gag.sourceforge.net Mark -- Original message -- From: "Jim Hall" <[EMAIL PROTECTED]> > You can do this with any sufficiently-capable boot manager. I used to > use V Communications' "System Commander", once upon a time. Don't > know if it's still available. Used to be fairly cheap: about $40 > (US). There are probably lots of other commercial utilities you can > find at a Best Buy or similar place, if he wants something that comes > as shrink-wrapped software. > > The open source ($0) XOSL does this too, I think. As you mentioned, > so does GRUB. > > -jh > > On 6/8/07, Alain M. <[EMAIL PROTECTED]> wrote: > > > > >> Install Freedos on the second primary > > >> partition. > > > > > > Yep, that's what I should have done. The HOWTO sure gave the > > > imporession that it would automagically share a parition. I'll > > > probably jsut shrink the FreeDOS FAT partition and dual-boot > > > Linux. > > > > It's easy on Linux, specially with grub. > > > > The trick is: have two primary partitions, one of them active, none > > hidden. There is a command in GRUB to change tha active partition "on > > the fly" prior to boot. > > > > The advantage is that nothing needs to be special, each run in C: and > > the other is still available (at the last letter) > > > > Alain > > > > - > > This SF.net email is sponsored by DB2 Express > > Download DB2 Express C - the FREE version of DB2 express and take > > control of your XML. No limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > ___ > > Freedos-user mailing list > > Freedos-user@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/freedos-user > > > > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] bootable USB stick
Hi again, Jim: If your computer has the right BIOS support, there is a MS-DOS centric "cookbook" for doing this at: http://www.pvrc.org/Newsletters/feb05.pdf If I were writing this again, I'd have you boot dos and do the "SYS C:" or whatever FIRST to make sure that the BIOS support works before copying the files. Mark -- Original message -- From: Jim Lemon <[EMAIL PROTECTED]> > Hi folks, > > After using FreeDOS for some years to run a battery of human performance > tests, I am running out of tricks keeping up with PC design. In order to > run the tests on PCs without a VFAT partition, I now boot off a CD-ROM > and write data to a diskette. Unfortunately, hardly any PCs these days > are shipped with diskette drives... > > My aim now is to create bootable USB sticks, running the whole show from > the stick. The whole installation is not much over 10Mb, so there's > plenty of room. I read Russell's tech note that indicates that USB > keyboards and mice will work (they already do with my present setup, I > use the 33h interrupt for the mice). However, I couldn't seem to find a > comprehensible method for creating bootable USB sticks. Is there a cook > book out there somewhere for doing this? > > Jim > > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] bootable USB stick
Jim: AFAIK, there are at least three different ways to install FreeDOS on a USB stick. Unfortunately, the BIOSs and USB sticks differ somewhat and I haven't found a way that works all the time. The easiest way, if you have the "proper" BIOS support, is to plug in the USB stick, turn on the computer, and boot FreeDOS from a CD. On SOME computers, the USB stick will show up (usually as C:). In this particular case, you can install FreeDOS normally, just like installing on a hard drive. There is an HP Utility which runs under Windows which I have found works MOST of the time: http://h18000.www1.hp.com/support/files/serveroptions/us/locate/69_6073.html This will reformat the USB stick, destroying all data on it. The third way is to boot DOS using memdisk and syslinux. The problem with this is it is just like booting from CD and the USB stick isn't accessible (unless you have the right BIOS support) after boot. You can also use a USB floppy disk drive. I've had good luck with those on most computers. Let me know if you have any questions. Mark Bailey -- Original message -- From: Jim Lemon <[EMAIL PROTECTED]> > Hi folks, > > After using FreeDOS for some years to run a battery of human performance > tests, I am running out of tricks keeping up with PC design. In order to > run the tests on PCs without a VFAT partition, I now boot off a CD-ROM > and write data to a diskette. Unfortunately, hardly any PCs these days > are shipped with diskette drives... > > My aim now is to create bootable USB sticks, running the whole show from > the stick. The whole installation is not much over 10Mb, so there's > plenty of room. I read Russell's tech note that indicates that USB > keyboards and mice will work (they already do with my present setup, I > use the 33h interrupt for the mice). However, I couldn't seem to find a > comprehensible method for creating bootable USB sticks. Is there a cook > book out there somewhere for doing this? > > Jim > > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Partitions freedos can boot from
The default MBR on a hard drive boots THE primary partition marked active. A boot loader like GRUB, LILO, GAG, or whatever can boot any partition. IIRC, however, the FreeDOS kernel won't start correctly from a logical partition. FWIW, the Linux kernel is perfectly happy booting from a logical partition. And, the Linux swap partition can be in a logical partition also. That suggests an easy fix for your system...create an extended partition as /dev/hda4, put a swap partition in it, and put FreeDOS in /dev/hda1. (These are the linux designations for the hard disk partitions.) The best tool I know of for manipulating and resizing partitions is GParted. There is a GREAT LiveCD including GParted available at gparted.sourceforge.net. The System Rescue CD also includes GParted: .sysresccd.org Mark Bailey -- Original message -- From: roger <[EMAIL PROTECTED]> > On Mon, 2007-04-23 at 23:43 -0400, Bonnie Dalzell wrote: > > So i have still not determined wether freedos can boot from a > > logical partition using grub. > > (All Primary Partitions) > /dev/hda1 LinuxSwap 364MB > /dev/hda2 Linux ReiserFS 30GB > /dev/hda3 FreeDOS Fat32 1GB > > /etc/grub.conf > --- Begin of Snip --- > title=FreeDOS > map (hd0,0) (hd0,2) > map (hd0,2) (hd0,0) > rootnoverify (hd0,2) > makeactive > chainloader /fdosboot.img > boot > --- End of Snip --- > > > I thought only primary partitions were bootable. And even then, some > bioses have a size limitation of what is considered a bootable > partition. (ie. 1024 Cylinder Limit) > > -- > Roger > http://www.eskimo.com/~roger/index.html > Key fingerprint = 8977 A252 2623 F567 70CD 1261 640F C963 1005 1D61 > > Mon Apr 23 22:28:38 PDT 2007 - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Installing without CDROM (was: I Have a Question)
Hi Leslie: The easiest way i know of to create a FAT (might as well make it FAT32) partition is to use the LiveCD from the GParted project: gparted.sourceforge.net This can also be run from a USB stick if your computer can boot from a USB stick. You can shrink an NTFS partition and create a new FAT partition. You have to be careful with partition ordering and the size of the restore and primary partitions on some systems. I wrote up a howto on installing FreeDOS on a WindowsXP system which is available at www.k1ea.com/hints. See Dual-boot "Real" DOS on Windows XP (0.95 beta) by Mark Bailey, KD4D At this point, i would recommend doing the partitioning with the new GParted LiveCD from gparted.sourceforge.net instead of using the older version referenced in that document. Let me know if you have any questions. Mark Bailey -- Original message -- From: Leslie Shrum <[EMAIL PROTECTED]> > Okay. That helps a lot. It is an 80 gig drive with about 40 gigs of free > space, so I have plenty of space to play with. I am assuming that I need to > also install whatever games that I was going to run in freedos on the same > partition; just for simplicity's sake. If you could get me the information > on > that how to, I would be really grateful. You have been so helpful so far. I > am > less worried now that I know that it is safe to make a FAT partition. Thank > you > so much! > Leslie > > --- Begin Message --- Okay. That helps a lot. It is an 80 gig drive with about 40 gigs of free space, so I have plenty of space to play with. I am assuming that I need to also install whatever games that I was going to run in freedos on the same partition; just for simplicity's sake. If you could get me the information on that how to, I would be really grateful. You have been so helpful so far. I am less worried now that I know that it is safe to make a FAT partition. Thank you so much! Leslie Eric Auer <[EMAIL PROTECTED]> wrote: Hi Leslie, > Okay... since I only have NTSF Drives I will use the limited floppy > method. Unless it is possible to create a FAT Partition without wipping > the whole drive. I have one hard drive which already has 2 partitions: > both are NTFS. One is labeled OS and the other is Labeled Recovery. If you have no FAT partitions, then the floppy method will not help you to install DOS anywhere on harddisk either. So you will first have to create a FAT partition to be able to install on harddisk. You can do that without data loss by using for example the partition resizer of the installer of a Linux distro of your choice. Those can make existing NTFS partitions smaller without deleting files. Your PC will be busy with this for a while. I think there was also some HowTo for "installing DOS on a NTFS- only computer" which explains the partition resizing process in more detail. Somebody on the list might know the URL of the howto. Once you made a NTFS partition smaller, you will be able to create a FAT partition and format it. I would suggest to use Linux for that as well - using DOS is not user friendly, and is more risky. If your FAT partition is no primary partition, you will have to use a boot menu like the Windows or Linux one to be able to select DOS at boot time. You may even have problems with SYS in general. Then you would either need a boot diskette to boot the DOS on your harddisk, or you would need nontrivial manual adjustments to make DOS bootable from harddisk. So the best choice would be to have a primary FAT partition to install DOS on, preferrably FAT16 as it is easier to boot from FAT16 than from FAT32. Do not make the partition too small, a few 100 MB will not hurt on a 200 GB disk. Eric - 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.php&p=sourceforge&CID=DEVDEV ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user Hope is only as strong as the Faith that Sustains it. Faith is only as strong as the Love we give We can only truly Love when we love OURSELVES http://www.myspace.com/leslieslittlecorner - No need to miss a message. Get email on-the-go with Yahoo! Mail for Mobile. Get started.- 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 o
Re: [Freedos-user] Partitioning Software
-- Original message -- From: "Lester Vedrox" <[EMAIL PROTECTED]> > > Mark> I have found Partition Magic unreliable on WindowsXP Service Pack 2 > > (and > later) versions of NTFS. > > > JL, Mark> I would recommend trying: > > http://gparted.sourceforge.net > > > JL> Easy to use, the GUI really help understanding how the partition > > layout. > Too bad it's too small for CD and too big for floppy, and needs to boot Linux. > There is a gparted liveCD at gparted.sourceforge.net that just boots on any computer that can boot from CD. The fact that it is running Linux isn't a problem...it doesn't install Linux on the hard drive and GParted is a GUI program very similar to Partition Magic. It is about 40 Mebabytes and fits on a CD just fine. Linux runs from the CD and memory. GParted is already installed with the bootable CD. Mark > If for some reason Gnome (link above) is not sufficient then Partition > Commander > (U$50) works just fine with WinXP SP2 NTFS. It's GUI looks ok, too. It can > also > be easily setup on a standalone bootable CD. > > > > PartitionMagic: > > > > > http://www.partitionmagic.com/home_homeoffice/products/system_performance/pm80/i > ndex.html > > > > Partition Commander: > > > > http://www.v-com.com/product/Partition_Commander_Home.html > > > > Acronis Disk Director Suite: > > > > http://www.acronis.com/homecomputing/products/diskdirector/ > > > > Partition Commander, for instance, allows converting NTFS partitions back > > to > FAT, the feature that was absent in PartitionMagic. Acronis Disk Director > Suite > seems to have the best choice of features of all three products, but I have > never tried it so can't comment on it. > > > > Lester > > > -- > ___ > Surf the Web in a faster, safer and easier way: > Download Opera 8 at http://www.opera.com > > Powered by Outblaze > > > ___ > 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] why make partitions hidden?
Lester Vedrox wrote: >> AB> Repartition disk (by FDISK or somethink like Partition Magic). >> >> EA> Use a GOOD partition editor (not MS FDISK... preferrably something with >> a reasonable user interface and something which you are good at using. > > James, you should probably consider investing in partitioning software: > > PartitionMagic: > > http://www.partitionmagic.com/home_homeoffice/products/system_performance/pm80/index.html > > Partition Commander: > > http://www.v-com.com/product/Partition_Commander_Home.html > > Acronis Disk Director Suite: > > http://www.acronis.com/homecomputing/products/diskdirector/ > > PartitionMagic used to be a leader in this field but it's dominance has been > challenged lately by competitors. Partition Commander, for instance, allows > converting NTFS partitions back to FAT, the feature that was absent in > PartitionMagic. Acronis Disk Director Suite seems to have the best choice of > features of all three products, but I have never tried it so can't comment on > it. > > Lester > > I have found Partition Magic unrealiable on WindowsXP Service Pack 2 (and later) versions of NTFS. There is an open-source, bootable CD which works well and includes the Linux version of fdisk: http://gparted.sourceforge.net I would recommend trying that. The price is right! :-) Mark ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Linux Tools and FreeDOS Dual Boot LiveCD
Hello, all: I have succeeded in creating a bootable CD containing Linux and FreeDOS. It turned out to be easy. This CD containts the two tools you need to dual-boot a Windows XP computer (gparted and fdisk) and the FreeDOS odin1440 boot floppy image (from odin.fdos.org - the 2005 version). Everything on it is GPL (I believe). It is based on the GParted 0.2 LiveCD and FreeDOS ODIN. You do not need to know anything about Linux to do this. 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. Is there somewhere we could post more recent versions of this? I don't have a web server available. The size should remain at under 35MB I believe. Let me know if you are willing to be a beta tester! Mark Bailey --- 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=lnk&kid=103432&bid=230486&dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] re: Dual Boot WindowsXP and FreeDOS - Alpha testers needed
-- Original message -- From: Johnson Lam <[EMAIL PROTECTED]> > On Fri, 3 Feb 2006 12:24:28 +0100 (MET), you wrote: > > For example, we may need to GHOST the whole > hard disk before we start, I believe that's rather small, after > compression it should be less than 800MB, a US60 can buy a FLASH DISK > or a COMPACT FLASH to store it, and boot the driver directly from > flash or floppy if the BIOS not new enough. > This hard disk has something like 30 GBytes of data and WindowsXP operating system, not less than 800 MBytes. And, it's a laptop with a small disk drive! :-) > > Copy a few megabyte from flash disk is acceptable to most people, and > that's enough to backup the whole pre-installed partition. It certainly is for a DOS installation! :-) > > > Rgds, > Johnson. > > > --- > 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=lnk&kid=103432&bid=230486&dat=121642 > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=lnk&kid=103432&bid=230486&dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Dual Boot WindowsXP and FreeDOS - Alpha testers needed
-- Original message -- From: Gerry Hickman <[EMAIL PROTECTED]> > Hi Mark, > > > As you say, this sounds like a good reason to use a hard disk, although > I'm somewhat confused as to why it can't use the memory and disk caching > to achieve it's goal? Well, no, the morse code is being sent by twiddling a bit on the parallel port. There is critical information that must be saved somewhere...a RAM disk is not acceptable. The problem with USB sticks on a LOT of installations (most, even) is that the write cycle interfears with sending the morse code. SMARTDRV helps somewhat (using MS-DOS) but even that is often not enough. Some of the USB sticks I'm using are, of course, USB-1, and many of the machines also have USB-1 ports. I COULD spend a lot of effort getting this working on a USB stick on a particular machine, but the dual boot works so well, and solves this problem so nicely, that I think this is the way to go. > Bear > in mind the data sticks of today are MUCH faster than the hard drives > DOS was designed to work with. This is frankly not what I see...MUCH slower transfers to or from USB sticks than hard drives...perhaps an order of magnitude slower in fact. > > > This procedure takes ten minutes. Re-installing Windows XP, installing > > all of the applications I have on this machine, and reconfiguring > > everything would take days...not just hours. > > Yes, well obviously I'm talking about doing it BEFORE you have installed > any applications! Still requires re-installing WindowsXP. Why would I want to try that trick when I can resize the partition in a few minutes? Also, I think many XP install/rescue CD's blow away the entire disk, so the old technique (wipe the disk, install DOS, install XP) may not even work. This work laptop is dual-booted. It used to be triple booted with Linux but I took Linux off when I started to run out of disk space. DOS is given a 500MB partition, which is plenty. It's nice to be able to use WindowsXP to download files to that partition and to run some of the utilities without rebooting DOS too. Mark > > -- > Gerry Hickman (London UK) > > > --- > 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=lnk&kid=103432&bid=230486&dat=121642 > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=lnk&kid=103432&bid=230486&dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Multiple DOS
Hi: GAG and GRUB are two free bootloaders...GAG much simpler to set up than GRUB. Mark > > An easy way to do this would be to install the two different > > DOS versions in two different primary partitions and use a > > boot loader like gag (gag.sourceforge.net) to select > > which to boot. GRUB would work as well, but I find > > configuring GRUB correctly a daunting task... :-) > > Perhaps easier than that (if PC-DOS doesn't support FAT32) would be to > install PC-DOS on a FAT16 partition, and then install FreeDOS on a > FAT32 partition; then use a simple bootloader to choose which one to > boot. That way FreeDOS will be able to see both partitions and > FreeDOS will always be the first primary partition to FreeDOS, and > PC-DOS will also act like it is the first DOS primay partition, as it > can only see its own drive and other FAT16 drives. > > > --- > 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 --- 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] Multiple DOS
Hi: An easy way to do this would be to install the two different DOS versions in two different primary partitions and use a boot loader like gag (gag.sourceforge.net) to select which to boot. GRUB would work as well, but I find configuring GRUB correctly a daunting task... :-) Good luck. Mark > Has anyone been able to multiboot PCDOS and FREEDOS? > > CWSIV > > > > > --- > 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 --- 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] Where is my 1mb of xms memory?
Hi Bernd: These images also self-extract, which means you don't need to buy WinImage to use them...if you don't have a floppy drive, you can use VFD to emulate one and get a real disk image file as well! Mark > [EMAIL PROTECTED] schreef: > > For a couple of DOS 6.22 boot floppy images, look at www.bootdisk.com. > > These self-extract to AL, which can be a real floppy drive or a virtual > > Windows drive using VFD (http://chitchat.at.infoseek.co.jp/vmware/vfd.html). > > > > Hope that helps! > > they were created using WinImage, which can also open them. > One of the few occasions for which I use drag-and-drop :) > > (as there isn't a "open exeFILE with program ABC" option) > > remember that running EMM386 isn't ALWAYS the best option, sometimes > running only with HIMEM can get you more available memory. > It depends a lot on total RAM and how many programs/drivers you want to > run and how much memory they each use. > > Bernd > > > > --- > 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 --- 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: Re[2]: [Freedos-user] Where is my 1mb of xms memory?
Hi: For a couple of DOS 6.22 boot floppy images, look at www.bootdisk.com. These self-extract to AL, which can be a real floppy drive or a virtual Windows drive using VFD (http://chitchat.at.infoseek.co.jp/vmware/vfd.html). Hope that helps! Mark > Hello Bernd, > > Monday, August 8, 2005, 5:18:13 PM, you wrote: > > I'm looking for ms dos 6.22 floppy images. This could take a while. > --- 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 1.2.1-k not working
There is a really neat free Windows program called VFD http://chitchat.at.infoseek.co.jp/vmware/vfd.html which I use all the time. It allows you to mount a file as a floppy disk and assign it a drive letter under Windows. You can use diskcopy to/from a real floppy disk (if you have one) or create multiple virtual drives. The FreeDOS sys command runs fine under WindowsXP and will put a boot sector on one of these drives. You can use the resulting image files to create bootable CD's or mount them using VFD and use diskcopy to a real floppy drive if you have one. I don't really miss WinIMAGE. Mark > Hi Bernd, > > > I'm extensively using WinImage. Too bad FreeDOS DISKCOPY isn't as > > flexible as either WinImage and RAWRITE yet. > > WinImage is nice, but it's not free or open-source. [...] But WinImage is great > for browsing big ISO files with lots of subfolders and it also has > "built-in" boot sectors you can choose. I guess we should ask the guy to > put the FreeDOS boot-sector in there too! > --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Newbie installation problem
Hi Blair: No, I think the FDISK /MBR writes a MASTER BOOT RECORD to the hard disk. SYS writes a VOLUME BOOT RECORD to a disk partition, and (if you omit bootonly) copies kernely.sys and command.com to the partition. These are different things. Mark > > SYS C: C: /BOOTONLY > > Try a regular SYS C:. I almost sounds as if you are missing the > kernel on your hard drive, although this shouldn't have happened. > > > FDISK /MBR > > This does basically the same as SYS C: BOOTONLY > > > --- > 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_idt77&alloc_id492&op ick > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Hi Michael: No change with this version...system hangs on vol c: with VDS option, works without. Mark Bailey > At 03:38 AM 7/30/2005 +, Mark Bailey wrote: > > >I see no difference at all with that version, either with the > >development kernel/command.com or the stable kernel/ > >command.com. > > > >Specifically, with > >device=a:\himem.exe > >device=a:\emm386.exe x=test memcheck vds > > > >vol c: hangs. Remove vds, it works normally. (development) > > Alright, one more time. I rewrote the VDS routines such that any reserved > function which was unused (0, 1, 0dh-0ffh) no longer returns an error code, > but simply sets carry flag and chains to old INT 4bh handler. That may get > around a SCSI conflict. Or not. > > In addition, I cleaned up slightly naughty code which re-enabled interrupts > when returning from the VDS call. Theoretically, the VDS interrupt might > have been called with hardware interrupts disabled for good reason. > > Will these revisions change anything? Don't know, but it's the best I can > do without a misbehaving machine here to test. Hopefully no new error was > introduced. Those with VDS-unhappy machines will need to try it out and > report back results. > > To test this version of EMM386, amble over to > ftp.devoresoftware.com\downloads\emm386 and download emmhorse.zip. As > before, unofficial release, no exterior version change, no EXE compression. > > > > > --- > 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=7477&alloc_id=16492&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Re: [Freedos-user]Wildcard Problems - Yes. Test Case!
Hello, all:
OK, I have a test case under Watcom. Unfortunately, IT IS NOT
sufficient to call FINDNEXT before doing the unlink. If you do the
unlink even after the call to FINDNEXT, then files are still skipped.
The test program is:
#include
#include
#include
void main()
{
struct _finddata_t fileinfo;
longhandle;
int rc;
char buffer[_MAX_PATH];
char *status;
int count = 0;
/* Display name and size of "*.c" files */
handle = _findfirst( "*.*", &fileinfo );
rc = handle;
while( rc != -1 )
{
printf( "%14s %10ld\n", fileinfo.name,
fileinfo.size );
status=_fullpath(buffer,fileinfo.name,(size_t) _MAX_PATH);
if (status != NULL)
printf("%s\n",buffer);
else
printf("_fullpath failed\n");
count++;
rc = _findnext( handle, &fileinfo );
if (unlink(buffer) != 0)
printf("Unlink failed.\n");
}
_findclose( handle );
printf("Found %i files.\n",count);
}
This finds all 88 files in the directory if the unlink is commented
out. If the unlink is added, it only finds 79 files (or maybe 78
depending on whether unlink is called before or after _findnext).
This is the same behavior as FreeCOM is showing using Turbo C++.
Is it legal to modify the directory (deleting files) and expect
findnext to work?
Mark Bailey
> OK, I've done a bit more research on this problem. The relevant
> portion of the delete function appears to be, removing some
> extraneous code:
>
> if (FINDFIRST(fullname, &f, FA_ARCH)) {
> error_sfile_not_found(fullname);
> } else do {
> strcpy(p, f.ff_name); /* Make the full
> path */
> [...]
>
> if(verbose && !optP)
> displayString(TEXT_DELETE_FILE,
> fullname);
> if(unlink(fullname) != 0) {
> perror(fullname); /* notify the user
> */
> } else
> ++count;
> } while (FINDNEXT(&f) == 0);
>
> FINDFIRST and FINDNEXT are suppl calls to findfirst and findnext which
> invoke DOS calls (respectively):
>
> r.r_ax = 0x4e00;
> rv = invokeDOS(&r);
>
> r.r_ax = 0x4f00;
> rv = invokeDOS(&r);
>
> Is it legal to do an invokeDOS on this interrupt on a non-existent file?
> The unlink is done before the findnext. There's a test case I may
> be able to duplicate...
>
---
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=7477&alloc_id=16492&op=click
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and FreeCOM - Wildcard Problems?
OK, I've done a bit more research on this problem. The relevant
portion of the delete function appears to be, removing some
extraneous code:
if (FINDFIRST(fullname, &f, FA_ARCH)) {
error_sfile_not_found(fullname);
} else do {
strcpy(p, f.ff_name); /* Make the full
path */
[...]
if(verbose && !optP)
displayString(TEXT_DELETE_FILE,
fullname);
if(unlink(fullname) != 0) {
perror(fullname); /* notify the user
*/
} else
++count;
} while (FINDNEXT(&f) == 0);
FINDFIRST and FINDNEXT are suppl calls to findfirst and findnext which
invoke DOS calls (respectively):
r.r_ax = 0x4e00;
rv = invokeDOS(&r);
r.r_ax = 0x4f00;
rv = invokeDOS(&r);
Is it legal to do an invokeDOS on this interrupt on a non-existent file?
The unlink is done before the findnext. There's a test case I may
be able to duplicate...
I have run this in verbose mode and it only shows the files it is
deleting. After the problem initially occurs, it quite consistently
deletes the first, third, fifth, etc. files on every subsequent del *.*.
This is very repeatable with NTFS4DOS and lots of files to start with.
Mark
> Good day, all:
>
> I am having a repeatable problem with
> "del *.*" on an NTFS partition mounted by NTFS4DOS.
>
> I can do a DIR on the directory I am using (\TEMP) and see
> 86 files. A "del *.*" deletes 74 of them and yields two
> errors:
>
> E:\TEMP\LICENSE.D32: Invalid Argument
> E:\TEMP\SAVE.DBG: Invalid Argument
>
> (Oddly, these two files ARE deleted). This is with the
> development kernel...the debug kernel does not print
> these two errors but behaves the same way).
>
> A subsequent "del *.*" deletes 6 of the twelve files.
> A subsequent "del *.*" deletes 3 of the remaining 6 files.
> A subsequent "del *.*" deletes 2 of the remaining files.
> A subsequent "del *.*" gets the last one.
>
> This is repeatable. I will start reading FreeCOM code, but does
> anyone have any ideas? I also have a report of a wildcard
> copy hanging a computer, but I cannot reproduce that one yet.
>
> This is on the "Haunted HP Pavilion", so clustersize is 2MB.
> However, I haven't found any more accesses to bytes_per_sector
> in FreeCOM.
>
> Any ideas?
>
> Mark Bailey
>
>
> ---
> 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=7477&alloc_id=16492&op=click
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
---
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=7477&alloc_id=16492&op=click
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Bulding FreeCOM? Where is suppl.zip?
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 --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] NTFS4DOS and FreeCOM - Wildcard Problems?
Good day, all: I am having a repeatable problem with "del *.*" on an NTFS partition mounted by NTFS4DOS. I can do a DIR on the directory I am using (\TEMP) and see 86 files. A "del *.*" deletes 74 of them and yields two errors: E:\TEMP\LICENSE.D32: Invalid Argument E:\TEMP\SAVE.DBG: Invalid Argument (Oddly, these two files ARE deleted). This is with the development kernel...the debug kernel does not print these two errors but behaves the same way). A subsequent "del *.*" deletes 6 of the twelve files. A subsequent "del *.*" deletes 3 of the remaining 6 files. A subsequent "del *.*" deletes 2 of the remaining files. A subsequent "del *.*" gets the last one. This is repeatable. I will start reading FreeCOM code, but does anyone have any ideas? I also have a report of a wildcard copy hanging a computer, but I cannot reproduce that one yet. This is on the "Haunted HP Pavilion", so clustersize is 2MB. However, I haven't found any more accesses to bytes_per_sector in FreeCOM. Any ideas? Mark Bailey --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Hi Michael: I dual or triple boot all of my machines and routinely switch from DOS to WindowsXP and back. So, this makes sense. Frankly, XP makes for a more convenient Web and e-mail interface (IMHO! :-)). So, during much, even most, of my testing, I boot XP a lot...sometimes just to copy something like UDMA2 or a new version of EMM386 from the web to a test floppy or to e-mail results of a test. I also create FreeDOS boot CD's and floppies from XP. Mark > At 04:05 AM 7/30/2005 +, Mark wrote: > Interesting thing, though. I could only get the message here if I first > booted into Win XP, then rebooted into my FreeDOS flash stick through > Windows restart. [...] Only rebooting from within XP. > --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] BIOS, SCSI, 8Gb and TUNS
Hi Gerry: Yes, I was running emm386. However, FDISK erased my (and at least one other) partition table without any prompt or request at all when only requested to examine the table. It's too risky to run the program at all until that bug is addressed (IMHO). I believe there is a development version floating around with that fix. It is PROBABLY fairly safe to run it without EMM386, but I do not believe it is worth the risk. There are other tools to examine and manipulate disk partitions that won't destroy the partition table when they have been only asked to examine it. Mark > Hi Mark > > > Ah, yes, ... :-) Try emm386 without the VDS argument > > and under no circumstances run FreeDOS FDISK unless > > you want to risk an erased partition table. > > Can you clarify; when your partition table became damaged, were you > running EMM386 at the time, and have you tried it without? Maybe you > already answered this. > > -- > Gerry Hickman (London UK) > > > --- > 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=7477&alloc_id=16492&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] BIOS, SCSI, 8Gb and TUNS
Hi Gerry: Ah, yes, ... :-) Try emm386 without the VDS argument and under no circumstances run FreeDOS FDISK unless you want to risk an erased partition table. Thanks for reporting this. Let us know what happens without the VDS argument to EMM386! Mark > Hi, > > I tried some rough tests today with BIOS, SCSI and TUNS. Here's are some > results. > > In an eariler post I said I'd seen drive sizes reported as 8Gb with SCSI > when the drives are actually much bigger. I thought it was related to > not using a SCSI driver and BIOS (INT13) reporting wrong size, and Eric > said it wasn't. I think Eric is right, but my BIOS has been updated > since I last seen this problem, so it's impossible to say what caused it. > > I tested today, FreeDOS Beta9 SR1, but with updated HIMEM and EMM386, > two physical SCSI drives of 36Gb each on Adaptec 29160N controller. SCSI > BIOS has both INT13 support enabled, and also INT13 support for drives > larger than 1Gb enabled. Asus AV333 motherboard, AMD Athlon 2100+ > > Test1 (this is really two tests): > > Load FreeDOS with HIMEM only; first WITH SCSI driver, then WITHOUT SCSI > driver. > > Result1: > > Drive size is reported correctly in both FDISK and PQMAGIC in both cases. > > However, enter EMM386 and ALL BETS ARE OFF! I mean total meltdown, with > both FDISK and PQMAGIC saying the drives were not partitioned and giving > totally crazy readings for disk sizes. The EMM386 line was this: > > DEVICE=SPECIAL\EMM386.EXE VDS NOEMS X=TEST /verbose > > When I tried to load my SCSI driver after EMM386 and it just hung. > > I then tested all the above with UMBPCI and everything worked perfectly. > > Testing TUNS: > > I now had a stable system, so decided to test loading LBACACHE high, > both with and without TUNS. > > If I don't have UMBPCI loaded, it's a bit silly because LBACACHE won't > load high, and I don't know if TUNS makes any difference. Output was as > follows: > > DISK 0X80 HEADS 0255 SECTORS 0063 > DISK 0X81 HEADS 0255 SECTORS 0063 [DONE] > > I then tested with UMBPCI loaded, and told LBACACHE to INSTALLhigh > without TUNS, it did exactly as it was told (checked mem /c /p), and > there were no timeouts. It gave the exact same output > > DISK 0X80 HEADS 0255 SECTORS 0063 > DISK 0X81 HEADS 0255 SECTORS 0063 [DONE] > > Here is my FDConfig.SYS file: > > ;device=special\fdxms.sys > DEVICE=DRIVER\HIMEM.EXE /NOABOVE16 /X > ;DEVICE=SPECIAL\EMM386.EXE VDS NOEMS X=TEST /verbose > device=other\umbpci.sys > > rem Load the SCSI for 29160N card > ;device=other\aspi8u2.sys /d > > rem UDMA hard drives > ;DEVICE=DRIVER\UDMA2.SYS > > DEVICEhigh=OTHER\VIDE-CDD.SYS /D:FDCD > > devicehigh=OTHER\ramdrive.sys 4096 512 1024 /e > ;devicehigh=OTHER\ifshlp.sys > > rem lbacache tuns switch is needed for SCSI and UMBPCI > INSTALLhigh=DRIVER\LBACACHE.COM > SHELL=COMMAND.COM A:\ /E:1024 /F /MSG /P=.\FREEDOS\FDAUTO.BAT > > DOSDATA=UMB > DOS=high,UMB > FILES=20 > BUFFERS=20 > LASTDRIVE=Z > > > > -- > Gerry Hickman (London UK) > --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Hi Michael: Well, the E000 message is repeatable on this box... Thanks again for all of your help! Mark > At 03:38 AM 7/30/2005 +, Mark Bailey wrote: > > >Specifically, with > >device=a:\himem.exe > >device=a:\emm386.exe x=test memcheck vds > > > >vol c: hangs. Remove vds, it works normally. (development) > > > >With stable kernel, I get screenfulls of garbage I can't read > >(no newlines) with VDS, normal operation without. > > > >UDMA2 still appears to fix it! > > Appears to mean that UDMA2 blocks the VDS calls because it comes before > EMM386 loads so disk accesses bypass UMB's and VDS, which is effectively > the same result as as not using VDS as an EMM386 parameter. Doesn't help > really, as far as determining your system incompatibility. Or Bernd's for > that matter. > > I've seen the E000 to E000 page frame message myself. It's extremely > intermittent. Can't see why it would happen, but it's never obliged when > debugging. > > Of course, maybe the whole thing means that there is memory corruption > somewhere, which could trash the VDS revector and the page frame > locate. But it's never shown itself as a real entity. > > > > > --- > 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=7477&alloc_id=16492&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Hi Michael: OK, I have done so. The new version still reports version 2.04, July 6, 2005, but is much larger! I see no difference at all with that version, either with the development kernel/command.com or the stable kernel/ command.com. Specifically, with device=a:\himem.exe device=a:\emm386.exe x=test memcheck vds vol c: hangs. Remove vds, it works normally. (development) With stable kernel, I get screenfulls of garbage I can't read (no newlines) with VDS, normal operation without. UDMA2 still appears to fix it! I reported this before, but EMM386 reports the following: selected page frame e000 not available, searching automatically using PAGEFRAME e000: That looks a bit odd... Thanks very much for all of your help! Mark Bailey > At 02:58 PM 7/29/2005 -0400, Mark wrote: > > >Does this provide a means of easily identifying the affected > >machines? How do I check the Haunted HP Pavilion? :-) > > Here's what to do: > > Go to ftp.devoresoftware.com/downloads/emm386 and download > EMMBLORT.ZIP. Try that version of EMM386.EXE with your machine using VDS. > > I changed EMM386 to not report an error with function 0 on a VDS > call. It's normally reserved and gives a VDS error condition, now it just > chains it through with the carry flag set. Hopefully that won't upset things. > > Let me know if that fixes or modifies the current behavior with VDS parameter. > > (Oh yeah, lest it not be obvious, EMMBLORT is not an official release of > EMM386. It is for testing purposes only.) > > > > > --- > 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=7477&alloc_id=16492&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Hi Bernd: OK, back to development kernel, development command.com, UDMA2 V2.5. With config.sys: device=a:\himem.exe device=a:\udma2.sys device=a:\emm386.exe x=test memcheck vds VOL C: works normally. Without device=a:\udma2.sys, vol c: hangs and forces a reboot. (That's the old behavior which I checked to make sure of the test case). This does not appear to be a seperate issue. Mark Bailey > Michael Devore schreef: > > Different issue entirely. Don't know what's going on in VMware, it may > > just not like VDS. > > very probably, yes, Michael. > Mark, can you try loading UDMA2.SYS anyway (in front of EMM386)? > > DEVICE=HIMEM.EXE > DEVICE=UDMA2.SYS > DEVICE=EMM386.EXE VDS other_options > > if that works, then finally what happens for me in VMware isn't > specifically a VMware bug :) > > for the record, the emulator uses a 'Phoenixbios 4.0 release 6'. > wish I could load a proper Linuxbios bios imagefile, then see DOS fail > miserably :) > > http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/udma/devel/Udma2_25. > zip > > Bernd > > > --- > 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=7477&alloc_id=16492&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] VOL Command hangs HP Pavilion with EMM386
Hi Michael: Well, what's trying to use it is the FreeCOM VOL command! (Or something else in FreeCOM). I doubt that there are any explicit calls to VDS functions there. The kernel may be more likely. This appears to be the same bug that caused FDISK to wipe out the MBR, so it at least appears that just initializing the VDS functions is trashing something in memory. I could ship you this laptop if you believe that will help or I can run any test routines you can think of! Mark Bailey > At 11:53 PM 7/28/2005 +, Mark wrote: > > >Do I need VDS? :-) What does it do? How can I help > >identify the problem? I do have the Haunted HP Pavilion (TM)! > > Turn it off if everything works without it. It's just for upper memory > reporting of true physical address instead of logical address for DMA > purposes. Maybe something is trying to use a function that isn't supported > or ignoring a return code that a sub-function is not supported. You don't > see any feedback messages when it's present do you? VDS will write to > display a line about unsupported functions, but can't help if a program > tries to use a subfunction that returns an unsupported code. > > Without the machine that croaks, though, not much chance I can tell you > what's going on with the VDS problem. Could be the fault of either VDS > support, or what's trying to use VDS. And no way of knowing here what or > how to fix/work around it. > > I was going to make VDS a default, maybe I shouldn't. > > > > > --- > 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 --- 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] VOL Command hangs HP Pavilion with EMM386
Hi Bernd et al: I wish to thank all of you again for the wonderful support and help! I have been amazed at the responsiveness of the FreeDOS community! Back with the haunted HP Pavilion (TM). Development kernel, sys, and command.com from fdos.org/kernel. EMM386.EXE and HIMEM.SYS from emm204x.zip. Random edit.com. config.sys: device=a:\himem.exe device=a:\emm386.exe x=test memcheck A:\> vol c: works fine. Reports correct serial number. So, it does appear to be the VDS parameter. I can have that checked by a couple of people who are also having failure to boot problems with FreeDOS if we believe that it will help. Do I need VDS? :-) What does it do? How can I help identify the problem? I do have the Haunted HP Pavilion (TM)! Mark > [EMAIL PROTECTED] schreef: > > Hello all: > > As I mentioned before, remove the VDS parameter and see if things go > better then. > VMware suffers from incompatibility with the VDS parameter, maybe your > system also. Maybe even a lot of systems, but that's a wild guess. > > IF things fail even without the VDS parameter, then please report to > this mailinglist. > > ANY access to C: might cause trouble. > > maybe time for me again to make an experimental bootdisk and let people > report to the mailinglist if things go OK or fail. > > Bernd > > > > > --- > 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 --- 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] VOL Command hangs HP Pavilion with EMM386
Hi Michael, et al: OK, I am back with the Haunted HP Pavilion (TM). Downloaded development kernel, command.com, and sys.com from fdos.org/kernel. Downloaded emm204x and extracted himem.exe and emm386.exe. Did a SYS: on a USB floppy from WindowsXP. Copied a random version of edit.com on the floppy. Baseline test: config.sys device=a:\himem.exe device=a:\emm386.exe x=test vds memcheck Booted. Edited config.sys. Entered "vol c:". Machine hung. Three finger reboot worked. config.sys device=a:\himem.exe rem Edited config.sys. Entered "vol c:". Worked fine, reporting Volume in drive C has no label Volume serial number is 2640-14E4 (correct serial number verified from WindowsXP). config.sys device=a:\himem.exe device=a:\emm386.exe x=a000-efff noems emm386 reports no suitable UMB memory block found. Edited config.sys. Entered "vol c:". Worked fine. config.sys device=a:\himem.exe device=a:\emm386.exe x=a000-efff noems memcheck Same advisory from emm386. Edited config.sys. Entered "vol c:". Worked fine. config.sys device=a:\himem.exe device=a:\emm386.exe x=a000-efff noems memcheck vds Entered "vol c:". Hung. Three finger reboot worked. Okay, now what? Do I need VDS? :-) Eliminating that will be my next experiment with NTFS4DOS! Mark > At 12:22 AM 7/28/2005 +, Mark Bailey wrote: > > >Help! How do I start to debug this?!?! This is the same machine > >which has FDISK overwriting the partition table whenever it is run > >with EMM386. > > Exclude all high memory via X=A000-EFFF and add NOEMS option. Those two > options only, unless your USB driver needs MEMCHECK (some do). Tells you > whether you have an upper memory block conflict. So, try: > > EMM386 X=A000-EFFF NOEMS > > EMM386 X=A000-EFFF NOEMS MEMCHECK > > > > > --- > 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 --- 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
[Freedos-user] VOL Command hangs HP Pavilion with EMM386
Hello all: OK, now that I've at least identified the FDISK problem, and solved the DIR divide by zero problem, I need to work on why FreeDOS doesn't boot and/or run stably on many computers. Fortunately, I have the Haunted HP Pavilion. I have a repeateable problem with the VOL command built into FreeCOM. Development kernel, development command.com, development sys.com. HIMEM.EXE and EMM386.EXE from emmx204.zip. Booting from USB floppy. (EDIT from Beta9SR1 CD :-)). config.sys: device=a:\himem.exe REM device=a:\emm38.exe x=test max=256M memcheck vds Boot HP Pavilion: [...] C: HD1, Pri[ 1], CHS= 0-1-1, start= 0 MB, size= 16MB WARNING: partition Pri:4 FS 06 has CHS=3584-0-1, not 1023-254-63 WARNING: partition Pri:4 FS 06 has CHS=3646-254-63, not 1023-354-63 WARNING: partition Pri:4 FS 06 is not LBA Please run FDISK to correct this - using LBA to access partition. start 3584-0-1, end 3646-254-63 D: HD1, Pri[ 4], CHS=3584-0-1, start=28113 MB, size=494 MB FreeDOS HIMEM64 4.11 [...] HIMEM - BIOS A20 method used A:\> vol c: Volume in drive C has no label Volume Serial Number is 2640-14E4 A:\> vol d: Volume in drive D has no label Volume Serial Number is 6D08-68B3 A:\> Change config.sys to: device=a:\himem.sys device=a:\emm386.exe x=test max=256M memcheck vds and reboot. [...] EMM386 2.04 [...] selected page frame e000 not available, searching automatically using PAGEFRAME e000: A:\> vol d: That's it...no output and no return. Repeat, removing MEMCHECK option from emm386. Still hangs. Remove x=test and add NOEMS. (config.sys now: device=a:\himem.exe device=a:\emm386.exe noems max=256M vds) Screen full of rapidly repeating garbage I can't read...looks like a register dump...the pattern looks like two lines but it scrolls by so fast I can't read it until I turn the power off. Add memcheck to device=a:\emm386 line. No change, rapidly scrolling garbage. Remove NOEMS. EMM386 2.04 [...] No other lines from EMM386. Boots normally, A:\> vol d: hangs. Help! How do I start to debug this?!?! This is the same machine which has FDISK overwriting the partition table whenever it is run with EMM386. Thanks. Mark Bailey --- 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
[Freedos-user] NTFS4DOS Divide error - FreeDOS but not MS-DOS 7.1
Good day, all: I have another FreeDOS problem with NTFS4DOS. This one DOES NOT affect MS-DOS (I think it's called 7.1...version from Windows98SE). The problem is a divide error. Without himem.exe loaded, I get Divide error Divide error . (lots of these, very quickly, followed by a repeating garbage pattern until I reboot using the same procedure as below) With himem.exe loaded: A:>a:\datapol\ntfs4dos (Identifies my two NTFS drives...assigning the first E:, the second F:) A:>dir e: Volume in drive E is PRESARIO DIR of E:\ autoexec.bat 010-15-04 7:38P config.sys 0 [...] (and six directories) 2 file(s) 0 bytes 6 dir(s) Divide error, stack: FB41 19A8 3246 15B5 38C8 6AE5 19A8 81DB 38A4 Hangs until I reboot. Windows dir command shows 69,679,292,416 bytes free. MS-DOS shows 2 file(s) 0 bytes 6 dir(s) A:> I have asked Datapol, but what's going on here? Thanks in advance for your help. I continue to believe that NTFS4DOS will be a very valuable tool for FreeDOS users, and I think getting it working is important. Development kernel (1.1.35w), new command.com, new himem.exe. This was particularly badly behaved when himem.exe was not loaded (because I copied the trivial MS-DOS config.sys file and forgot to change himem.sys to himem.exe! :-)) Mark Bailey --- 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=7477&alloc_id=16492&op=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
This may be a side effect of memory corruption with EMM386. In fact, it appears to be a result of some interaction with EMM386. I do not believe the hard disk in question is faulty and I do not believe that it has non-standard parameters. I do not believe the memory corruption is due to the hard drive configuration. There are plenty of other solutions... I recommend using one of them instead of FreeDOS FDISK. :-( Mark > Hi Michael, > > >> If it's always been there, why have more people not been affected? > > > Biggest mitigating factors are that if your hard drive behaves without > > errors, is reasonably standard with expected parameters, and there is no > > corruption of the program, the MBR write on startup won't occur. > > Ah, so this bug only happens with faulty hard-drives or file-systems? > > It's just I have to build 30 PCs in coming weeks, plus some production > servers, and plan to use FreeDOS FDISK to partition them. I was a bit > worried reading about this bug, but all my hard drives are brand new, so > should be OK. --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS won't boot correctly from hard disk
Hi: Thanks. I know all of these workarounds. The problem was an apparent bug in an older version of FreeDOS sys.com. Mark > On Wed, 2005-07-20 at 17:16, [EMAIL PROTECTED] wrote: > > Hello, all: > > > > Back to my other laptop and other problem. I am unable to install > > FreeDOS on my 477 MB FAT32 partition. This is a DIFFERENT laptop > > entirely. There is an extended partition, and an NTFS partition. > > The FAT32 partition is a primary partition (the third, I believe). > > > www.bootdisk.com > > try it with a MSDOS 622 or PCDOS disk and use its fdisk. > > There is some disagreement about partition marking between windows and > linux and rumors that MickeyMouse will be changing again for some > version of NTFS. > > So I would advise trying to cheat in this way. > > BTW there is now an Oreilly book on Knoppix and its tricks. Looked like > a good toolkit to have just in case. > > -- > +-<<>>+ > || > || \ /|\ || |\ / |~~\ /~~\ /~~| //~~\| > || \ / | \ || | X |__/||| |( `--.| > ||__ | | \| \_/ / \ | \ \__/ \__| \\__/| > || > ++ > > > > --- > 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=7477&alloc_id=16492&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=7477&alloc_id=16492&op=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
I agree. It is far too risky to run the FreeDOS FDISK under any circumstances - just based on the limited tests I have done. I will run it ONLY on this test computer. It becomes even more of an adventure given your analysis of the source code! :-) Mark > At 11:40 PM 7/21/2005 +, Mark wrote: > > >Are any of the tests that have been suggested (other kernels, > >MS-DOS, ommitting VDS, trying UDMA2, older versions of > >FDISK, etc.) going to help in getting this problem fixed? I have > >a repeatable problem (always a good thing) and have, I think, > >done a pretty good job isolating it. I will be glad to try > >another test when it will help, but I am not inclined to start > >running more tests at random! :-) This has taken an > >unbelievable amount of time to isolate! > > My point, which may have been buried, is that I don't think you or anyone > else should use FDISK at all until at least the problems I listed are > fixed. It's just a dangerous piece of software right now, with no > protections on errors. Any disk read error or failure to interpret > something from the BIOS properly will eat your disk MBR. No good, no good > at all. > > > > > --- > 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=7477&alloc_id=16492&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=7477&alloc_id=16492&op=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
Hi Michael et al: Fiddling with this is very time consuming and a bit risky. Though, so far, it has only been the partition table that has gotten clobbered. And, only one machine that I know of appears to have permanently lost all of its data as a result. The rest have been recoverable using Linux disk recovery tools. Are any of the tests that have been suggested (other kernels, MS-DOS, ommitting VDS, trying UDMA2, older versions of FDISK, etc.) going to help in getting this problem fixed? I have a repeatable problem (always a good thing) and have, I think, done a pretty good job isolating it. I will be glad to try another test when it will help, but I am not inclined to start running more tests at random! :-) This has taken an unbelievable amount of time to isolate! By the way, I consider this bug extremely serious. The worst possible bug would trash the data instead of just the partition table, but this one is close! I'd be suprised if the FreeDOS project had very many that were more critical. Mark Bailey > 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. > --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS won't boot correctly from hard disk
Hello, all: I downloaded the development kernel, SYS, and command.com files TODAY and repeated the experiment. Everything worked fine...the hard disk boots, is recognized, and comes up as C:. There is no A: confusion. I did some research and learned way more than I ever wanted to know about volume boot sectors. :-) The SYS version says V3.6, July 21, 2005. Does that mean it was updated or it it somehow automatically built every day? The version that failed was version 3.4, so I guess this problem was fixed. This problem would have been enough to send a casual user back to MS-DOS (IMHO). :-( Now, back to the FDISK problem - tomorrow, maybe. Mark > Hello, all: > > Back to my other laptop and other problem. I am unable to install > FreeDOS on my 477 MB FAT32 partition. This is a DIFFERENT laptop > entirely. There is an extended partition, and an NTFS partition. > The FAT32 partition is a primary partition (the third, I believe). > > I just grabbed a Windows98SE boot disk, booted it from a USB > floppy, and did a SYS C:. Rebooting (yes, using GAG) yielded a > C:> prompt and a functioning MS-DOS installation. > > Rebooted Windows and reformatted the partition. Booted the > Beta9SR1 CD. Entered 1 1 2 to run FreeDOS. From the > X:\whatever prompt, entered A:. > > Entered > SYS C: > > DIR C: shows the files. (kernel.sys command.com). > > Rebooted. Got an error about being unable to find command.com. > entered a:\command.com a:/ > > Got an error about C: being invalid and a > > > prompt. Entered A:. > > A: looks like the hard disk partition which was booted. DIR C: > and DIR D: fail. During boot, the kernel recogizes the two > partitions on the hard drive as C: and D:, according to the > messages that go by. > > Any ideas on the problem here? I've tried various times to use > different versions of SYS, booting from floppy, etc., but have been > unsuccessful. > > Obviously, this should boot correctly to a C:> prompt. > > Mark Bailey > > > --- > 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=7477&alloc_id=16492&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=7477&alloc_id=16492&op=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
Hi Bernd: I'll try that. I'm only willing to run this on the one computer...too risky for any others. I'm not blaming fdisk, but do not consider running it safe. If I do not run fdisk, the disk partition table does not get destroyed! Mark > [EMAIL PROTECTED] schreef: > > Ok, I just added edit.exe to my boot floppy! :-) > > > > First, modifying config.sys to: > > a:\device=himem.exe > > a:\device=emm386.exe noems X=a000-efff memcheck vds > > > > EMM386 reports "no suitable UMB memory block found" :-) > > > > FDISK shows a bunch of garbage after "Do you want to use > > large disk (FAT32) support (Y/N). I hit and rebooted. > > > > The kernel no longer sees the partitions on boot. So, that still failed, > > trashing my partition table. > > load UDMA2.SYS before EMM386, or get rid of the VDS parameter for > EMM386. Disk isn't found then in VMware, so I'm not even trying a real > computer as I'm not sure if it actually harms the harddisk data or only > corrupts access to the harddisk. > > I should probably try HIMEM/EMM386 with VDS parameter on a partition > running MSDOS kernel, to see if disk is still accessible. > > DEVICE=HIMEM.EXE > DEVICE=UDMA2.SYS > DEVICE=EMM386.EXE NOEMS X=A000-EFFF MEMCHECK VDS > > -or- > > DEVICE=HIMEM.EXE > DEVICE=EMM386.EXE NOEMS X=A000-EFFF MEMCHECK > > I'm not searching for to blame a component, too many factors involved. > > Bernd > > > --- > 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=7477&alloc_id=16492&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] FreeDOS won't boot correctly from hard disk
Hello, all: Back to my other laptop and other problem. I am unable to install FreeDOS on my 477 MB FAT32 partition. This is a DIFFERENT laptop entirely. There is an extended partition, and an NTFS partition. The FAT32 partition is a primary partition (the third, I believe). I just grabbed a Windows98SE boot disk, booted it from a USB floppy, and did a SYS C:. Rebooting (yes, using GAG) yielded a C:> prompt and a functioning MS-DOS installation. Rebooted Windows and reformatted the partition. Booted the Beta9SR1 CD. Entered 1 1 2 to run FreeDOS. From the X:\whatever prompt, entered A:. Entered SYS C: DIR C: shows the files. (kernel.sys command.com). Rebooted. Got an error about being unable to find command.com. entered a:\command.com a:/ Got an error about C: being invalid and a > prompt. Entered A:. A: looks like the hard disk partition which was booted. DIR C: and DIR D: fail. During boot, the kernel recogizes the two partitions on the hard drive as C: and D:, according to the messages that go by. Any ideas on the problem here? I've tried various times to use different versions of SYS, booting from floppy, etc., but have been unsuccessful. Obviously, this should boot correctly to a C:> prompt. Mark Bailey --- 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=7477&alloc_id=16492&op=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
Ok, I just added edit.exe to my boot floppy! :-) First, modifying config.sys to: a:\device=himem.exe a:\device=emm386.exe noems X=a000-efff memcheck vds EMM386 reports "no suitable UMB memory block found" :-) FDISK shows a bunch of garbage after "Do you want to use large disk (FAT32) support (Y/N). I hit and rebooted. The kernel no longer sees the partitions on boot. So, that still failed, trashing my partition table. OK, let's restore it AGAIN. (I just tried DIR commands on the restored partitions which failed. They just hung...odd). Make config.sys a:\device=himem.exe Reboot. The DIR commands now work. Reboot again. Kernel still recognizes the partitions. emm386.exe not run. FDISK did NOT trash my MBR. Bare himem. Mark > I'd recommend a test with EMM386 option X=A000-EFFF instead of TEST (i.e. > absolutely no UMBs) in case there's an upper memory block that looks good, > but is actually used by a disk ROM. Could cause serious confusion if that > happens. And then just bare HIMEM, without EMM386, if it still works with > full UMB exclusion, in case of a DMA situation. > --- 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=7477&alloc_id=16492&op=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
Hi Bernd: I don't believe it is just FDISK. It appears to be FDISK + EMM386, maybe plus the development kernel. However, until this is isolated and the cause understood, I do not recommend using it. There are other tools which do the same thing! :-) Mark > [EMAIL PROTECTED] schreef: > > Meanwhile, personally, I don't recommend using FreeDOS FDISK! :-( > > > > Mark > > I hope you have the option of using FreeDOS FDISK running under as many > MS components as you can (kernel, shell, himem, emm386). A Win98 > bootdisk for example. > > Just to be absolutely sure it's solely the FreeFdisk program to be blamed. > > and you might try other versions if you want from > http://www.23cc.com/free-fdisk/ > > Thanks for your investigations. > > Bernd > > > --- > 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=7477&alloc_id=16492&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=7477&alloc_id=16492&op=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
OK. Back to the standard development kernel. config.sys still has himem.exe and emm386.exe. No autoexec.bat. Boot floppy without running FDISK. Reboot Linux. Partition table normal. Copy it to the floppy this time! :-) Reboot FreeDOS from floppy. A:> fdisk Displays a bunch of garbage after (Y/N). No [Y], no characters I can find on my keyboard. Try ...advances to next screen...garbage after Enter choice: Try ...back to prompt. Reboot...I didn't like the looks of that. This looked normal. A:> fdisk [Y] [4] No partitions defined. Restore the disk partition again. I suppose I could check and make sure that it's emm386 instead of himem, but I hope this gives y'all enough information to debug this. I also DO NOT feel like trying this on any of my other computers! Meanwhile, personally, I don't recommend using FreeDOS FDISK! :-( Mark > Hello, all: > > OK, on my "haunted" HP laptop, I am going to try another test. > I just ran the Linux FDISK...it warns: > > "The number of cylinders for this disk is set to 3648. > There is nothing wrong with that, but this is larger than 1024, > and could in certain setups cause problems with: > ... > 2) booting and partitioning software from other OSs > (e.g., DOS FDISK, OS/2 FDISK) > > It seems to work. > > > I have now created what I believe to be the simplest > possible FreeDOS boot floppy: > > I downloaded the development kernel, command.com, and > sys.com from www.fdis.org/kernel. Ran sys.com from WindowsXP > and copied the FDISK.exe file from the Beta9SR1 CD into the > root directory. > > Booting the resulting floppy (on a USB floppy drive). > > FreeDOS kernel version 1.1.35w (Build 2035w-UNSTABLE, Jul 20 2005) > > [...] > > Warning: partition Pri:1 FS 04 has CHS= 2-11-8, not 1-254-63 > C: HD1, Pri [ 1], CHS= 0-1-1, start= 0 MB, size=16 MB > WARNING: partition Pri:4 FFS 06 is not LBA > Please run FDISK to correct this - using LBA to access partition. > start 3584-0-1, end 3646-254-63 > D: HD1, Pri[ 4], CHS= 3584-0-1, start=28113MB, size = 494 MB > > [...] > > Enter new date (mm-dd-[cc]yy): > > OK, this looks OK. Reboot Linux and run their FDISK again. > Still looks normal: > > Device Boot Start End Blocks ID System > /dev/hda1 1 3163844 FAT16 > <32M > /dev/hda3* 17 358428657936 7 HPFS/NTFS > /dev/hda4 3585 3647 506047+ 6 FAT16 > > Reboot haunted HP again. > > Enter returns at date/time prompt. Get to A:> prompt. > > Reboot Linux and check fdisk. (Booting Linux from CD). > > Linux fdisk shows the same. > > Reboot FreeDOS. Return at date and time prompts. > > a:> fdisk > [...] > Do you want to use large disk (FAT32) support (Y/N).[Y] > > Free FDISK Version 1.3.0 DEBUG > > Enter choice:[4] > > Damn. Appeared to work. Shows a reasonable table. > > Reboot Linux and check. Fine. > > Reboot floppy several times with no problems. > > Replace kernel with DEBUG kernel from the same page. > > Reboot. FDISK still normal. :-( > > OK. Go and download emmx204.zip and copy emm386.exe and himem.exe > to the floppy. > > Create a config.sys on the floppy: > > device=a:\himem.sys > device=a:\emm386.exe noems x=test memcheck vds > > A:> fdisk > ... [Y] > [4] > > BOOM! FDISK reports "NO PARTITIONS DEFINED" > > Now, that's interesting... > > Mark > > > --- > 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=7477&alloc_id=16492&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] More FreeDOS FDISK tests
Hello, all: OK, on my "haunted" HP laptop, I am going to try another test. I just ran the Linux FDISK...it warns: "The number of cylinders for this disk is set to 3648. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: ... 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) It seems to work. I have now created what I believe to be the simplest possible FreeDOS boot floppy: I downloaded the development kernel, command.com, and sys.com from www.fdis.org/kernel. Ran sys.com from WindowsXP and copied the FDISK.exe file from the Beta9SR1 CD into the root directory. Booting the resulting floppy (on a USB floppy drive). FreeDOS kernel version 1.1.35w (Build 2035w-UNSTABLE, Jul 20 2005) [...] Warning: partition Pri:1 FS 04 has CHS= 2-11-8, not 1-254-63 C: HD1, Pri [ 1], CHS= 0-1-1, start= 0 MB, size=16 MB WARNING: partition Pri:4 FFS 06 is not LBA Please run FDISK to correct this - using LBA to access partition. start 3584-0-1, end 3646-254-63 D: HD1, Pri[ 4], CHS= 3584-0-1, start=28113MB, size = 494 MB [...] Enter new date (mm-dd-[cc]yy): OK, this looks OK. Reboot Linux and run their FDISK again. Still looks normal: Device Boot Start End Blocks ID System /dev/hda1 1 3163844 FAT16 <32M /dev/hda3* 17 358428657936 7 HPFS/NTFS /dev/hda4 3585 3647 506047+ 6 FAT16 Reboot haunted HP again. Enter returns at date/time prompt. Get to A:> prompt. Reboot Linux and check fdisk. (Booting Linux from CD). Linux fdisk shows the same. Reboot FreeDOS. Return at date and time prompts. a:> fdisk [...] Do you want to use large disk (FAT32) support (Y/N).[Y] Free FDISK Version 1.3.0 DEBUG Enter choice:[4] Damn. Appeared to work. Shows a reasonable table. Reboot Linux and check. Fine. Reboot floppy several times with no problems. Replace kernel with DEBUG kernel from the same page. Reboot. FDISK still normal. :-( OK. Go and download emmx204.zip and copy emm386.exe and himem.exe to the floppy. Create a config.sys on the floppy: device=a:\himem.sys device=a:\emm386.exe noems x=test memcheck vds A:> fdisk ... [Y] [4] BOOM! FDISK reports "NO PARTITIONS DEFINED" Now, that's interesting... Mark --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Partition Table Trashed again - repeatable!!!
Hello, all: IT'S REPEATABLE. I just booted Beta9SR1 from CD many times and ran FDISK like crazy with no problems. I booted a floppy with the kernel Jeremy wanted me to run, ran FDISK, and it reported no partitions! And, blew my partition table. The original table was: 000: fafc 31c0 8ed0 8ed8 bd00 7c8d 66e0 fbb8 ..1...|.f... 010: e01f 8ec0 89ee 89ef b900 01f3 a5ea 227c .."| 020: e01f 8ed8 8ed0 31c0 8ec0 8dbe be01 f605 ..1. 030: 8075 7181 c710 0081 fffe 7d72 f1e8 c700 .uq...}r 040: 6e6f 2061 6374 6976 6520 7061 7274 6974 no active partit 050: 696f 6e20 666f 756e 6400 e9fd ffe8 a700 ion found... 060: 7265 6164 2065 7272 6f72 2077 6869 6c65 read error while 070: 2072 6561 6469 6e67 2064 7269 7665 00e9 reading drive.. 080: d8ff e882 0070 6172 7469 7469 6f6e 2073 .partition s 090: 6967 6e61 7475 7265 2021 3d20 3535 4141 ignature != 55AA 0a0: 00e9 b6ff e810 0072 b426 813e fe7d 55aa ...r.&.>.}U. 0b0: 75d0 ea00 7c00 00bb aa55 b441 cd13 7232 u...|U.A..r2 0c0: 81fb 55aa 752c f6c1 0174 27eb 1010 0004 ..U.u,...t'. 0d0: 7c00 008b 4508 ..|...E. 0e0: a3d5 7c8b 450a a3d7 7cb8 0042 becd 7ccd ..|.E...|..B..|. 0f0: 13c3 b804 02bb 007c 8b4d 028a 7501 cd13 ...|.M..u... 100: c331 dbb4 0ecd 105e ac56 3c00 75f3 c300 .1.^.V<.u... 110: 120: 130: 140: 150: 160: 170: 180: 190: 1a0: 1b0: cd39 ce39 0001 .9.9 1c0: 0100 04fe 3f01 3f00 0080 ?.?. 1d0: 8000 1e0: 0110 07fe 7ffe 10ec 0300 2092 6a03 .. .j... 1f0: 8100 06fe bf3e 008e 6e03 7f71 0f00 55aa .>..n..q..U. boot, from A:> prompt: fdisk Y 4 no partitions Trashed partition table!!! 000: fafc 31c0 8ed0 8ed8 bd00 7c8d 66e0 fbb8 ..1...|.f... 010: e01f 8ec0 89ee 89ef b900 01f3 a5ea 227c .."| 020: e01f 8ed8 8ed0 31c0 8ec0 8dbe be01 f605 ..1. 030: 8075 7181 c710 0081 fffe 7d72 f1e8 c700 .uq...}r 040: 6e6f 2061 6374 6976 6520 7061 7274 6974 no active partit 050: 696f 6e20 666f 756e 6400 e9fd ffe8 a700 ion found... 060: 7265 6164 2065 7272 6f72 2077 6869 6c65 read error while 070: 2072 6561 6469 6e67 2064 7269 7665 00e9 reading drive.. 080: d8ff e882 0070 6172 7469 7469 6f6e 2073 .partition s 090: 6967 6e61 7475 7265 2021 3d20 3535 4141 ignature != 55AA 0a0: 00e9 b6ff e810 0072 b426 813e fe7d 55aa ...r.&.>.}U. 0b0: 75d0 ea00 7c00 00bb aa55 b441 cd13 7232 u...|U.A..r2 0c0: 81fb 55aa 752c f6c1 0174 27eb 1010 0004 ..U.u,...t'. 0d0: 7c00 008b 4508 ..|...E. 0e0: a3d5 7c8b 450a a3d7 7cb8 0042 becd 7ccd ..|.E...|..B..|. 0f0: 13c3 b804 02bb 007c 8b4d 028a 7501 cd13 ...|.M..u... 100: c331 dbb4 0ecd 105e ac56 3c00 75f3 c300 .1.^.V<.u... 110: 120: 130: 140: 150: 160: 170: 180: 190: 1a0: 1b0: 1c0: 1d0: 1e0: 1f0: 55aa ..U. Thank goodness for Linux and gpart!!! :-) I'm going to bed. Mark --- 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. htt
[Freedos-user] Partition table trashed again
Hello, all: OK, either booting FreeDOS over and over, doing a DIR C: on a recognized partiton which hung, or doing fdisk operations trashed my partition table again. There's a problem somewhere. I suppose it could be a BIOS bug, but I'm leaning towards FDISK. Here's the trashed MBR: 000: fafc 31c0 8ed0 8ed8 bd00 7c8d 66e0 fbb8 ..1...|.f... 010: e01f 8ec0 89ee 89ef b900 01f3 a5ea 227c .."| 020: e01f 8ed8 8ed0 31c0 8ec0 8dbe be01 f605 ..1. 030: 8075 7181 c710 0081 fffe 7d72 f1e8 c700 .uq...}r 040: 6e6f 2061 6374 6976 6520 7061 7274 6974 no active partit 050: 696f 6e20 666f 756e 6400 e9fd ffe8 a700 ion found... 060: 7265 6164 2065 7272 6f72 2077 6869 6c65 read error while 070: 2072 6561 6469 6e67 2064 7269 7665 00e9 reading drive.. 080: d8ff e882 0070 6172 7469 7469 6f6e 2073 .partition s 090: 6967 6e61 7475 7265 2021 3d20 3535 4141 ignature != 55AA 0a0: 00e9 b6ff e810 0072 b426 813e fe7d 55aa ...r.&.>.}U. 0b0: 75d0 ea00 7c00 00bb aa55 b441 cd13 7232 u...|U.A..r2 0c0: 81fb 55aa 752c f6c1 0174 27eb 1010 0004 ..U.u,...t'. 0d0: 7c00 008b 4508 ..|...E. 0e0: a3d5 7c8b 450a a3d7 7cb8 0042 becd 7ccd ..|.E...|..B..|. 0f0: 13c3 b804 02bb 007c 8b4d 028a 7501 cd13 ...|.M..u... 100: c331 dbb4 0ecd 105e ac56 3c00 75f3 c300 .1.^.V<.u... 110: 120: 130: 140: 150: 160: 170: 180: 190: 1a0: 1b0: 1c0: 1d0: 1e0: 1f0: 55aa ..U. Mark --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How does SYS determine bootsector to install?
Hi Bernd: Thanks for the help. I booted from the Beta9SR1 CD and exited to a DOS shell (X: prompt). I am using the GAG bootloader from the MBR of the hard disk, and selected primary partition 3 (where FreeDOS is installed). This is a primary FAT32 partition, marked active by GAG, and I performed a "SYS C: /bootonly" from the CD command line. (I also tried variants of SYS C: /bootonly /b ff and such without making any difference). The boot of FreeDOS starts normally and shows my two disk partitions correctly: C: HD1, Pri[ 3], CHS=1919-0-1, start=15053MB, size=478MB D: HD1, Ext[ 1], CHS=1980-1-1. start=15531MB, size=9036MB Bad or missing Command Interpreter (I entered a:\command.com a:/) FreeCom version 0.82... Error reading from drive C: DOS area: unknown command given to driver (I entered F for Fail) Drive C: not responding > (I entered a:. A DIR on A: showed the first partition and the FreeDOS files. The config file and autoexec.bat are written for C:). Here is the DIR C: result (taken from the Beta9SR1 CD boot): Volume in drive C is FREEDOS Volume Serial Number is F493-CCEE Directory of C:\ DATAPOL07-19-2005 7:55a FDOS 07-19-2005 7:55a AUTOEXEC BAT 361 07-19-2005 8:01a COMMAND COM68,353 07-18-2005 8:00p CONFIG SYS 392 07-19-2005 8:06a KERNEL SYS44,056 07-19-2005 7:27a SYS COM11,459 07-19-2005 7:34a 5 file(s)124,621 bytes 2 dir(s)476 Mega bytes free For good measure, here's the fdisk /info /tech (also from the Beta9SR1 CD command line): Current fixed disk drive: 1 (TC: 4864 TH: 254 TS: 63) Partition Status Mbytes Description Usage Start Cyl End Cyl 1 222 55 Unknown 0% 0 6 2 7 A 14998 NTFS 39% 7 1918 C: 3 12 478 FAT32 (LBA) 1%1919 1979 4 522623 Extended 59%1980 4863 Contents of Extended DOS Partition: Drv Volume Label Mbytes System Usage D: NO NAME9037 FAT32 L40% 12598 Linux N56% 486 Linux S 2% Thanks again. Why the heck is this sort of A:? Mark > [EMAIL PROTECTED] schreef: > > Harddisk partition should have FAT12, FAT16 or FAT32 filesystem, be a > primary partition, be an ACTIVE primary partition, and contain a > bootsector which points to the kernel to be loaded. > > > > When I boot the disk partition, it begins to boot as A:! This causes > > great difficulty...it should be C:. > > boot from a diskette and do a DIR C:, then post output on this mailinglist. > > > > Mark > > sometimes your name shows up, other times only your email address as > sender. Strange. > > Bernd > --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] How does SYS determine bootsector to install?
Good day, all: I just attempted to install FreeDOS on a partition on this laptop again. I copied the new, development, SYS.COM command to the root of a floppy disk image, created a CD, and booted the cd. Everything is normal, so I entered "SYS C:". When I boot the disk partition, it begins to boot as A:! This causes great difficulty...it should be C:. My best theory at the moment is that, since SYS.COM was in the root directory of the boot media, it copied the floppy disk image boot sector and that is somehow different than a hard disk boot sector. I read the documentation page at http://freedos.sourceforge.net/kernel/docs/sys.htm but that didn't help me. The beta9 installation CD uses a file freedos.bss. Do I need to explicitely identify that? Thanks! Mark --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] re: FDISK Corruption - no smoking gun
Good evening, all: I screwed up my analysis of the MBR files badly. I apologize for wasting your time. I do not understand what happened, but the MBR does not appear to have been modified. It may be something to do with a restart versus a cold reboot. I will test that tomorrow evening. Again, I sorry about screwing up! Thanks for your patience. (And, thanks, Eric, for the lessons in how to format the dumps. I have downloaded xxd and will use it if the requirement arises again! :-) ) Mark --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] re: FDISK Corruption - possible smoking gun
Hi Eric:
OK, let's try again. I apologize profusely for the HTML
formatting...I hate it myself. The darned webmail
client decided I wanted it for some reason.
The original post I sent was the output of FDISK from
booting Beta9SR1. The first time, no complaints.
Current fixed disk drive: 1 (TC: 3648 TH: 254 TS: 63)
Partition Status Mbytes Description Usage Start Cyl End Cyl
1 20 16 Hidden FAT16 0% 0 1
3 7 A 27980 NTFS 98% 16 3582
C: 4 6 494 FAT16 2% 3584 3646
I must have erred in capturing the MBR before I started.
(See MBR.TXT attached). The resulting MBR is NEWMBR1.TXT
and I'm sure that's right...cause I went and redid it when it
didn't look like the original.
Recall that the first time I booted Beta9SR1 it ran fine.
When I tried to boot the new kernel, it complained and
then Beta9SR1 complained. It appears that either simply
booting one of these, or more likely, running
fdisk, did change the partition table.
Is THIS plain text?
Mark
>
> Hi (your last mail to the -user list was in html, oops),
> FreeDOS is right to complain here: There is an official
> partition type for FAT16 LBA, but you have a partition
> which is marked as FAT16 CHS while at the same time reaching
> beyond the 1024 cylinders that CHS can reach! WinXP seems
> to just ignore the problem. FreeDOS shows a warning and tries
> to ignore the problem, too, but somehow crashes.
>
> Partition Status Mbytes Description Usage Start Cyl End Cyl
> 1 20 16 Hidden FAT16 0% 0 1
> 3 7 A 27980 NTFS 98% 16 3582
> C: 4 6 494 FAT16 2% 3584 3646
> start/end cyl are > 1023
>
> WARNING: partition Pri: 4 FS 06 has CHS:3584-0-1 not 1023-254-63
> WARNING: partition Pri: 4 FS 06 has CHS:3546-254-63, not 1023-254-63
> 3646, I assume?
>
> WARNING: partition Pri: 4 FS 06 is not LBA
>
> Please run FDISK to correct this - using LBA to access partition
> start 3584-0-1, end 3646-254-63
> C:HD1, Pri [ 4], CHS: 3584-0-1, start=28113 MB, size=494 MB
>
> Those messages are far too verbose if you ask me! It would have been
> enough to show only:
> Partition should be marked as LBA, use FDISK to correct this:
> start 3584-0-1, end 3646-254-63
> C:HD1, Pri [ 4], CHS: 3584-0-1, start=28113 MB, size=494 MB
>
> This would already contain all required information (you can
> add, optionally, the overall drive geometry to the
> start 3584-0-1, end 3646-254-63
> line).
>
>
>
> Would be nice if Jeremy could reduce the error message verbosity here :-)
>
> PS: This is NOT a smoking gun. Your partition table is wrong,
> but in a "mild" way, which WinXP fixes silently and which FreeDOS
> complains about. Nothing caused by FDISK, though.
>
> ("fixes" as in "assumes the right value" - WinXP does not fix the data
> on disk. Actually MS FDISK is SO "caring" / crazy that if you create a
> FAT16 partition but format it with a FAT32 filesystem, their FDISK will
> pretend that the partition table would show the correct FAT32 value...)
>
> Eric
>
>
>
> ---
> 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=7477&alloc_id=16492&op=click
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
000 33fc 8ec0 8ed8 bec0 7c00 00bf b906 0100
020 a5f3 2eea 0006 4700 4741 203a 0090 0010
040 0001 7c00 17bf
060 b406 bb0e 0007 058a 903c 0774 cd57 5f10
100 eb47 bfee 061d 3d80 7500 b45f cd02 a916
120 000f 5674 c033 d88e c08e bebe b97d 0004
140 3c80 7480 830a 10c6 f6e2 32b0 bbe9 b200
160 b480 bb41 55aa 13cd 5b72 fb81 aa55 5575
200 26bf 8b06 084c 0d89 4c8b 890a 024d 42b4
220 1ebe bb06 0003 5650 b253 cd80 7313 5b30
240 585e 754b b0f1 e931 0080 1bbb b801 1000
260 d88e c08e 03b9 5100 80ba b900 0002 02b4
300 2ab0 cd90 7313 5946 ede2 31b0 5ceb 5b90
320 585e 27eb b290 8a80 0174 4c8b bb02 0003
340 5153 bb52 7c00 01b8 cd02 7313 5a0b 5b59
360 754b b0ed eb31 9033 595a 815b fe3e 557d
400 74aa b005 eb34 9023 00ea 007c b800 1000
420 c08e 8126 1c3e 4701 7541 260d 3e83 011e
440 7547 ea05 0120 1000 33b0 07bb b400 cd0e
460 eb10 56fe 6170 7472 7469 6f69 206e 6174
500 6c62 0065 7245 6f72 2072 6f6c 6461 6e69
520 2067 706f 7265 7461 6e69 2067 7973 7473
540 6d65 4d00 7369 6973 676e 6f20 6570 6172
560 6974 676e 7320 7379 6574 006d
600
*
660 2c00 6344 3800 0100
700 0001 fede 063f 003f b708 0001 0080
720 0701 fe07 b747 0001 b178 01d4 fe00
740 fe0c 68bf 01d6 f3fd 000e fe00
760 fe05 5cbc 01e5 f644 02c2 aa55
0001000
000 fcfa c031
Re: [Freedos-user] re: FDISK Corruption - possible smoking gun
The original post I sent was the output of FDISK from
booting Beta9SR1. The first time, no complaints.
Current fixed disk drive: 1 (TC: 3648 TH: 254 TS: 63)
Partition Status Mbytes Description Usage Start Cyl End Cyl
1 20 16 Hidden FAT16 0% 0 1
3 7 A 27980 NTFS 98% 16 3582
C: 4 6 494 FAT16 2% 3584 3646
-- Original message -- > > Hi (your last mail to the -user list was in html, oops), > FreeDOS is right to complain here: There is an official > partition type for FAT16 LBA, but you have a partition > which is marked as FAT16 CHS while at the same time reaching > beyond the 1024 cylinders that CHS can reach! WinXP seems > to just ignore the problem. FreeDOS shows a warning and tries > to ignore the problem, too, but somehow crashes. > > Partition Status Mbytes Description Usage Start Cyl End Cyl > 1 20 16 Hidden FAT16 0% 0 1 > 3 7 A 27980 NTFS 98% 16 3582 > C: 4 6 494 FAT16 2% 3584 3646 > start/end cyl are > 1023 > > WARNING: partition Pri: 4 FS 06 has CHS:3584-0-1 not 1023-254-63 > WARNING: partition Pri: 4 FS 06 has CHS:3546-254-6
3, not 1023-254-63 > 3646, I assume? > > WARNING: partition Pri: 4 FS 06 is not LBA > > Please run FDISK to correct this - using LBA to access partition > start 3584-0-1, end 3646-254-63 > C:HD1, Pri [ 4], CHS: 3584-0-1, start=28113 MB, size=494 MB > > Those messages are far too verbose if you ask me! It would have been > enough to show only: > Partition should be marked as LBA, use FDISK to correct this: > start 3584-0-1, end 3646-254-63 > C:HD1, Pri [ 4], CHS: 3584-0-1, start=28113 MB, size=494 MB > > This would already contain all required information (you can > add, optionally, the overall drive geometry to the > start 3584-0-1, end 3646-254-63 > line). > > > > Would be nice if Jeremy could reduce the error message verbosity here :-) > > PS: This is NOT a smoking gun. Your partition table is wrong, >
; but in a "mild" way, which WinXP fixes silently and which FreeDOS > complains about. Nothing caused by FDISK, though. > > ("fixes" as in "assumes the right value" - WinXP does not fix the data > on disk. Actually MS FDISK is SO "caring" / crazy that if you create a > FAT16 partition but format it with a FAT32 filesystem, their FDISK will > pretend that the partition table would show the correct FAT32 value...) > > Eric > > > > --- > 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=7477&alloc_id=16492&op=click > ___ > Freedos-user mailing list
> Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] FDISK Corruption - possible smoking gun
Hello, all: OK, I walked up to this laptop and ran FreeDOS Beta9SR1 from CD. I did all kinds of fdisk /info /tech and ran it interactively several times. All appeared normal. Current fixed disk drive: 1 (TC: 3648 TH: 254 TS: 63) Partition Status Mbytes Description Usage Start Cyl End Cyl 1 20 16 Hidden FAT16 0% 0 1 3 7 A 27980 NTFS 98% 16 3582 C: 4 6 494 FAT16 2% 3584 3646 Then, I booted WindowsXP. Still normal. Then, I booted my bootable CD with the development kernel. FreeDOS kernel version 1.1.35w (Build 2035w -UNSTABLE, Jul 10 2005) WARNING: partition Pri: 4 FS 06 has CHS:3584-0-1 not 1023-254-63 WARNING: partition Pri: 4 FS 06 has CHS:3546-254-63, not 1023-254-63 WARNING: partition Pri: 4 FS 06 is not LBA Please run FDISK to correct this - using LBA to access partition start 3584-0-1, end 3646-254-63 C:HD1, Pri [ 4], CHS: 3584-0-1, start=28113 MB, size=494 MB Invalid Opcode... PANIC: MCD chain corrupted I then went back and attempted to reboot Beta9SR1: WARNING: Partion ID does not suggest LBA - part PRI: 4 FS 06 and it hung! FDISK /info /tech or interactively (Y for large disk support, option 4) appears to have changed my partition table. WindowsXP is still happy for the moment. chkdsk notes no errors on the FAT partition. Comments? Mark
Re: [Freedos-user] FreeDOS kicks some serious Ass!
Yeah, some people just don't like WindowsXP. It's hard to buy a new computer without it installed, though! > Hi Mark, > > > You can install FreeDOS on a new computer and have it dual-boot > > with Windows XP as well. This doesn't harm the WindowsXP > > installation at all and doesn't require re-installing > > WindowsXP. > > Hehe, I'm sure this is useful for some folks, but for me it would be > like sacrilege! > > -- > Gerry Hickman (London UK) > > > --- > 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=7477&alloc_id=16492&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=7477&alloc_id=16492&op=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?
Hi Kenneth: No, I am not sure, of course. I had something similar happen to me once as well. Fortunately, gpart fixed that one...but it did happen after I ran FDISK. I don't believe he HAD a problem except that NTFS4DOS didn't recognize the XP partition. Are there any FreeDOS tools that just DISPLAY the partition information? How about save and restore it? I know some of the Linux tools, but not DOS. Thanks! Mark > [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=7477&alloc_id=16492&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Can FDISK destroy partitions using the examine partitions option?
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. 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 --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and EMM386 - the solution!
Hi Bernd: They e-mailed me the patched version. I do not know if they have re-released it. And, yes, the only file that is really required is ntfs4dos.exe. Mark > Mark Bailey schreef: > > the boot floppy and received a patched version of NTFS4DOS > > and received the following e-mail: > > > > - > > > > I've played a little with FreeDOS and NOT using UMBPCI. I found that the > > extender we use in the standard package (DOS/32) doesn't fit together > > with EMM386 well. I changed the extender to CAUSEWAY and now I get 612KB > > lower memory free. > > Is the 'fixed' NTFS4DOS version you received also already downloadable > (in freeware version) from Datapol? > > Hope they make Causeway the default. > > Only NTFS4DOS.EXE is needed? Maybe they can do as other ramdrive progs > do: return the errorlevel for the driveletter assigned: [A=1..Z=26] > > Bernd > > > --- > 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=7477&alloc_id=16492&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Redirect output of VOL command?
Good day, all: I was trying to do something clever to replace my C program findtdsk. All findtdsk is look at disk volume labels and return an ERRORLEVEL if it finds a match. findtdsk is crashing an HP computer and I don't feel like trying to debug it long distance. In the MS-DOS world, this can be done with a batch script doing things like: VOL A: | find /c "MS_RAMDRIVE" | choice /c:01 /n Te FreeDOS VOL command seems to treat everything after VOL as the first argument. This gives a syntax error. So does VOL A: > temp.dat Is there any way around this? Is this a bug in VOL? Thanks for the wonderful support. Mark Bailey --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Is there a maximum partition size in the FreeDOS kernel?
Good day: Trying to do a DIR on an NTFS partition, one of my friends is getting the following error: Divide error, stack: FB3C 158E 0246 14CB 38C8 6AE5 158E 7939 38A4 What's the size limit on a partition for the FreeDOS kernel? I believe this was a 160GByte partition, but I'm checking to be sure. I don't have anything that big to test with! The large size seems like the first place to look. Thanks again for the great support. Mark --- 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=7477&alloc_id=16492&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] NTFS4DOS and FreeDOS - more information
Good evening: Thanks very much to Eric Auer and Michael Devore for all of the suggestions! The support has been OUTSTANDING! OK, I have learned a bit more. Apparently, NTFS4DOS is slightly smarter than the documentation would have me believe. I did some experiments with MS-DOS 6.22 and let the wizard create the floppy disk. It wrote just "NTFS4DOS" to autoexec.bat with something called vtmode.com. I removed that from autoexec.bat since I have NO IDEA what it is. So, I learned that you can just run NTFS4DOS from the command line, without any arguments, and it behaves pretty well and does what I need (maps the NTFS partition and it stays mapped until exiting). Under MS-DOS 6.22, newest version of UMBPCI: Conventional Memory640 138501 Upper 64 0 64 Under MS-DOS 6.22, EMM386.EXE (MS-DOS flavor) Conventional Memory640 226414 Upper 51 0 51 FreeDOS, development kernel, command.com, sys Newest HIMEM, Newest UMBPCI Conventional Memory639 141 498 Upper64 4 60 FreeDOS, development kernel, command.com, sys Newest HIMEM/EMM386 Conventional Memory639 384255 Upper64 4 60 Trying to use installhigh/loadhigh doesn't help and, in fact, crashes MS-DOS 6.22 (error messages from FreeDOS). There are argument differences in himem and emm386: MSDOS: (from Datapol's documentation) DEVICEHIGH=a:\HIMEM.SYS /NUMHANDLES=128 /TESTMEM:OFF /Q FreeDOS: DEViCEHIGH=a:\fdos\himem.exe MSDOS: (based on sheer guesswork) DEVICEHIGH=a:\emm386.exe noems FreeDOS: (based on suggestions) DEVICEHIGH=a:\fdos\emm386.exe x=test memcheck vds noems max=256M Does this spark any ideas? It looks like chasing another K of Upper memory won't help. It also looks like installhigh/loadhigh isn't the way to go. (Thanks to Eric Auer for suggesting that or I probably wouldn't have noticed the significance of that autoexec.bat file). Thanks again for the great support! I appreciate it a lot. Mark --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
Hi Michael: Ok, this fails with BOTH UMBPCI and EMM386 in my Emachines T1600 and on an HP Pavillion P4. It works with UMBPCI and not EMM386 on a Dell D600. I guess I need to try DOS=HIGH without UMB, but I'm beginning to think NTFS4DOS is busted. Next step I suppose is to try MSDOS 6.22, like the instructions say, with UMBPCI and EMM386 on the two of these machines do. I also purchased a license from Datapol and I'm asking their tech support about this. We'll see if it was worth $25.00! Thanks again for all of your help. I will keep you posted. Mark > At 04:14 PM 7/13/2005 -0400, Mark Bailey wrote: > > >Will try DOS=HIGH only. Thanks! Too bad UMBPCI doesn't > >work on all the computers. :-( > > Well, if DOS=HIGH doesn't do it, I may have to d/l NTFS4DOS myself, force > 64K UMB, and see if I get the same fragmentation. Something bizarre going > on with NTFS4DOS anyway, what with it eating 400K of memory in conventional > if can't load in upper memory of 58K space. > > > > > --- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by HP, > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
Hi Michael:
Thanks again for the help. That didn't change the symptoms at
all from just using NOEMS...still get the error from DOS/32A!
What does DOSDATA=UMB do? I am booting from a USB floppy
drive most of the time...occasionally from a CD with a 1.44MByte
floppy disk image. Development kernel, command.com, and
SYS command. New himem.exe/emm386.exe.
NTFS4DOS failed to load at all.
config.sys:
!LASTDRIVE=Z
!BUFFERS=20
!FILES=40
!DOS=HIGH,UMB
!DOSDATA=UMB
echo NTFS4DOS included by permission from datapol gmbh, germany
echo NTFS4DOS and this CD may only be used on "private computers"
echo and for "private uses"
echo See www.datapol.de/dpd.
echo Mark Bailey, [EMAIL PROTECTED], July 12, 2005 - Alpha 1.0
SHELL=a:\command.com a:\ /p
!MENUCOLOR=7,0
MENUDEFAULT=1,5
MENU 1 - Boot FreeDOS without NTFS4DOS
MENU 2 - Boot FreeDOS with NTFS4DOS
12?DEVICE=A:\FDOS\HIMEM.EXE
12?DEVICE=a:\fdos\emm386.exe x=test memcheck vds noems max=256M
2?installhigh=a:\datapol\ntfs4dos.exe a:\command.com a:\ /p
12?DEVICE=a:\fdos\tdsk.exe 4096
--
mem /f /x
Segment Size Name Type
--- -- -
0271 6512 DOS system data
0273 192FILES data area
0280 2528HIMEM device driver
031f 3344EMM386 device driver
03f1 384TDSKdevice driver
0409 48 free
040d 2992 COMMAND program
04c9 96 MEM environment
04d048240 MEM program
1098 583264 free
9f00 200704 reserved
d000 6368 DOS system data
d002 64DEVICE data area
d007 1904FILES data area
d07f 2288LASTDRV data area
d10f 2048STACKS data area
d18f 3312 CTMOUSE program
d25f28752 free
d96524416 free
df5c 2304 free
dfed 288 COMMAND environment
Testing XMS memory ...
INT 2F AX=4309 supported
XMS version 3.00 XMS driver version3.11
HMA state existsA20 line stateenabled
Free XMS memory 530183168 bytes
Largest free XMS block530183168 bytes
Free handles 68
Block Handle Size Locks
--- ---
0 18029379841
1 1812 41943040
2 18221054720
Free upper memory 55520 bytes
Largest upper block 28768 bytes
Memory TypeTotal Used Free
Conventional 636K19K 617K
Upper 64K10K54K
Reserved 324K 324K 0K
Extended (XMS)522,936K 5,179K 517,757K
Total memory 523,960K 5,532K 518,428K
Total under 1 MB 700K29K 671K
Largest executable program size 617K (631,520 bytes)
Largest free upper memory block28K ( 28,768 bytes)
FreeDOS is resident in the high memory area.
> At 01:31 PM 7/12/2005 -0400, Mark wrote:
>
> >OK, here is the config.sys file I used with emm386. Note
> >that including NOEMS on the command line causes the
> >installhigh to FAIL with:
> >DOS/32A fatal (1002): DOS reported insufficient memory
>
> Well, the problem is here. You need the NOEMS option to free up that upper
> memory to get NTFS4DOS into it. NTFS4DOS fails to load into the upper
> memory after NOEMS and complains about it with a cryptic message from the
> extender. This even though 64K UMB is available, same as with
> UMBPCI. NTFS4DOS also using a horrible amount of conventional memory
> beyond the 64K that's in upper memory when it does work, which makes me
> think it has a bug.
>
> Ah! Just remembered a factoid. DOS/32A is one of those extenders that
> fails if too much VCPI memory is available. Try this: Add NOEMS option
> AND add the option MAX=256M too. That will limit VCPI memory below the
> trouble-spot with it. Give us a MEM /F /X report with the NOEMS and
> MAX=256M options in place.
>
>
>
>
> ---
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
> core and dual graphics technology at this free one hour event hosted by HP,
> AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
---
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July
Re: [Freedos-user] FreeDOS kicks some serious Ass!
Hi Johnson: My attempts have been very successful. The FreeDOS installer has problems if the WindowsXP partition is FAT32...it insists on writing a boot sector to C: no matter what. Just don't use the installer and SYS the disk manually and copy files over. The procedure I wrote up is a bit MS-DOS centric, but works very well. The computer I am typing this on triple boots (actually many more) WindowsXP, DOS, and Linux. Mark > On Mon, 11 Jul 2005 09:03:58 -0400, you wrote: > > Hi Mark, > > >You can install FreeDOS on a new computer and have it dual-boot > >with Windows XP as well. This doesn't harm the WindowsXP > >installation at all and doesn't require re-installing > >WindowsXP. You just put FreeDOS on a trivial amount > >of disk space at the end of the drive. > > My experience is failure. > > WinXP check the bootsector, it must be nothing or Win9x FAT identical, > otherwise after copying the file in text GUI screen and reboot, it > won't put XP's boot sector into the hard disk ... I got a non-bootable > disk prompt until update the bootsector to Win9x > > >I worked out a detailed procedure for doing this and would > >welcome comments. It uses free tools that the Linux guys > >use for dual booting. > > > >See www.k1ea.com/hints > >Dual-boot "Real" DOS on Windows XP > >for a detailed procedure, though a bit MSDOS centric. The > >keys are shrinking the NTFS partition to make room for > >DOS, formatting a FAT32 partition, and configuring the > >dual boot. > > Thanks for your effort. > I'll try your way. > > > Rgds, > Johnson. > > > --- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by HP, > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and UMBPCI.SYS?!?!
Hi Michael: Thanks. I took that straight out of the documentation. I need to check that boot disk and make sure I caught that. Could have been the problem. And, I do know better! :-) Mark > At 11:08 PM 7/10/2005 +, Mark Bailey wrote: > > >SWITCHES=/F > >DOS=HIGH,UMB > >DEVICEHIGH=a:\HIMEM.SYS /NUMHANDLES=128 /TESTMEM:OFF /Q > >DEVICEHIGH=A:\UMBPCI.SYS > > This is a strange example since DEVICEHIGH simply won't work (because it > can't) before upper memory is actually available. That won't occur until a > upper memory driver such as UMBPCI or EMM386 is loaded. I don't see how > either DEVICEHIGH listed would do other than load to conventional memory. > > > > > --- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by HP, > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] NTFS4DOS and UMBPCI.SYS?!?!
Help again! The documentation with NTFS4DOS uses UMBPCI.SYS instead of EMM386 to support loading the driver high. Can I use EMM386 or must I use UMBPCI? If I must use UMBPCI, what version should I use and where should I get it? :-) Thanks again. The config.sys example from the NTFS4DOS documentation is: SWITCHES=/F DOS=HIGH,UMB DEVICEHIGH=a:\HIMEM.SYS /NUMHANDLES=128 /TESTMEM:OFF /Q DEVICEHIGH=A:\UMBPCI.SYS BUFFERS=11,0 FILES=60 LASTDRIVE=Z FCBS=1,0 STACKS=0,0 SET CMDLINE= installhigh=a:\ntfs4dos.exe /r4 /lC A:\COMMAND.COM /K A:\autoexec.bat /E:1280 /P Mark Bailey --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] How to build a boot diskette for NTFS4DOS?
Hi All: OK, I'm confused. I want to try to get NTFS4DOS working from a bootable CD and loaded into high memory (using DEVICEHIGH). My first attempt was a failure and resulted in an "out of memory" error. I forget the exact message. I sent an e-mail to the list asking if anyone has done this, but didn't get any responses. :-( There have been lots of e-mails about debugging problems with loading programs (and drivers I suppose) high and various options to EMM386 like MEMCHECK which I intend to try. I need to put a complete FreeDOS environment on the floppy. I think I need the newest versions of EMM386 and HIMEM.SYS to be on the safe side. Do I need a new kernel or can I use the "stock" one? (I mean the one from Beta9SR1 (either the installation CD or the ODIN distribution). I can get a reasonable config.sys/autoexec.bat from my hard disk installation, since the ones on ODIN are not useful. Other than the new EMM386 and HIMEM, and possibly a new kernel, should I update anything else (command.com? FORMAT, SYS, something else...)? Thanks. I know FreeDOS hasn't done a stable release yet, but it really is an amazing achievement and very useable. And, it is the only one of the DOS variants I've found that's explicitely redistributeable. I appreciate all the hard work that has gone into FreeDOS. Mark Bailey --- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Writing to NTFS filesystems
Hello, all: In many cases, it is a LOT easier just to shrink the Windows XP NTFS partition a bit and create a FAT32 partition for sharing files between Windows XP and DOS. You can even make this FAT32 partition bootable and install FreeDOS if you want. Partition Magic used to be able to do this, but doesn't work on the NTFS partitions I've tried in the last year or so. I think it may be related to XP SP2. YMMV. The open source qtparted program does this easily enough. You can boot it from the system rescue cd, www.sysresccd.org and do the repartitioning. For more information, you can see http://k1ea.com/hints/DOS%20dual%20boot%20version%201.0.pdf The recently released NTFS4DOS driver also allows write access to NTFS partitions and does work with FreeDOS as well. Mark Bailey > Hi, > > Kenneth J. Davis escribió: > > > For applications which are best run from pure DOS, but the user has > > only NTFS (and Windows), and the max data stored is known ahead of > > time, a possible solution involves creating the file ahead of time (in > > Windows) and then in DOS either using a special driver to treat the > > file as a virtual drive or in the application specially supporting > > it. The file itself could be an app specific format (where a Windows > > program/GUI reads it and displays the information to/interacts with > > the user) or simply a disk image so a program like VFD makes it a > > virtual drive to Windows as well. Although not currently supported, > > it should even be possible to boot FreeDOS (possibly from the same > > disk image data stored to) from the NTFS partition. I am aware of one > > company that used an approach similar to this (where the user > > interacted with a Windows program, and the computer rebooted into DOS > > to run the tests, and then back into Windows for processing/displaying > > the results). > > Doesn't PowerQuest do this in their PartitionMagic when you want to do > something critical to the %systemdrive%? > > Aitor > > > > --- > 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 --- 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
Re: [Freedos-user] Dual booting Linux and FreeDOS
Hi Tom: You can see www.k1ea.com/hints Dual-boot "Real" DOS on Windows XP by Mark Bailey, KD4D for detailed instructions on how to configure GAG (a boot loader) to dual boot Windows XP and MS-DOS. To extend this to Linux (all of my machines actually triple boot various DOS flavors, Windows XP, and various Linux flavors), you need to install GRUB or LILO in the /root partition of the Linux installation. DO NOT install GRUB or LILO in the MBR of the disk...that's where GAG lives. Most of the Linux installers I've used lately offer that as an option. Otherwise, that's something like /dev/sda3 instead of /dev/sda (or hd(0,3) instead of hd(0,0)). I'm probably remembering the GRUB syntax wrong... :-) GAG is much easier to deal with. It will boot FreeDOS just fine. The only "glitch" is that the default FreeDOS installer insists on installing the basic boot files to "C:". If your multi-boot machine has something else on what FreeDOS thinks is C:, you have to manually do a "SYS" to the other drive and manually install FreeDOS there. Let me know if you have any questions. I suspect GRUB can be forced to do this, but GAG is much easier to configure. See gag.sourceforge.net. The machine I am typing on now has MS-DOS, FreeDOS, Windows XP, Debian sarge, and simplyMEPIS (If I recall correctly...:-)) Mark Bailey > Is it possible to have a dual boot system (Linux and FreeDOS) using grub or > grub4dos? From what I've seen from searching the web, a lot of people are > having trouble with this kind of setup. Has there been any progress on this > front? I really don't want to use a boot floppy if I don't have to, and I'd > rather not have MSDOS on my computer as explained in the "GRUB for DOS > How-To" that was posted on 2004-12-28. It was mentioned in that post that > the DOS based GRUB will not run with all FreeDOS kernels. I assume that this > means that some FreeDOS kernels will. Any ideas which ones will work? > > Also, emulation from within Linux with DOSemu or BOCHS is not an option for > me for I want to use FreeDOS to run a machine controller program (TurboCNC) > and that program requires realtime access to the computer. > > Thanks, > Tom Murray > > > > > --- > 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=6595&alloc_id=14396&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=6595&alloc_id=14396&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Dual booting Linux and FreeDOS
Good day: I don't know if it will boot FreeBSD, but I use the GAG boot loader to triple boot all of my machines...Linux, Windows XP, and various flavors of DOS. I find it much easier to deal with than LILO or GRUB. When I install the Linux OS, I install Lilo or Grub in the MBR of the /root partition instead of the hard disk. GAG will not directly boot Linux, so you need the boot loader in the /root partition. Works very well for me...I have four machines triple booting (or more). See gag.sourceforge.net for more information. Good luck! Mark Bailey > I have had little problem "dual-booting" FreeDOS and Linux. I used the > quotes because I usually boot four or more OS's on a given PC. It is > easiest to start with a floppy boot image, tweak it until it works as > you want it to, and then install to the HDD. I have just been learn- > ing that grub does not yet seem to be able to boot FreeBSD with the > new ufs2 file system, even though it is supposed to. It works fine > with ufs1. > Ken Martwick > > On Sun, Apr 10, 2005 at 11:11:02AM -0400, Thomas Murray wrote: > > Is it possible to have a dual boot system (Linux and FreeDOS) using grub or > > grub4dos? From what I've seen from searching the web, a lot of people are > > having trouble with this kind of setup. Has there been any progress on this > > front? I really don't want to use a boot floppy if I don't have to, and I'd > > rather not have MSDOS on my computer as explained in the "GRUB for DOS > > How-To" that was posted on 2004-12-28. It was mentioned in that post that > > the DOS based GRUB will not run with all FreeDOS kernels. I assume that > > this means that some FreeDOS kernels will. Any ideas which ones will work? > > > > Also, emulation from within Linux with DOSemu or BOCHS is not an option for > > me for I want to use FreeDOS to run a machine controller program (TurboCNC) > > and that program requires realtime access to the computer. > > > > Thanks, > > Tom Murray > > > > > > > > > > --- > > 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=6595&alloc_id=14396&op=click > > ___ > > Freedos-user mailing list > > Freedos-user@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/freedos-user > > > > --- > 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=6595&alloc_id=14396&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=6595&alloc_id=14396&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Determining RAM Disk drive letter using TDSK
Good day, all:
I got tired of struggling with drive letters and TDSK. I have written
a short C program which scans volume names for drives
C: through Z: (A: and B: were prompting for floppy insertions). By
default, it looks for the name "TURBODSK" from TDSK. However,
it accepts an argument of a name to look for...for example
findtdsk FDOS_BETA9
This program returns the drive letter in the DOS ERRORLEVEL and
prints the volume found to stderr.
I have also included a batch file to print out the drive letter.
I based this on a public domain example and release it into the
public domain. I built it under Windows using Open Watcom.
I could easily modify this to have the "turbodat" behavior and
create a file. However, the ERRORLEVEL return fits my requirements
better.
If anyone needs an executable, I can send it to you.
Mark Bailey
The C source file is:
/*
**
** findtdsk.c - finds the first FREEDOS TDSK RAM DRIVE (label TURBODSK)
**by scanning all drive letters from A: to Z:
**
** takes an optional argument, VOLNAME, which is the name of a disk volume to
** search for
**
** Returns the number corresponding to the disk with the correct volume name
** (MSDOS ERRORLEVEL: 0=A, 1=B, ... , 25=Z
**
** Released into the Public Domain
** Mark Bailey 21 March 2005
**
** Based on GETVOL.C from Bob Stout
** GETVOL.C - Retrieve a disk volume label
** (proof you don't need FCBs to do it!)
**
** public domain demo by Bob Stout
*/
#include
#include
#include
#include
#include
#include
#if defined(__ZTC__)
#pragma ZTC align 1
#else /* MSC/QC/WATCOM/METAWARE */
#pragma pack(1)
#endif
#define SUCCESS 0
char *getvol(char drive)
{
char search[] = "A:\\*.*";
static struct find_t ff;
*search = drive;
if (SUCCESS == _dos_findfirst(search, _A_VOLID, &ff))
{
if (8 < strlen(ff.name))/* Eliminate period */
strcpy(&ff.name[8], &ff.name[9]);
return ff.name;
}
else return NULL;
}
int main(int argc, char *argv[])
{
char *label;
char drive;
int i;
char *volname;
if (strcmp(argv[1],"/?") == 0)
{
puts("\aUsage: FINDTDSK [VOLNAME]\n"
"Where VOLNAME is an optional volume name to search for\n"
"The default VOLNAME is TURBODSK"
);
return -1;
}
else if (argv[1] != NULL)
volname = argv[1];
else
volname = "TURBODSK";
/*
*Do not check drives A and B
*/
for (i=2;i<26;i++)
{
drive = (char) (i+(int) 'A');
label = getvol(drive);
if (strcmp(volname,label)==0)
{
fprintf(stderr,"Disk %c has label %s\n",drive,label);
return (i);
}
}
return -1;
}
and a simple batch test file is:
echo off
findtdsk
if %ERRORLEVEL%==-1 echo "Not found"
if %ERRORLEVEL%==0 echo "A:"
if %ERRORLEVEL%==1 echo "B:"
if %ERRORLEVEL%==2 echo "C:"
if %ERRORLEVEL%==3 echo "D:"
if %ERRORLEVEL%==4 echo "E:"
if %ERRORLEVEL%==5 echo "F:"
if %ERRORLEVEL%==6 echo "G:"
if %ERRORLEVEL%==7 echo "H:"
if %ERRORLEVEL%==8 echo "I:"
if %ERRORLEVEL%==9 echo "J:"
if %ERRORLEVEL%==10 echo "K:"
if %ERRORLEVEL%==11 echo "L:"
if %ERRORLEVEL%==12 echo "M:"
if %ERRORLEVEL%==13 echo "N:"
if %ERRORLEVEL%==14 echo "O:"
if %ERRORLEVEL%==15 echo "P:"
if %ERRORLEVEL%==16 echo "Q:"
if %ERRORLEVEL%==17 echo "R:"
if %ERRORLEVEL%==18 echo "S:"
if %ERRORLEVEL%==29 echo "T:"
if %ERRORLEVEL%==20 echo "U:"
if %ERRORLEVEL%==21 echo "V:"
if %ERRORLEVEL%==22 echo "W:"
if %ERRORLEVEL%==23 echo "X:"
if %ERRORLEVEL%==24 echo "Y:"
if %ERRORLEVEL%==25 echo "Z:"
echo on
---
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=6595&alloc_id=14396&op=click
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Re: FreeDOS command.com documentation?
Hi Eric: Thanks! Great support. Wrong shell for the if (...) else (...) thing. Oh, well... Thanks again. Will try "vol d:>test" without the space. Thanks, Eric! Mark > > Hi, > > > 1. The "VOL" command built into command.com appears to > > output to stderr instead of stdout. > > No, but you have to do e.g. > VOL d:>somefile.txt > because > VOL d: >somefile.txt > is rejected. Looks like FreeCOM command.com is 1. too picky > and 2. does not strip spaces before the < > | signs. Should be FIXED. > > > 2. The MS-DOS syntax > > if condition ( > > ... > > ) > > gives a syntax error. Where is the behavior of "if" in command.com > > documented? > > You cannot do IF with () in MS-DOS. Maybe you can in WinNT, with the > cmd.* shell, but you cannot do it with command.com of MS DOS. > To get more information, do: > IF /? > at the prompt. To get a list of all commands in FreeCOM, by the way, do > ? > at the prompt. Further help is available by starting help (htmlhelp) > and reading the "batch file commands" section. > > There is some homepage, too: > http://freedos.sourceforge.net/freecom/FreeCOM.html > If you want to download a new version as suggested by > http://freedos.sourceforge.net/freecom/FreeCOM.html#-download-http > then you should NOT use the files directly in the > http://freedos.sourceforge.net/freecom/packages/ directory - those are OLD. > Instead, use e.g.: http://freedos.sourceforge.net/freecom/packages/082pl3/ > or alternatively: > http://freedos.sourceforge.net/freecom/packages/TESTING/com082pl3ak/ > > Somebody should really move the old versions to subdirectories on that > server :-(. > > Eric > > > > --- > 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=6595&alloc_id=14396&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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=6595&alloc_id=14396&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] FreeDOS command.com documentation?
Hello, all: I've been fiddling with an MS-DOS script to find out what drive letter is assigned to a ram drive, trying to get it to work with tdsk and FreeDOS. I've run into two differences that suprised me. 1. The "VOL" command built into command.com appears to output to stderr instead of stdout. So, piping the output, redirecting it to a file, etc., does not work. The external "VOL" command does output to stdout. This seems odd... 2. The MS-DOS syntax if condition ( ... ) gives a syntax error. Where is the behavior of "if" in command.com documented? I've seen one example script that seemed to use a "+" to seperate multiple commands in an if statement. Again, where is the behavior and syntax documented? I want to do this booting from a CD, so it appears I CAN'T use a pipe (|) since that appears to need a file on the boot device. I may have to break down and use something other than tdsk so I can get the drive letter... Thanks! I appreciate the great support I get for FreeDOS. Mark Bailey --- 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=6595&alloc_id=14396&op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FreeDOS boot flop -- ramdrive question
Hi Charlie: If you are trying to do what I am doing, the "difficult" part is finding the drive letter for the RAM disk. Here is a batch file I rigged up which will find the drive letter for any volume label...I forget the volume label tdisk assigns, but you can create one under FreeDOS and use the VOL command to check. Microsoft's utility uses "MS-RAMDRIVE." This finds a disk labelled DOS71. finddisk.bat - @Echo Off If %1'==' %0 C D E F G H I J K M N O P Q R S T U V W X Y Z Set RAMD= :Loop If %1'==' GOTO:End Vol %1: | Find "DOS71" > NUL If ErrorLevel 1 ( Shift Goto:Loop ) Set RAMD=%1 echo Found it: %RAMD%. :End --- This is based on something I found on the web. I had to simplify the one I found until I could understand it. I have attached the original document. Hope this helps. Mark > I know a studious kid who likes cds from the school > library better than the ones she gets for xmas. I > think she will like some of the old DOS games and > programs, so I am making a customized boot floppy for > her 10th birthday. I uploaded a generic version to my > FreeDOS shrine at: > www.geocities.com/wilkes_charlie/dosbox.htm > Click on the picture at the top of the page if you > want to download it. > Here is my question -- I am using microsoft utilities > from the win98 emergency disk to make a ram drive and > set it in the path. Is there a non-ms way to do it, > e.g., something that works with tdsk? > > Charlie > > > > > __ > Do you Yahoo!? > Take Yahoo! Mail with you! Get it on your mobile phone. > http://mobile.yahoo.com/maildemo > > > --- > 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=6595&alloc_id=14396&op=click > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user FINDRAMD.BAT.pdf Description: Adobe PDF document
Re: [Freedos-user] remastering cd iso under Linux?
Good day: You do not HAVE to use the SYSLINUX loader. I've been successful using the El Torito standard (with 1.44 or 2.88 MByte) boot sectors on CD's. The trick is getting a proper floppy disk image file. I did it this way because I've also been fiddling with MS-DOS boot CD's and haven't played with ISOLINUX for those yet. These CD images can be created from the boot floppy image file using mkisofs -b imagefile.img -c catalog ... I got the 2.88MByte boot disk image I'm using from www.fdos.org/bootdisks. I mounted the image file (using a program called VFD on Windows XP), configured it the way I wanted it, and then used it to build an ISO file for a bootable CD. I'm actually building these on Windows XP, but the basic process is the same. You can put a CD-ROM driver in config.sys and access the rest of the CD as a seperate drive letter. The computer basically acts like it was booted from a floppy drive and the floppy disk image ends up mapped as A:, not C: (which is where the boot device is if you use the ISOLINUX boot loader). No special drivers are required at all...it's just like booting from a floppy. You don't even need a CD-ROM driver unless you want to access more than 2.88 MBytes! :-) You don't need eltorito.sys or anything else that you would not need for booting from a floppy disk. No ISOLINUX, no ISOLINUX.CFG... Hope this helps. Mark > Michael schreef: > > > I have a CD ISO image I keep of useful free software programs for > > Windows. I was wanting to use the spare space on the discs to make a > > FreeDOS (and maybe Memtest) rescue disc. I've downloaded the FreedOS > > CD ISO. Do I just copy this ISO to a directory and copy the files from > > my other ISO into that directory? I'm working under Linux here. Is > > there anything special I need to do when remaking the ISO in order to > > make disc bootable into FreeDOS? Any tips would be appreciated. Thanks. > > Nothing difficult. However, FreeDOS cdrom *is* a bootable cdrom, and > like Linux distributions, uses ISOLINUX bootloader for the installation > cdrom. > You can use MKISOFS under Linux, and point to isolinux/isolinux.bin as > bootloader. > > layout is basically this: > AUTORUN.INF (root of cd, optional) > FREEDOS > ISOLINUX > and then your other programs > > You'll first have to unpack the ISO (or mount it, then copy it to a > writable directory) before adding your other programs and remastering. > > Bernd > > > --- > 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 --- 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] Installing FreeDOS on E:?
Hi Michael: Thank you VERY MUCH for this information. I will do some more experiments to try to narrow this down. What I was seeing was things like "del/s" freezing the computer before completing. Perhaps the disk was somehow corrupted. Or, maybe it was the wrong data in the boot sector (from the SYS command) or maybe something else. The applications I am trying to run are actually pretty good torture tests, with a lot of direct access to serial and parallel ports and critical timing requirements. Your information helps a great deal in where to look! Thanks again. Mark > At 02:43 AM 2/1/2005 +, Mark wrote: > > >I just tried running some applications from a USB stick booting > >FreeDOS. It didn't work very well...the USB stick got > >slightly corrupted. I have seen similar problems today with > >MS-DOS without SMARTDRV, so some research is in order! > > USB boot corruption would not specifically be a FreeDOS issue. Nowadays I > often boot FreeDOS and test applications all on a USB stick showing as huge > A: drive, under various memory manager configurations. A few tests hammer > the USB drive extensively without problems (my main remaining wish there is > for better throughput, as it can get very draggy, reminding more of a > floppy than hard disk in extreme cases). > > > > > --- > 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 --- 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] Installing FreeDOS on E:?
Hi Arkady: Ok, the BIOS provides support for DOS to recognize the partitions. This doesn't work on anything like all BIOS's, but it does seem to work on a lot of newer ones. I appreciate the clarification... I'm definitely still learning about how PC's boot. It is NOT true that C: is always a bootable partition. C: may not contain a boot sector and may not be the active partition. On at least one of my computers, a logical partition gets a drive letter under DOS. I'm not sure if I could make it C:, but it sure shows up as D:! I bet if I removed the FAT primary partition, it would show as C:. You can illustrate this by booting from a floppy if there is a FAT partition around. I just tried running some applications from a USB stick booting FreeDOS. It didn't work very well...the USB stick got slightly corrupted. I have seen similar problems today with MS-DOS without SMARTDRV, so some research is in order! You can set the "hidden" property using any number of Linux-based tools...I was using qtParted. Some boot loaders allow hiding partitions as well. This allows booting DOS from a primary partition which isn't the first one on the disk, I believe. Thanks for all the help! I'd love to be able to boot FreeDOS from a CD and run from a USB stick. I've got that working now with MS-DOS, so there is hope... :-) Mark > Hi! > > 27-ñÎ×-2005 23:16 [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote to > freedos-user@lists.sourceforge.net: > > kn> between Linux and Windows. The BIOS maps both of > kn> these drives (as C: and D:) when I boot the CD. > > BIOS doesn't maps anything, this does OS. And disk C: always assigned > to bootable primary partition. > > kn> Apparently, it isn't possible even to set the "hidden" > kn> flag on a logical partition, and setting the "hidden" > kn> flag on the primary partition doesn't seem to hide it anyway. > > How (in which program) you set "hidden"? (Note: unless you change ID > code in partition table (from FATxx to something else), DOS always will > recognize partition.) > > > > > --- > 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 --- 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] Installing FreeDOS on E:?
Hi Aitor: I'm not positive, but I don't THINK GAG will recognize a USB device unless the BIOS recognizes it. If you try this, please let me know what you find out. I use GAG on all of my machines...much easier to configure than GRUB. Mark > Hi there, > > Sorry about the slight offtopic, but... > > [EMAIL PROTECTED] escribió: > > > > >I'm using a boot loader called "GAG" to multiboot all of my computers. > >The laptop I'm using has FreeDOS, Windows XP, and Linux installed > >now with the GAG boot loader in the MBR. C: is the FreeDOS > >installation permanately on the laptop. It was MS-DOS last week... > > > > > Now that you have experience with that, is GAG able to boot any OS from > a partition on a USB device of any kind? > I am thinking of a great deal of possibilities with my IDE/ATA=>USB > adapter provided that the target OS is capable of understanding that > it is being booted from such device... (I don't know if any of the > Windows would be able to do that). > > > > > > >>> > >>> > >>> > >>> > >>Congratulations on getting USB stick bootable. How did you make it > >>visible as E: in DOS ? > >> > >> > > > >This is done automatically by the BIOS on at least two of my new > >computers. The USB stick gets a drive letter. One of the > >computers will only boot from it if it is a real floppy drive, the > >other offers the option to boot from USB Mass Storage. DOS > >doesn't know that it isn't a second hard drive. When it boots, > >DOS sees the USB stick as C:. No DOS USB drivers are required. > > > > > Sounds like bad news. Few available BIOSes seem to provide such a > support for USB, at least that I know of > > Aitor > > > --- > 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 --- 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
[Freedos-user] Creating custom bootable DOS CD's under Windows XP
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 floppy drive makes it a bit easier, but is not required. This uses several free programs: VFD (Virtual Floppy Disk), which simulates a floppy disk drive as A: or B: (either 1.44 MBytes or 2.88MBytes), mkboot which allows copying boot sectors, and mkisofs, which creates the ISO file. This is currently written for MSDOS and is still crude...it installs the system files and boot sector. I haven't added copying the other files but using this you get an A:\> prompt from MS-DOS. The same general technique will work with FreeDOS. Any knowledgeable DOS user can easily extend this. I like doing this from Windows XP because I can download stuff off the net and use the Windows GUI to create the CD image. 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 --- 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] Installing FreeDOS on E:?
Hi Bernd: Oh, I forgot to mention that the "SYS" command takes care of copying kernel.sys and command.com. Basically, if I copy the ODIN directory into something sensible and do a few tweaks of autoexec.bat and config.sys, then the USB stick boots and provides a good FreeDOS environment. My reason for doing this is to support ham radio applications. I want to make the procedure for installing it as easy as I can for a novice user who doesn't know much (if anything) about DOS. If you want a copy of the detailed installation for MS-DOS (which requires manually copying files to the USB stick), let me know. I hope to have it updated for FreeDOS soon. Mark > [EMAIL PROTECTED] schreef: > > >The FreeDOS installer appears to absolutely insist > >on writing a boot sector and some other stuff > >to C: even if you request an installation to > >something like E:\fdos. > > > > > Yes, sorry. Alternatives are welcome, but I need to guarantee that a > bootsector is written in order to get a bootable system. > Maybe I'll build in some kind of 'cheat-code' like Knoppix has, to alter > behaviour of FreeDOS a bit. > Is it doable to simply unplug the harddisk? Disconnect POWER and/or IDE > cable. > > >I can do a "SYS E:" and get the USB stick to boot. I > >can copy the ODIN directory from the CD and get > >a reasonably functional installation of FreeDOS. I > >suppose I could spend a few hours looking at the > >installation CD, figuring out where to find all of the > >configuration files, and manually copying them, but > >I was hoping for an easier way. Maybe I could dig out > >the SUBST command (doesn't seem to be in ODIN) > >and fake it out that way, or... > > > > > Congratulations on getting USB stick bootable. How did you make it > visible as E: in DOS ? > ODIN is more or less complete. > > http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/beta9sr1/r > eadme.txt > contains the config.sys/autoexec.bat. > Be sure to pick the one for harddisk (DEVICE=C:\...) > > >Any ideas? :-) > > > > > Any ideas on how to offer the SYS thing to the user? > I'm thinking about: > *if no previous OS, write bootsector anyway > *if previous OS, but target is C:\[freedosdirectory], then also write > bootsector > *if previous OS, and target not C:\ , ask where to write FreeDOS bootsector. > > Does your USB-drive become A: if you boot from it, or C: ? > if 'C:', then configuration files are simple: just move the \KERNEL.SYS > and \FDCONFIG.SYS from C: to the USBdrive > > Bernd > > > --- > 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 --- 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] Installing FreeDOS on E:?
Hi Bernd: Thanks for the reply. This has been fun. :-) Mark > [EMAIL PROTECTED] schreef: > > > Yes, sorry. Alternatives are welcome, but I need to guarantee that a > bootsector is written in order to get a bootable system. Yes, you do need to write a boot sector. How about the following: If the Freedos installation is to a directory on another BIOS device (not C:), then ask: "Write boot sector to C: and set up multiboot (recommended) or write boot sector to device whatever?" C: should be the default of course. Almost all Linux installers have a similar issue: they write a boot loader to the MBR of the hard disk by default with autodetection of other operating systems. However, most have an option to write the boot loader to the root partition instead of the MBR to allow installation without trashing the MBR and still allow booting the kernel by chaining the boot loader. Obviously, the user then has to set up his boot loader manually. I'm using a boot loader called "GAG" to multiboot all of my computers. The laptop I'm using has FreeDOS, Windows XP, and Linux installed now with the GAG boot loader in the MBR. C: is the FreeDOS installation permanately on the laptop. It was MS-DOS last week... Anyone wanting to install FreeDOS on a second hard drive (a good solution for desktops) will have the same problem. Your multibooting setup is clever, but obviously makes using the installer to install on something like a USB stick annoyingly difficult. > Is it doable to simply unplug the harddisk? Disconnect POWER and/or IDE > cable. Possibly, but I really don't want to take this laptop apart. Easy enough on a desktop, but this is really seems a simple installer change...just do a "SYS" to a different device and DON'T go through all the multiboot logic. When you create a bootable floppy from the CD, you don't overwrite the boot sector on C:. This case is very similar to that...it's a different device. > > > > > Congratulations on getting USB stick bootable. How did you make it > visible as E: in DOS ? This is done automatically by the BIOS on at least two of my new computers. The USB stick gets a drive letter. One of the computers will only boot from it if it is a real floppy drive, the other offers the option to boot from USB Mass Storage. DOS doesn't know that it isn't a second hard drive. When it boots, DOS sees the USB stick as C:. No DOS USB drivers are required. > > > Any ideas on how to offer the SYS thing to the user? > I'm thinking about: > *if no previous OS, write bootsector anyway > *if previous OS, but target is C:\[freedosdirectory], then also write > bootsector > *if previous OS, and target not C:\ , ask where to write FreeDOS bootsector. I don't think this is quite right...just because C: doesn't contain a previous operating system (for instance, my shared partition between Linux and Windows XP) does NOT mean I want it trashed by the installer. Also, if you don't write a boot sector to the new partition/device, it won't be bootable. That's the other problem...since you write the boot sector to C:, the USB device (at E: in my case) IS NOT bootable when the installer finishes. If the user is installing to a BIOS device other than C:, maybe just ask where he wants the boot sector and startup files. > > Does your USB-drive become A: if you boot from it, or C: ? C:. > if 'C:', then configuration files are simple: just move the \KERNEL.SYS > and \FDCONFIG.SYS from C: to the USBdrive No, I can't let you trash C:, so I can't get the files from there. Which ones on the CD are copied? I can't currently use the installer at all...I have to use "SYS" and then manually copy everything from the CD. > > Bernd > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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
[Freedos-user] Installing FreeDOS on E:?
Hello, all: I'm fiddling with booting FreeDOS from USB sticks. If a computer has the correct BIOS, I have this working well with MS-DOS and hope to get it running with FreeDOS. How can I get a "clean" and reasonably easy install of FreeDOS on a drive other than C:? The only machine I have which has BIOS support for booting USB memory devices has two FAT32 partitions...a primary one for multi-booting dos and a logical partition for sharing between Linux and Windows. The BIOS maps both of these drives (as C: and D:) when I boot the CD. Apparently, it isn't possible even to set the "hidden" flag on a logical partition, and setting the "hidden" flag on the primary partition doesn't seem to hide it anyway. The FreeDOS installer appears to absolutely insist on writing a boot sector and some other stuff to C: even if you request an installation to something like E:\fdos. I can do a "SYS E:" and get the USB stick to boot. I can copy the ODIN directory from the CD and get a reasonably functional installation of FreeDOS. I suppose I could spend a few hours looking at the installation CD, figuring out where to find all of the configuration files, and manually copying them, but I was hoping for an easier way. Maybe I could dig out the SUBST command (doesn't seem to be in ODIN) and fake it out that way, or... Any ideas? :-) Thanks in advance. Mark --- 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
[Freedos-user] Dual-booting FreeDOS and XP
Good morning, all: I have put together a detailed procedure for adding DOS dual-booting to a Windows XP computer without destroying the XP installation. This uses Linux tools, including qtparted (using parted/ntfsresize) to shrink the XP NTFS partition, add a FAT16 or FAT32 partition for DOS, and install MS-DOS or FreeDOS. The document is written more for MS-DOS, but mentions FreeDOS. The intended audience was people using Amateur Radio programs under DOS. I thought this might be useful for people who want to install FreeDOS on their new computers. You can look at the pdf at http://k1ea.com/hints/DOS%20dual%20boot%20version%201.0.pdf or http://www.trlog.com/DOS_dual_boot_20041207.pdf I would appreciate any suggestions or feedback. I have four computers booting XP, DOS (various variants), and Linux and I never had to re-install XP. The section on actually installing and configuring FreeDOS is weak, but the FreeDOS beta9sr1 installation works if the new DOS partition shows up as C:. It typically will if you are adding this capability to a new computer with XP pre-installed. I would like to improve this and add more information on configuring FreeDOS as well when I get some more time. Mark Bailey --- 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] Re: FreeDOS/DOS question
Hi: I've been fiddling with bootable DOS CD's. I've even created a mini "How-to" that creates a 2.88MByte floppy disk image, creates a bootable CD image, and boots it. You can add a CDROM driver if you like and use the rest of the CD. I'll be glad to send it to you if you like. It's a rough draft, but I think the process is well described. It can be used with DOS 6.22 or FreeDOS. Mark Bailey > Hi! > > 11-ñÎ×-2005 10:48 [EMAIL PROTECTED] (seraph00) wrote to > <[EMAIL PROTECTED]>: > > Note, this letter mirrored in freedos-user@ group. > > s> I have a rather large collection of games that are either DOS based or that > s> can run under DOS. I have a legal working copy of DOS 6.22 as well as of > s> the current release of FreeDOS. > s> The idea for the project is a simple one, but it is one that i'm not having > s> the best of luck figuring out how to do on my own. I'm looking for a way, > via > s> a CD, that I can boot a computer off the CD, and without having to install > s> anything, be able to load up a working form of DOS and some sort of > s> customizable menu to be able to look through a list of DOS games on the CD > s> and choose whichever one the user would like to play. > > There is already exists bootable CDs with DOS - for example, take a > look at Beta9sr1 from www.freedos.org. You may make similar bootable > distribution and modify its configuration files and contents, as you like. > (Don't forget: if some program tries to write something - configs or save > games - to disk, it will not work from CD). > > I myself have no experience in creating bootable CDs, you may ask > authot of Beta9 distribution, Bernd Blaauw. You may ask him through > [EMAIL PROTECTED] maillist. > > > > > --- > 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 --- 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] Floppy image > 2.88Meg
Hello, all: You can use "Virtual Floppy Drive" or some other software emulator to make 2.88MByte floppy images without a drive. Works fine and gives twice as much room on a bootable CD (unless you can afford the memory for a CD driver...) http://chitchat.at.infoseek.co.jp/vmware/vfd.html Mark > On Mon, 20 Dec 2004 08:23:40 +0300 (MSK), you wrote: > > Hi Arkady, > > > After 1.44, there was introduced one more format - 2.88. Its was not > >very widespread, but supported by most (modern) chipsets. > > I know, just don't understand what he want to ask. > > 2.88MB need a 2.88MB drive which can't be found anywhere now. > > I've a LS120 but I need to re-install and test under FreeDOS, a years > ago I've tried to boot FreeDOS but failed. > > > Rgds, > Johnson. > > > > --- > 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://productguide.itmanagersjournal.com/ > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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://productguide.itmanagersjournal.com/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Fix for Borland Turbo Pascal Bug?
Hi: Thanks for the information. However, MS-DOS 4.10. (no GUI) fixes this. Apparently, so does DR DOS/OpenDOS. So, it is possible to "fix" the Borland bug in DOS. I didn't even install the Windows GUI for this test, just a few basic MS-DOS files from Windows 98SE. Bernd Blaauw suggested a development kernel. "Mark, you might want to try a development kernel, as I believe someone changed something which made things work again." I'll try that. The Borland application is not open source and I didn't write it...I may have to look at the patch tool, though, and see if it works as well. I'd like to switch to FreeDOS, but this one application is the only reason I'm using DOS at all... :-) Mark > Hi! > > 30-îÏÑ-2004 19:04 [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote to > [EMAIL PROTECTED]: > > kn> I've been bitten by an apparent bug in Turbo Pascal running on > kn> newer computers. Here is the only FreeDOS reference I can > kn> This apparently also fails on MS-DOS 6.22 but DOES NOT fail on the > kn> version of MS-DOS that ships with Windows 98SE (4.10.). > > If you mean "runned under GUI", then this may be explained as slowdown > of DOS boxes (Windows kernel eats some time for itself). > > kn> Does anyone know what this bug is > > This bug is in CRT unit: Borlands programmers implement delay() in such > way, that it loops given count of iteration for each request millisecond. > For this, when program starts, CRT units measures how much of iterations > performed during millisecond. Trouble is that on faster computers there is > too much of iterations and in next calculations result is division by zero > (which in TP called "Runtime error 200"). > > kn> and whether it could be fixed in FreeDOS? > > There is some ways, how to fix bug in TP library itself and how to fix > already compiled programs. And this not depends from OS. For example, take a > look at: > > http://fjf.gnu.de/newdelay.pas > http://www.brain.uni-freiburg.de/~klaus/pascal/runerr200/newdelay.pas > http://www.brain.uni-freiburg.de/~klaus/pascal/runerr200/bp7patch.zip > ftp://garbo.uwasa.fi/pc/turbopas/rdelay10.zip > > __O\_/_\_/O__ > TP6BUGS7.LST - Version 7 of TP 6.0 bug list > Duncan Murdoch > [EMAIL PROTECTED] (Internet address) > DJ Murdoch at 1:249/99.5. (Fidonet) > _ > O/~\ /~\O > __O\_/_\_/O__ > BP7BUGS2.LST - Version 2 of BP 7.0 bug list > Duncan Murdoch > [EMAIL PROTECTED] (Internet address) > DJ Murdoch at 1:249/99.5. (Fidonet) > _ > O/~\ /~\O > > Also, for fixing programs, compiled by TP/BP, I very recommend TPPATCH, > written by Andreas Bauer (unfortunately, don't > know its URL). > > > > > --- > 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://productguide.itmanagersjournal.com/ > ___ > Freedos-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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://productguide.itmanagersjournal.com/ ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to install FreeDOS to D:?
Hi Bernd: Thanks again. "Obviously" :-) I intend > *boot the other partition, and let it become C: On this machine, that isn't even on the first hard disk. My boot loader will swap them and make the specific partition active. However, when I boot from CD, the MBR boot loader is bypassed. Then, when FreeDOS comes up, it sees the "wrong" C:. If I hide all of the primary partitions on the first hard drive, I'm not quite sure what the BIOS will do. But, since it maps the second drive primary FAT32 partition now, I guess it would become C:. I tend to distrust "fdisk" programs on 80 Gig hard drives, but I know the newer ones will handle it. Or, I can use one of the Linux tools to hide the partitions, then unhide them. Ugh...I believe I mentioned that before! Also, I know folks who are installing DOS to USB sticks to be able to boot it on laptop computers. In this case, the boot sector MUST be written to the USB stick. Somehow, it rarely seems to be C:. Again, this works fine with MSDOS and I could hack my way around it for FreeDOS, but... Mark > [EMAIL PROTECTED] schreef: > > >I'd like to install FreeDOS manually, copying the files to > >D:\fdos\bin and doing a "SYS D:" to get around this problem. How can > >I easily get the \fdos\bin directory created without also writing a > >bootsector to C:? > > > > > That is not possible, because we want to guarantee that the system boots. > If C: already contains an operating system, we'll now create a proper > dualboot system. > The config.sys is also written to be put on C:, with references to your D: > > If you put the files on another partition than C:, we don't know what > you're intending: > *boot FreeDOS from C:, but run programs from D: > *boot the other partition, and let it become C: > > I can only recommend to use a tool (I hope our FDISK allows it) to set > the correct primary partition active before running the FreeDOS installer. > If you wait another day, you can try the updated FreeDOS distro, as I'm > releasing that today. > > SYS D: should still be possible, but SYS C: has also been done, though. > Can you describe a bit more about why you consider this a problem? Then > I might try to work around it in a future release. > > Bernd > > > --- > 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://productguide.itmanagersjournal.com/ > ___ > Freedos-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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://productguide.itmanagersjournal.com/ ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] How to install FreeDOS to D:?
Hi Bernd: Oh, it's possible. I could manually extract the files I want from the bootable CD and do the COPY and SYS commands. I just want an easier way to get the \fdos\bin tree. Unless the FreeDOS "SYS" command is broken and always accesses C:? That would be ugly...I suppose I'd have to manually copy the boot sector. Your installer breaks my existing MS-DOS installation every time I run it. It's a great option to allow most of the files to live in an extended partition, though! :-) My problem is that these ARE NOT dual boot machines. I routinely boot many different OS's, including different versions of DOS. I really want FreeDOS confined ONLY to it's partition. I'll use another bootloader to chain to that partition and hide other partitions if necessary. I can do this with MS-DOS easily (I do it all the time). How do I do the same thing with FreeDOS? :-) Hide the partitions before I run the installer? Ugh... :-) Thanks for your prompt response! Mark > [EMAIL PROTECTED] schreef: > > >I'd like to install FreeDOS manually, copying the files to > >D:\fdos\bin and doing a "SYS D:" to get around this problem. How can > >I easily get the \fdos\bin directory created without also writing a > >bootsector to C:? > > > > > That is not possible, because we want to guarantee that the system boots. > If C: already contains an operating system, we'll now create a proper > dualboot system. > The config.sys is also written to be put on C:, with references to your D: > > If you put the files on another partition than C:, we don't know what > you're intending: > *boot FreeDOS from C:, but run programs from D: > *boot the other partition, and let it become C: > > I can only recommend to use a tool (I hope our FDISK allows it) to set > the correct primary partition active before running the FreeDOS installer. > If you wait another day, you can try the updated FreeDOS distro, as I'm > releasing that today. > > SYS D: should still be possible, but SYS C: has also been done, though. > Can you describe a bit more about why you consider this a problem? Then > I might try to work around it in a future release. > > Bernd > > > --- > 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://productguide.itmanagersjournal.com/ > ___ > Freedos-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/freedos-user --- 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://productguide.itmanagersjournal.com/ ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Re: Fix for Borland Turbo Pascal Bug?
Hello, again: I forgot to mention that apparently DR. DOS/OpenDOS have also "fixed" this problem. I will test with those as well, but I'd rather use FreeDOS. Mark > Hello, all: > > I've been bitten by an apparent bug in Turbo Pascal running on > newer computers. Here is the only FreeDOS reference I can > find: > http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=Using_FreeDOS/303 > > This apparently also fails on MS-DOS 6.22 but DOES NOT fail on the > version of MS-DOS that ships with Windows 98SE (4.10.). > > Does anyone know what this bug is and whether it could be fixed in > FreeDOS? The program I'm running is the only reason I'm still > using DOS! :-) I'm going to try the Beta9 FreeDOS, but the > older version of FreeDOS would not run this program. > > Thanks very much for any help. I'd love to be able to switch to FreeDOS. > > Mark --- 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://productguide.itmanagersjournal.com/ ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Fix for Borland Turbo Pascal Bug?
Hello, all: I've been bitten by an apparent bug in Turbo Pascal running on newer computers. Here is the only FreeDOS reference I can find: http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=Using_FreeDOS/303 This apparently also fails on MS-DOS 6.22 but DOES NOT fail on the version of MS-DOS that ships with Windows 98SE (4.10.). Does anyone know what this bug is and whether it could be fixed in FreeDOS? The program I'm running is the only reason I'm still using DOS! :-) I'm going to try the Beta9 FreeDOS, but the older version of FreeDOS would not run this program. Thanks very much for any help. I'd love to be able to switch to FreeDOS. Mark --- 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://productguide.itmanagersjournal.com/ ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
