Re: [Freedos-user] Some driver updates
Thank you, it is in my to do list to try them it is just limited personal time - it takes lot of effort to revive retro systems and getting a working DOS is only part of the challenge. Sometimes newer software such as FreeDOS or Jack's drivers save a lot of time to get things working and the job done faster and smoother, allowing for more time to be spend for example looking for parts in friends' basements. Cheers, Dimitris On Sat, Nov 4, 2017 at 11:58 AM, wrote: > Hi! > > On 2017-11-04, 11:41, Dimitris Zilaskos wrote: > >> Hi, >> >> There some bad heated past definitely which hopefully will be cooled down >> by >> time but ultimately like I said, there is a number of dos era systems that >> people like myself may want to use with FreeDOS and Jack's drivers are an >> option >> to do that when available for use - in my case for example when the >> reported >> issues with the supplied memory managers were not likely to be resolved >> any time >> soon. So users such as myself may want to have as many options to get >> these old >> dos era beasts working available to them. I was particularly happy when I >> was >> able to use my systems with FreeDOS in ways I never had before and I >> received >> extensive help from the community especially Jack, Eric as well as others >> so >> this whole ordeal is holding some of my retro projects back. >> > > I too have a couple of old 486 systems and recently also two 286 laptops > (yeah!) but I wasn't yet able to install FreeDOS on them. The first reason > being that my first project, a desktop 486, doesn't have a CD-ROM drive > and, natually, no USB either. The only way to get FreeDOS on the HDD was to > place it into a different system (a P4) and install it there. The bad news: > this very HDD was too small for FreeDOS. So at that point I did give up, > mostly due to my real life job which doesn't give me enough spare time to > continue the project, at least for now. > > My question to you is: > Why not use real retro software on real retro systems? I plan to install > DR DOS 5.0, which I still have a legal copy of. I also plan to get > abandonware of that time, which will not be a problem for a private person. > Yes, it could be called "stealing", but it really is not, since those > programs are no longer sold. Abandonware is clealy not trying to ruin > businesses, but when there is no chance to give them money for it, then > there is no damage. And the spirit is specifically to preserve old > software, not to steal it. > > Memory managers like Quarterdeck EMM (QEMM) and 386MAX come to mind. They > *could* be available from abandonware sites, but I didn't check. > > It may be possible to use FreeDOS with those memory managers. If they do > their job properly, you should use them. > > Cheers, > A. > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Some driver updates
Hi, There some bad heated past definitely which hopefully will be cooled down by time but ultimately like I said, there is a number of dos era systems that people like myself may want to use with FreeDOS and Jack's drivers are an option to do that when available for use - in my case for example when the reported issues with the supplied memory managers were not likely to be resolved any time soon. So users such as myself may want to have as many options to get these old dos era beasts working available to them. I was particularly happy when I was able to use my systems with FreeDOS in ways I never had before and I received extensive help from the community especially Jack, Eric as well as others so this whole ordeal is holding some of my retro projects back. Cheers, Dimitris On Sat, Nov 4, 2017 at 6:58 AM, Rugxulo wrote: > Hi, > > On Fri, Nov 3, 2017 at 7:17 PM, Dimitris Zilaskos > wrote: > > > > the wishes of the owners of the respective intellectual property have to > be respected. > > Personal opinion does not invalidate the law, and a so-called license > is only valid if it doesn't contradict the system enforcing it. > > Just because a disgruntled developer is angry (unfairly, I might add) > doesn't give him the right to rescind pre-existing licenses or do > whatever irrational thing he wants. > > Can he legally go "closed source" based upon a whim? Sure, but that's > not what he did. > > He 100% directly blamed me for saying "the drivers don't work anymore" > (which I have screenshots to prove is true for the Mar-18-2015 > release, which is what he directly emailed me about, telling me to > mirror for FreeDOS, even though that was after he'd already explicitly > said he was "giving up on FleaDOS"). > > He even went so far as to try to pretend that his old releases were > legally "tainted" so that Jim Hall would get scared and delete them. > So the only reason we still have any old releases is due to > stubbornness against him. If he had his way, we wouldn't even have > that. He is VERY vengeful, and unfairly so. > > At this point I have (sadly, unproven) reason to suspect that "he" is > not who he says "he" is. Either that or someone else is intercepting > and pretending to be us. So I highly suspect that not all messages > from "him" were really written by one person. But that's probably > nothing new in such a hostile world. Anyways, if you want to be naive, > just call it extreme emotional distress, mental illness, or similar. > It's not rational behavior from a sane person. You cannot negotiate > with such a person, they either can't or flat out refuse to > understand. > > Some or all of his trivial personal details are probably bogus. Maybe > I'm too cynical and suspicious at this point, but it makes no sense. > For months he said he couldn't get on the mailing list, and then > magically he reappeared. But all he did is blame me, insult heavily, > and go closed source. Call *me* crazy, but freedos-user sounds like > the complete opposite place to do that! So yeah, the whole technical > "problem" that started this long ordeal was resolved but ignored in > lieu of bigger (psychological) problems. > > Sigh. I don't want to bring all this up, but some people (even > geniuses whom I respect, like Eric Auer) can't seem to let go. And > that's another thing I don't understand, but I don't want to get into > all of "that" either! Ugh. > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Some driver updates
Hi, Jack's drivers are required on a number of dos-era systems else FreeDOS will not even install/boot. Being unable to use FreeDOS is annoying but a working system is needed and the wishes of the owners of the respective intellectual property have to be respected. Cheers, Dimitris On Fri, Nov 3, 2017 at 4:27 PM, Ralf Quint wrote: > On 11/3/2017 7:19 AM, Tom Ehlert wrote: > > > > just as a tiny side note: > > > > I am only aware of 2 persons THAT CONSISTENTLY SHOUT. > > Jack and the american president. > > > +1 :-P > > Ralf > > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] dma crosse
From: Dimitris Zilaskos --===2004488960791693994== Content-Type: multipart/alternative; boundary=001a11402ebefae056053a86f6a3 --001a11402ebefae056053a86f6a3 Content-Type: text/plain; charset=UTF-8 Hi, I keep getting the error dma crosses 64k boundary when using tools like rawrite3 or hard drive manufacturers tools floppy creation software. I need to boot from Windows 98 bootdisk to get rid of it. Please let me know if there is a way to get rid of this problem under FreeDOS. Cheers, Dimitris --001a11402ebefae056053a86f6a3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi,I keep getting the error-adma crosses 64k boundary when using tools like rawrite3 or hard drive manufacturers tools floppy creation software. I need to boot from Windows 98 bootdisk to get rid of it.Please let me know if there is a way to get rid of this problem under FreeDOS.Cheers,Dimitris --001a11402ebefae056053a86f6a3-- --===2004488960791693994== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- --===2004488960791693994== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --===2004488960791693994==-- --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedo
From: Dimitris Zilaskos --===4049000903152666126== Content-Type: multipart/alternative; boundary=001a114004b64325ba053a605bd1 --001a114004b64325ba053a605bd1 Content-Type: text/plain; charset=UTF-8 Hi, Thank you for the advice. I tried FDIMPLES, seem to show everything installed, but for some reason p7zip is missing from its list. Best regards, Dimitris On Wed, Aug 17, 2016 at 12:25 AM, Jerome Shidel wrote: > If you run the installer in advanced mode, you can add them at > installation by using detailed package selection. > > You can switch the installer into Advanced mode at any point it is waiting > on user input. For example, the installer runs in Normal mode when you > boot. You continue through all the prompts until you reach the "BASE or > ALL/FULL" package selection. Press CTRL+C, then select "Switch to Advanced > mode" it will then return you back to the package set selection but now > "Detailed selections" will be available. > > If you run the installer from the command prompt, you can start it in > advanced mode by using "SETUP adv" > > There are many things the installer does (or tries to do) automatically in > Normal mode. But in Advanced mode, nearly all of those decisions are left > to the user. > > Also, if you use FDIMPLES (installed with FULL/ALL), you can browse > through and select packages to be installed. Similar to using some Linux > package browsing systems like Yast. FDIMPLES does not do networking at > present. So, you will need to have you CD inserted. > > Jerome > > On Aug 16, 2016, at 7:01 PM, Dimitris Zilaskos > wrote: > > Ok thanks. Would be awesome to have an option to get them installed. > > Cheers, > > Dimitris > > On Tue, Aug 16, 2016 at 5:52 PM, Jerome Shidel wrote: > >> Hello, >> >> > On Aug 16, 2016, at 11:38 AM, Dimitris Zilaskos >> wrote: >> > >> > Hi, >> > >> > I did a full freedos 1.2 installation but not all archivers were >> installed. While I got them from the CD eventually from the ARCHIVERS >> directory I was wondering if that is supposed to happen. >> > >> > Best regards, >> > >> > Dimitris >> >> Yes, for now. >> >> There is roughly 400mb in about 100 packages that are included on the 1.2 >> cd and large USB stick versions that are included but not installed. At >> present they are considered extra/bonus packages. >> >> Jerome >> >> >> -- >> ___ >> Freedos-user mailing list >> Freedos-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-user >> > > > -- > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > > > > -- > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > > --001a114004b64325ba053a605bd1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi,Thank you for the advice. I tried FDIMPLES, seem to show everything installed, but for some reason p7zip is missing from its list.Best regards,DimitrisOn Wed, Aug 17, 2016 at 12:25 AM, Jerome Shidel <mailto:jer...@shidel.net"; target="_blank">jer...@shidel.net> wrote:If you run the installer in advanced mode, you can add them at installation by using detailed package selection.You can switch the installer into Advanced mode at any point it is waiting on user input. For example, the installer runs in Normal mode when you boot. You continue through all the prompts until you reach the "BASE or ALL/FULL" package selection. Press CTRL+C, then select "Switch to Advanced mode" it will then return you back to the package set selection but now "Detailed selections" will be available.-aIf you run the installer from the command prompt, you can start it in advanced mode by using "SETUP adv"There are many things the installer does (or tries to do) automatically in Normal mode. But in Advanced mode, nearly all of those decisions are left to the user.Also, if you use FDIMPLES (installed with FULL/ALL), you can browse through and select packages to be installed. Similar to using some Linux package browsing systems like Yast. FDIMPLES does not do networking at
Re: [Freedos-user] freedo
From: Dimitris Zilaskos --===2905593142841686751== Content-Type: multipart/alternative; boundary=001a114b0aa08b4740053a6228e0 --001a114b0aa08b4740053a6228e0 Content-Type: text/plain; charset=UTF-8 Thank you for your replies. I think I must had the wrong cd inserted, because now I can see all the packages as expected. Sorry for the confusion! Cheers, Dimitris On Fri, Aug 19, 2016 at 1:36 AM, Rugxulo wrote: > Hi, > > On Thu, Aug 18, 2016 at 5:46 PM, Dimitris Zilaskos > wrote: > > > > Thank you for the advice. I tried FDIMPLES, seem to show everything > > installed, but for some reason p7zip is missing from its list. > > I don't really recommend p7zip for heavy use. For one thing, there is > no active (DOS) maintainer, and it's somewhat buggy because of that > (and the fact that it's really a very sloppy POSIX port that barely > works with DJGPP). I don't grok C++, so I wasn't much further help > regarding it. It does work, but it's far from perfect. > > If you just want to unpack .7z files, use 7zdec. But normally, as Jim > Hall always tells us, ZIP is preferred overall, so just use (old but > good) Info-Zip (zip / unzip). > > (Or you could run old standalone Win32 7za [sic] under HX. That worked > pretty well. Besides, the DJGPP build of p7zip doesn't have 7z [sic] > anyways ... although even that build [Win32] I did briefly get running > under HX). > > There's also upstream DJGPP builds of XZ, if you just can't live > without LZMA. And a billion other archivers (UHarc??). I honestly > haven't kept up in recent years (not sure why I ever bothered, I'm not > savvy enough to understand the details anyways). > > > -- > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > --001a114b0aa08b4740053a6228e0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thank you for your replies. I think I must had the wrong cd inserted, because now I can see all the packages as expected. Sorry for the confusion!Cheers,DimitrisOn Fri, Aug 19, 2016 at 1:36 AM, Rugxulo <mailto:rugx...@gmail.com"; target="_blank">rugx...@gmail.com> wrote:Hi, On Thu, Aug 18, 2016 at 5:46 PM, Dimitris Zilaskos <mailto:dimitr...@gmail.com";>dimitr...@gmail.com> wrote: > > Thank you for the advice. I tried FDIMPLES, seem to show everything > installed, but for some reason p7zip is missing from its list. I don't really recommend p7zip for heavy use. For one thing, there is no active (DOS) maintainer, and it's somewhat buggy because of that (and the fact that it's really a very sloppy POSIX port that barely works with DJGPP). I don't grok C++, so I wasn't much further help regarding it. It does work, but it's far from perfect. If you just want to unpack .7z files, use 7zdec. But normally, as Jim Hall always tells us, ZIP is preferred overall, so just use (old but good) Info-Zip (zip / unzip). (Or you could run old standalone Win32 7za [sic] under HX. That worked pretty well. Besides, the DJGPP build of p7zip doesn't have 7z [sic] anyways ... although even that build [Win32] I did briefly get running under HX). There's also upstream DJGPP builds of XZ, if you just can't live without LZMA. And a billion other archivers (UHarc??). I honestly haven't kept up in recent years (not sure why I ever bothered, I'm not savvy enough to understand the details anyways). - ___ Freedos-user mailing list mailto:Freedos-user@lists.sourceforge.net";>Freedos-user@lists.sourcef rge.net https://lists.sourceforge.net/lists/listinfo/freedos-user"; rel="noreferrer" target="_blank">https://lists.sourceforge.net/lists/listinfo/freedos-user --001a114b0aa08b4740053a6228e0-- --===2905593142841686751== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- --===2905593142841686751== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --===2905593142841686751==-- --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0
[Freedos-user] freedos 1.
From: Dimitris Zilaskos --===7160934022374945973== Content-Type: multipart/alternative; boundary=001a113f201cec7e0e053a3222e4 --001a113f201cec7e0e053a3222e4 Content-Type: text/plain; charset=UTF-8 Hi, I did a full freedos 1.2 installation but not all archivers were installed. While I got them from the CD eventually from the ARCHIVERS directory I was wondering if that is supposed to happen. Best regards, Dimitris --001a113f201cec7e0e053a3222e4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi,I did a full freedos 1.2 installation but not all archivers were installed. While I got them from the CD eventually from the ARCHIVERS directory I was wondering if that is supposed to happen.Best regards,Dimitris --001a113f201cec7e0e053a3222e4-- --===7160934022374945973== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- --===7160934022374945973== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --===7160934022374945973==-- --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedo
From: Dimitris Zilaskos --===6441216991813819129== Content-Type: multipart/alternative; boundary=001a114013c0e837f6053a385540 --001a114013c0e837f6053a385540 Content-Type: text/plain; charset=UTF-8 Ok thanks. Would be awesome to have an option to get them installed. Cheers, Dimitris On Tue, Aug 16, 2016 at 5:52 PM, Jerome Shidel wrote: > Hello, > > > On Aug 16, 2016, at 11:38 AM, Dimitris Zilaskos > wrote: > > > > Hi, > > > > I did a full freedos 1.2 installation but not all archivers were > installed. While I got them from the CD eventually from the ARCHIVERS > directory I was wondering if that is supposed to happen. > > > > Best regards, > > > > Dimitris > > Yes, for now. > > There is roughly 400mb in about 100 packages that are included on the 1.2 > cd and large USB stick versions that are included but not installed. At > present they are considered extra/bonus packages. > > Jerome > > > -- > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > --001a114013c0e837f6053a385540 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ok thanks. Would be awesome to have an option to get them installed.Cheers,DimitrisOn Tue, Aug 16, 2016 at 5:52 PM, Jerome Shidel <mailto:jer...@shidel.net"; target="_blank">jer...@shidel.net> wrote:Hello, > On Aug 16, 2016, at 11:38 AM, Dimitris Zilaskos <mailto:dimitr...@gmail.com";>dimitr...@gmail.com> wrote: > > Hi, > > I did a full freedos 1.2 installation but not all archivers were installed. While I got them from the CD eventually from the ARCHIVERS directory I was wondering if that is supposed to happen. > > Best regards, > > Dimitris Yes, for now. There is roughly 400mb in about 100 packages that are included on the 1.2 cd and large USB stick versions that are included but not installed. At present they are considered extra/bonus packages. Jerome - ___ Freedos-user mailing list mailto:Freedos-user@lists.sourceforge.net";>Freedos-user@lists.sourcef rge.net https://lists.sourceforge.net/lists/listinfo/freedos-user"; rel="noreferrer" target="_blank">https://lists.sourceforge.net/lists/listinfo/freedos-user --001a114013c0e837f6053a385540-- --===6441216991813819129== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- --===6441216991813819129== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --===6441216991813819129==-- --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Which
From: Dimitris Zilaskos --===6423063471355840179== Content-Type: multipart/alternative; boundary=001a114b0aa0a1dfff0539a74401 --001a114b0aa0a1dfff0539a74401 Content-Type: text/plain; charset=UTF-8 Hi, I had some more time to spend on this project today. I reinstalled Freedos on a 2 GB disk-on-module. Again after installation I had to do a sys from 2031 bootdisk and then copy kernel.sys to get a bootable freedos 1.2 system. I can use my CDROM connected to the IDE interface on the Sound Blaster card. So all is fine here apart from past 2031 bootdisks requiring the workaround to boot from hard drive. The issue I am facing now is that the mechanical drives I connected to the secondary IDE channel of my Vesa Local Bus controller are not detected. Windows 98 SE bootdisk does not detect them either, The BIOS of my system only supports 2 hard drives. Last time I had this setup working with Linux, so I will try to dig some old bootdisk to see if Linux can detect the secondary IDE hard drives. Is there anything I can try from FreeDOS? Best regards, Dimitris On Wed, Jul 20, 2016 at 11:31 PM, Dimitris Zilaskos wrote: > Hi Eric, > > I have tried the /FORCE:CHS and it did not help. > > Cheers, > > Dimitris > > On Wed, Jul 20, 2016 at 7:19 PM, Eric Auer wrote: > >> >> Hi Dimitris, >> >> > I retried sys c: from the 2031 bootdisk and it failed to boot, hanging >> at >> > Loading FreeDOS, hard drive working like mad, I rebooted with the same >> > floppy, did the same thing, and it booted. Tried again with sys 3.6e, >> > hang again, tried again with sys 2.6, was able to boot again. >> >> This is a bit confusing but it sounds like a problem with the way >> that our FAT32 boot sector uses LBA. So with the new SYS 3.6e, you >> should be able to boot with /FORCE:CHS (explicitly selecting the >> CHS FAT32 boot sector: SYS 2.6 does not even have a LBA version). >> >> This will probably work with various, including newer (and better) >> versions of the kernel.sys file: In earlier tests, you mentioned >> that using SYS CONFIG to require pure LBA or pure CHS mode from a >> kernel did not affect the ability of the kernel to use the drive. >> >> Regards, Eric >> >> >> >> >> -- >> What NetFlow Analyzer can do for you? Monitors network bandwidth and >> traffic >> patterns at an interface-level. Reveals which users, apps, and protocols >> are >> consuming the most bandwidth. Provides multi-vendor support for NetFlow, >> J-Flow, sFlow and other flows. Make informed decisions using capacity >> planning >> reports.http://sdm.link/zohodev2dev >> ___ >> Freedos-user mailing list >> Freedos-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-user >> > > --001a114b0aa0a1dfff0539a74401 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi,I had some more time to spend on this project today. I reinstalled Freedos on a 2 GB disk-on-module. Again after installation I had to do a sys from 2031 bootdisk and then copy kernel.sys to get a bootable freedos 1.2 system. I can use my CDROM connected to the IDE interface on the Sound Blaster card. So all is fine here apart from past 2031 bootdisks requiring the workaround to boot from hard drive.The issue I am facing now is that the mechanical drives I connected to the secondary IDE channel of my Vesa Local Bus controller are not detected. Windows 98 SE bootdisk does not detect them either, The BIOS of my system only supports 2 hard drives. Last time I had this setup working with Linux, so I will try to dig some old bootdisk to see if Linux can detect the secondary IDE hard drives. Is there anything I can try from FreeDOS?Best regards,DimitrisOn Wed, Jul 20, 2016 at 11:31 PM, Dimitris Zilaskos <mailto:dimitr...@gmail.com"; target="_blank">dimitr...@gmail.com> wrote:Hi Eric,I have tried the /FORCE:CHS and it did not help.-aCheers,Dimitris /div>On Wed, Jul 20, 2016 at 7:19 PM, Eric Auer <mailto:e.a...@jpberlin.de"; target="_blank">e.a...@jpberlin.de> wrote: Hi Dimitris, > I retried sys c: from the 2031 bootdisk and it failed to boot, hanging at > Loading FreeDOS, hard drive working like mad, I rebooted with the same > floppy, did the same thing, and it booted. Tried again with sys 3.6e, > hang again, tried again with sys 2.6, was able to boot again. This is a bit confusing but it sounds like a problem with the way that our FAT32 boot sector uses LBA. So with the new SYS 3.6e, you should be able to boot with /FORCE:CHS (explicitly selecting the CHS FA
Re: [Freedos-user] Which
From: Dimitris Zilaskos --===5997703658926392847== Content-Type: multipart/alternative; boundary=001a1141173ef8ad59053ad6c161 --001a1141173ef8ad59053ad6c161 Content-Type: text/plain; charset=UTF-8 Hi, After lots of testing and lots of help from Jack Ellis and Eric, I was able more or less to overcome the roadblocks: a) Gibberish after boot: use only JEMMEX, and/or replace HIMEMX with XMGR /T0 (or /B /T0 and then /T0 per documentation) b)Freedos 1.2 pre22 not booting after installation, requiring sys c: from 2031 bootdisks (sys 2.6) to workaround see next point c) Lack of BIOS support for secondary IDE I installed EZ-BIOS using the hard drive manufacturer's tools found at http://members.shaw.ca/rinocanada/hdutils.htm Though aimed to address BIOS drive size limitations, in my cases it added support for the secondary IDE, and removed the need for workaround after freedos installation failed to boot c)rawrite3/hard drive manufacturer's tools complaining about crossing 64K DMA barrier while wring to floppy: workaround 1 (only for rawrite3, fails for larger programs such as hard drive tools): load lowdma.sys early on in config.sys, then lh rawrite3 (slow) workaround 2 (for both): patched lowdma.sys from Eric that removed the requirement to use lh (also slow) workaround 3: boot from windows 98 bootdisk (considerably faster) d)after rawrite3/hard drive tools writing to disk, dir a: still slows the old files/directories this caused some confusion if the tools did the job right with the workarounds, but reboot proved they work. Windows 98 bootdisk does not suffer from this issue e)SB16 IDE CDROMs not being detected by UIDE/UDVD2 Probably I did something wrong the card jumpers or the cabling, as I failed to replicate the problem. Once it is configured to use the tertiary IDE channel, it worked fine. This is with a CT 2290 "plug-n-play" card that needs to be configured from software for sound related settings with the diagnose.exe tool - IDE IRQ and channel still need jumpers. I failed to get it to work with a similar CT2910 according to PCB, CT2291 according to the sticker SB16 card with a very similar but not identical layout, and with jumpers for everything. Perhaps the card IDE is problematic as sound works - I did not have time to test if Linux performs better (Windows bootdisk and creative IDE drivers also fail). f)UMC8672 dos driver support I found dos drivers for my VLB controller (PM-67B, UMC8672 based) at http://driverzone.com/drivers/umc/control/um8672.htm. Unfortunately they do not work - complain about UM8672 not being detected. Supposedly they would enable the secondary IDE channel. Perhaps they need the BIOS chip add on on the card judging from README talking about pressing F10 during boot and a BIOS style menu which I do not have. In any case, EZ-BIOS removed the need for such a driver. Thanks everyone for the help! Cheers, Dimitris On Tue, Aug 9, 2016 at 10:51 PM, TJ Edmister wrote: > On Tue, 09 Aug 2016 13:57:35 -0400, Dimitris Zilaskos > wrote: > > > The issue I am facing now is that the mechanical drives I connected to > > the > > secondary IDE channel of my Vesa Local Bus controller are not detected. > > Windows 98 SE bootdisk does not detect them either, The BIOS of my system > > only supports 2 hard drives. > > IIRC, if your motherboard BIOS only supports two drives, you could use a > controller card with its own onboard ROM for additional drives to be > recognized under DOS (or Win9x). Depending on what chipset the card uses, > there might also be a driver which can enable the second channel. > > Not sure if the various DMA DOS drivers would detect and add drives on the > second channel (in fact, I don't know if they work on ISA/VL IDE > controllers or if PCI is required) > > > > -- > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. http://sdm.link/zohodev2dev > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > --001a1141173ef8ad59053ad6c161 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi,After lots of testing and lots of help from Jack Ellis and Eric, I was able more or less to overcome the roadblocks:a) Gibberish after boot: use only JEMMEX, and/or replace HIMEMX with XMGR /T0 (or /B /T0 and then /T0 per documentation)b)Freedos 1.2 pre22 not booting after installation, requiring sys c: from 2031 bootdisks
Re: [Freedos-user] dma cr
From: Dimitris Zilaskos --===7567637663601894498== Content-Type: multipart/alternative; boundary=001a114013c0cba44c053ac0e9fc --001a114013c0cba44c053ac0e9fc Content-Type: text/plain; charset=UTF-8 Hi, Hi, Thank you for your reply. Hardware is a year 1995 486-DX4 100, hardly remarkable at its time. Cheers, Dimitris On Tue, Aug 23, 2016 at 6:28 PM, Tom Ehlert wrote: > > I keep getting the error dma crosses 64k boundary when using tools > > like rawrite3 or hard drive manufacturers tools floppy creation > > software. I need to boot from Windows 98 bootdisk to get rid of it. > > > Please let me know if there is a way to get rid of this problem under > FreeDOS. > > MSDOS redirects int 13 to an internal driver, detects DMA access crossing > a 64k boundary, > and avoids it. > > FreeDOS ddoes not do this; sorry. > > there was no need to do this so far; IMO rawrite3 could/should handle > this by itself. of course, software is usually only tested against > MSDOS, so there is little motivation to do so for rawrite3 > programmers. > > I'm still surprised this comes up today, and not 15 years ago. > do you have remarkable hardware? > > Tom > > > > -- > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > --001a114013c0cba44c053ac0e9fc Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi,Hi,Thank you for your reply. Hardware is a year 1995 486-DX4 100, hardly remarkable at its time.Cheers,DimitrisOn Tue, Aug 23, 2016 at 6:28 PM, Tom Ehlert <mailto:t...@drivesnapshot.de"; target="_blank">t...@drivesnapshot.de> wrote:> I keep getting the error-adma crosses 64k boundary when using tools > like rawrite3 or hard drive manufacturers tools floppy creation > software. I need to boot from Windows 98 bootdisk to get rid of it. > Please let me know if there is a way to get rid of this problem under FreeDOS. MSDOS redirects int 13 to an internal driver, detects DMA access crossing a 64k boundary, and avoids it. FreeDOS ddoes not do this; sorry. there was no need to do this so far; IMO rawrite3 could/should handle this by itself. of course, software is usually only tested against MSDOS, so there is little motivation to do so for rawrite3 programmers. I'm still surprised this comes up today, and not 15 years ago. do you have remarkable hardware? Tom - ___ Freedos-user mailing list mailto:Freedos-user@lists.sourceforge.net";>Freedos-user@lists.sourcef rge.net https://lists.sourceforge.net/lists/listinfo/freedos-user"; rel="noreferrer" target="_blank">https://lists.sourceforge.net/lists/listinfo/freedos-user --001a114013c0cba44c053ac0e9fc-- --===7567637663601894498== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- --===7567637663601894498== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user --===7567637663601894498==-- --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dma cr
From: Dimitris Zilaskos --===3972634112440227579== Content-Type: multipart/alternative; boundary=001a113f201c552d2b053ac43b1a --001a113f201c552d2b053ac43b1a Content-Type: text/plain; charset=UTF-8 Hi, rawrite1 also works. Problem is tools from maxtor/western digital/seagate etc appear to be based around some hard wired version of rawrite3, which prevents these tools from being able to create their bootdisks under freedos. Cheers, Dimitris On Tue, Aug 23, 2016 at 9:35 PM, Rugxulo wrote: > Hi, > > On Tue, Aug 23, 2016 at 12:28 PM, Tom Ehlert wrote: > >> > >> I keep getting the error dma crosses 64k boundary when using tools > >> like rawrite3 or hard drive manufacturers tools floppy creation > >> software. I need to boot from Windows 98 bootdisk to get rid of it. > > > > I'm still surprised this comes up today, and not 15 years ago. > > do you have remarkable hardware? > > Is it possible that different tools don't exhibit the same behavior / bug? > > So, just for comparison, there are various other tools to write floppy > images to physical disk: > > 1). FD diskcopy > http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/diskcopy/0.9/ > > 2). sfx14436 (stub) > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/ > distributions/tools/ > > 3). FreeBSD fdimage.exe > http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old- > releases/i386/4.8-RELEASE/4.8-RELEASE/tools/ > > 4). PLoP's diskimg > https://www.plop.at/en/dostools.html#diskimg.com > > > -- > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > --001a113f201c552d2b053ac43b1a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi,rawrite1 also works. Problem is tools from maxtor/western digital/seagate etc appear to be based around some hard wired version of rawrite3, which prevents these tools from being able to create their bootdisks under freedos.Cheers,DimitrisOn Tue, Aug 23, 2016 at 9:35 PM, Rugxulo <mailto:rugx...@gmail.com"; target="_blank">rugx...@gmail.com> wrote:Hi, On Tue, Aug 23, 2016 at 12:28 PM, Tom Ehlert <mailto:t...@drivesnapshot.de";>t...@drivesnapshot.de> wrote: >> >> I keep getting the error dma crosses 64k boundary when using tools >> like rawrite3 or hard drive manufacturers tools floppy creation >> software. I need to boot from Windows 98 bootdisk to get rid of it. > > I'm still surprised this comes up today, and not 15 years ago. > do you have remarkable hardware? Is it possible that different tools don't exhibit the same behavior / bug? So, just for comparison, there are various other tools to write floppy images to physical disk: 1). FD diskcopy http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/diskcopy/0.9/"; rel="noreferrer" target="_blank">http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/diskcopy/0.9/ 2). sfx14436 (stub) https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/too s/" rel="noreferrer" target="_blank">https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/tools/ 3). FreeBSD fdimage.exe http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/4.8-R LEASE/4.8-RELEASE/tools/" rel="noreferrer" target="_blank">http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-RELEASE/tools/ 4). PLoP's diskimg https://www.plop.at/en/dostools.html#diskimg.com"; rel="noreferrer" target="_blank">https://www.plop.at/en/dostools.html#diskimg.com - ___ Freedos-user mailing list mailto:Freedos-user@lists.sourceforge.net";>Freedos-user@lists.sourcef rge.net https://lists.sourceforge.net/lists/listinfo/freedos-user"; rel="noreferrer" target="_blank">https://lists.sourceforge.net/lists/listinfo/freedos-user --001a113f201c552d2b053ac43b1a-- --===3972634112440227579== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- --===3972634112440227579== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___ Freedos-user mailin
Re: [Freedos-user] Which freedos on 486
Hi, After lots of testing and lots of help from Jack Ellis and Eric, I was able more or less to overcome the roadblocks: a) Gibberish after boot: use only JEMMEX, and/or replace HIMEMX with XMGR /T0 (or /B /T0 and then /T0 per documentation) b)Freedos 1.2 pre22 not booting after installation, requiring sys c: from 2031 bootdisks (sys 2.6) to workaround see next point c) Lack of BIOS support for secondary IDE I installed EZ-BIOS using the hard drive manufacturer's tools found at http://members.shaw.ca/rinocanada/hdutils.htm Though aimed to address BIOS drive size limitations, in my cases it added support for the secondary IDE, and removed the need for workaround after freedos installation failed to boot c)rawrite3/hard drive manufacturer's tools complaining about crossing 64K DMA barrier while wring to floppy: workaround 1 (only for rawrite3, fails for larger programs such as hard drive tools): load lowdma.sys early on in config.sys, then lh rawrite3 (slow) workaround 2 (for both): patched lowdma.sys from Eric that removed the requirement to use lh (also slow) workaround 3: boot from windows 98 bootdisk (considerably faster) d)after rawrite3/hard drive tools writing to disk, dir a: still slows the old files/directories this caused some confusion if the tools did the job right with the workarounds, but reboot proved they work. Windows 98 bootdisk does not suffer from this issue e)SB16 IDE CDROMs not being detected by UIDE/UDVD2 Probably I did something wrong the card jumpers or the cabling, as I failed to replicate the problem. Once it is configured to use the tertiary IDE channel, it worked fine. This is with a CT 2290 "plug-n-play" card that needs to be configured from software for sound related settings with the diagnose.exe tool - IDE IRQ and channel still need jumpers. I failed to get it to work with a similar CT2910 according to PCB, CT2291 according to the sticker SB16 card with a very similar but not identical layout, and with jumpers for everything. Perhaps the card IDE is problematic as sound works - I did not have time to test if Linux performs better (Windows bootdisk and creative IDE drivers also fail). f)UMC8672 dos driver support I found dos drivers for my VLB controller (PM-67B, UMC8672 based) at http://driverzone.com/drivers/umc/control/um8672.htm. Unfortunately they do not work - complain about UM8672 not being detected. Supposedly they would enable the secondary IDE channel. Perhaps they need the BIOS chip add on on the card judging from README talking about pressing F10 during boot and a BIOS style menu which I do not have. In any case, EZ-BIOS removed the need for such a driver. Thanks everyone for the help! Cheers, Dimitris On Tue, Aug 9, 2016 at 10:51 PM, TJ Edmister wrote: > On Tue, 09 Aug 2016 13:57:35 -0400, Dimitris Zilaskos > wrote: > > > The issue I am facing now is that the mechanical drives I connected to > > the > > secondary IDE channel of my Vesa Local Bus controller are not detected. > > Windows 98 SE bootdisk does not detect them either, The BIOS of my system > > only supports 2 hard drives. > > IIRC, if your motherboard BIOS only supports two drives, you could use a > controller card with its own onboard ROM for additional drives to be > recognized under DOS (or Win9x). Depending on what chipset the card uses, > there might also be a driver which can enable the second channel. > > Not sure if the various DMA DOS drivers would detect and add drives on the > second channel (in fact, I don't know if they work on ISA/VL IDE > controllers or if PCI is required) > > > > -- > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. http://sdm.link/zohodev2dev > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] dma crosses 64k boundary error
Hi, Based on Eric's comments and with Jack's help, I was able to get rawrite3 to work under freedos by a) loading lowdma.sys in fdconfig.sys early durting boot b) LH rawrite3. Unfortunately that does not work with hard drive manufacturer's tools, they complain at LH about lack of RAM. Since they are executables around 1.44 MB I suspect they are just too big for LH to work with them. Cheers, Dimitris On Tue, Aug 23, 2016 at 10:56 PM, Dimitris Zilaskos wrote: > Hi, > > rawrite1 also works. Problem is tools from maxtor/western digital/seagate > etc appear to be based around some hard wired version of rawrite3, which > prevents these tools from being able to create their bootdisks under > freedos. > > Cheers, > > Dimitris > > On Tue, Aug 23, 2016 at 9:35 PM, Rugxulo wrote: > >> Hi, >> >> On Tue, Aug 23, 2016 at 12:28 PM, Tom Ehlert wrote: >> >> >> >> I keep getting the error dma crosses 64k boundary when using tools >> >> like rawrite3 or hard drive manufacturers tools floppy creation >> >> software. I need to boot from Windows 98 bootdisk to get rid of it. >> > >> > I'm still surprised this comes up today, and not 15 years ago. >> > do you have remarkable hardware? >> >> Is it possible that different tools don't exhibit the same behavior / bug? >> >> So, just for comparison, there are various other tools to write floppy >> images to physical disk: >> >> 1). FD diskcopy >> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/diskcopy/0.9/ >> >> 2). sfx14436 (stub) >> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dis >> tributions/tools/ >> >> 3). FreeBSD fdimage.exe >> http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-relea >> ses/i386/4.8-RELEASE/4.8-RELEASE/tools/ >> >> 4). PLoP's diskimg >> https://www.plop.at/en/dostools.html#diskimg.com >> >> >> -- >> ___ >> 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] dma crosses 64k boundary error
Hi, rawrite1 also works. Problem is tools from maxtor/western digital/seagate etc appear to be based around some hard wired version of rawrite3, which prevents these tools from being able to create their bootdisks under freedos. Cheers, Dimitris On Tue, Aug 23, 2016 at 9:35 PM, Rugxulo wrote: > Hi, > > On Tue, Aug 23, 2016 at 12:28 PM, Tom Ehlert wrote: > >> > >> I keep getting the error dma crosses 64k boundary when using tools > >> like rawrite3 or hard drive manufacturers tools floppy creation > >> software. I need to boot from Windows 98 bootdisk to get rid of it. > > > > I'm still surprised this comes up today, and not 15 years ago. > > do you have remarkable hardware? > > Is it possible that different tools don't exhibit the same behavior / bug? > > So, just for comparison, there are various other tools to write floppy > images to physical disk: > > 1). FD diskcopy > http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/diskcopy/0.9/ > > 2). sfx14436 (stub) > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/ > distributions/tools/ > > 3). FreeBSD fdimage.exe > http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old- > releases/i386/4.8-RELEASE/4.8-RELEASE/tools/ > > 4). PLoP's diskimg > https://www.plop.at/en/dostools.html#diskimg.com > > > -- > ___ > 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] dma crosses 64k boundary error
Hi, Hi, Thank you for your reply. Hardware is a year 1995 486-DX4 100, hardly remarkable at its time. Cheers, Dimitris On Tue, Aug 23, 2016 at 6:28 PM, Tom Ehlert wrote: > > I keep getting the error dma crosses 64k boundary when using tools > > like rawrite3 or hard drive manufacturers tools floppy creation > > software. I need to boot from Windows 98 bootdisk to get rid of it. > > > Please let me know if there is a way to get rid of this problem under > FreeDOS. > > MSDOS redirects int 13 to an internal driver, detects DMA access crossing > a 64k boundary, > and avoids it. > > FreeDOS ddoes not do this; sorry. > > there was no need to do this so far; IMO rawrite3 could/should handle > this by itself. of course, software is usually only tested against > MSDOS, so there is little motivation to do so for rawrite3 > programmers. > > I'm still surprised this comes up today, and not 15 years ago. > do you have remarkable hardware? > > Tom > > > > -- > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] dma crosses 64k boundary error
Hi, I keep getting the error dma crosses 64k boundary when using tools like rawrite3 or hard drive manufacturers tools floppy creation software. I need to boot from Windows 98 bootdisk to get rid of it. Please let me know if there is a way to get rid of this problem under FreeDOS. Cheers, Dimitris -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedos 1.2 archivers
Thank you for your replies. I think I must had the wrong cd inserted, because now I can see all the packages as expected. Sorry for the confusion! Cheers, Dimitris On Fri, Aug 19, 2016 at 1:36 AM, Rugxulo wrote: > Hi, > > On Thu, Aug 18, 2016 at 5:46 PM, Dimitris Zilaskos > wrote: > > > > Thank you for the advice. I tried FDIMPLES, seem to show everything > > installed, but for some reason p7zip is missing from its list. > > I don't really recommend p7zip for heavy use. For one thing, there is > no active (DOS) maintainer, and it's somewhat buggy because of that > (and the fact that it's really a very sloppy POSIX port that barely > works with DJGPP). I don't grok C++, so I wasn't much further help > regarding it. It does work, but it's far from perfect. > > If you just want to unpack .7z files, use 7zdec. But normally, as Jim > Hall always tells us, ZIP is preferred overall, so just use (old but > good) Info-Zip (zip / unzip). > > (Or you could run old standalone Win32 7za [sic] under HX. That worked > pretty well. Besides, the DJGPP build of p7zip doesn't have 7z [sic] > anyways ... although even that build [Win32] I did briefly get running > under HX). > > There's also upstream DJGPP builds of XZ, if you just can't live > without LZMA. And a billion other archivers (UHarc??). I honestly > haven't kept up in recent years (not sure why I ever bothered, I'm not > savvy enough to understand the details anyways). > > > -- > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedos 1.2 archivers
Hi, Thank you for the advice. I tried FDIMPLES, seem to show everything installed, but for some reason p7zip is missing from its list. Best regards, Dimitris On Wed, Aug 17, 2016 at 12:25 AM, Jerome Shidel wrote: > If you run the installer in advanced mode, you can add them at > installation by using detailed package selection. > > You can switch the installer into Advanced mode at any point it is waiting > on user input. For example, the installer runs in Normal mode when you > boot. You continue through all the prompts until you reach the "BASE or > ALL/FULL" package selection. Press CTRL+C, then select "Switch to Advanced > mode" it will then return you back to the package set selection but now > "Detailed selections" will be available. > > If you run the installer from the command prompt, you can start it in > advanced mode by using "SETUP adv" > > There are many things the installer does (or tries to do) automatically in > Normal mode. But in Advanced mode, nearly all of those decisions are left > to the user. > > Also, if you use FDIMPLES (installed with FULL/ALL), you can browse > through and select packages to be installed. Similar to using some Linux > package browsing systems like Yast. FDIMPLES does not do networking at > present. So, you will need to have you CD inserted. > > Jerome > > On Aug 16, 2016, at 7:01 PM, Dimitris Zilaskos > wrote: > > Ok thanks. Would be awesome to have an option to get them installed. > > Cheers, > > Dimitris > > On Tue, Aug 16, 2016 at 5:52 PM, Jerome Shidel wrote: > >> Hello, >> >> > On Aug 16, 2016, at 11:38 AM, Dimitris Zilaskos >> wrote: >> > >> > Hi, >> > >> > I did a full freedos 1.2 installation but not all archivers were >> installed. While I got them from the CD eventually from the ARCHIVERS >> directory I was wondering if that is supposed to happen. >> > >> > Best regards, >> > >> > Dimitris >> >> Yes, for now. >> >> There is roughly 400mb in about 100 packages that are included on the 1.2 >> cd and large USB stick versions that are included but not installed. At >> present they are considered extra/bonus packages. >> >> Jerome >> >> >> -- >> ___ >> Freedos-user mailing list >> Freedos-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-user >> > > > -- > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > > > > -- > > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > > -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] freedos 1.2 archivers
Ok thanks. Would be awesome to have an option to get them installed. Cheers, Dimitris On Tue, Aug 16, 2016 at 5:52 PM, Jerome Shidel wrote: > Hello, > > > On Aug 16, 2016, at 11:38 AM, Dimitris Zilaskos > wrote: > > > > Hi, > > > > I did a full freedos 1.2 installation but not all archivers were > installed. While I got them from the CD eventually from the ARCHIVERS > directory I was wondering if that is supposed to happen. > > > > Best regards, > > > > Dimitris > > Yes, for now. > > There is roughly 400mb in about 100 packages that are included on the 1.2 > cd and large USB stick versions that are included but not installed. At > present they are considered extra/bonus packages. > > Jerome > > > -- > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] freedos 1.2 archivers
Hi, I did a full freedos 1.2 installation but not all archivers were installed. While I got them from the CD eventually from the ARCHIVERS directory I was wondering if that is supposed to happen. Best regards, Dimitris -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Which freedos on 486
Hi, I had some more time to spend on this project today. I reinstalled Freedos on a 2 GB disk-on-module. Again after installation I had to do a sys from 2031 bootdisk and then copy kernel.sys to get a bootable freedos 1.2 system. I can use my CDROM connected to the IDE interface on the Sound Blaster card. So all is fine here apart from past 2031 bootdisks requiring the workaround to boot from hard drive. The issue I am facing now is that the mechanical drives I connected to the secondary IDE channel of my Vesa Local Bus controller are not detected. Windows 98 SE bootdisk does not detect them either, The BIOS of my system only supports 2 hard drives. Last time I had this setup working with Linux, so I will try to dig some old bootdisk to see if Linux can detect the secondary IDE hard drives. Is there anything I can try from FreeDOS? Best regards, Dimitris On Wed, Jul 20, 2016 at 11:31 PM, Dimitris Zilaskos wrote: > Hi Eric, > > I have tried the /FORCE:CHS and it did not help. > > Cheers, > > Dimitris > > On Wed, Jul 20, 2016 at 7:19 PM, Eric Auer wrote: > >> >> Hi Dimitris, >> >> > I retried sys c: from the 2031 bootdisk and it failed to boot, hanging >> at >> > Loading FreeDOS, hard drive working like mad, I rebooted with the same >> > floppy, did the same thing, and it booted. Tried again with sys 3.6e, >> > hang again, tried again with sys 2.6, was able to boot again. >> >> This is a bit confusing but it sounds like a problem with the way >> that our FAT32 boot sector uses LBA. So with the new SYS 3.6e, you >> should be able to boot with /FORCE:CHS (explicitly selecting the >> CHS FAT32 boot sector: SYS 2.6 does not even have a LBA version). >> >> This will probably work with various, including newer (and better) >> versions of the kernel.sys file: In earlier tests, you mentioned >> that using SYS CONFIG to require pure LBA or pure CHS mode from a >> kernel did not affect the ability of the kernel to use the drive. >> >> Regards, Eric >> >> >> >> >> -- >> What NetFlow Analyzer can do for you? Monitors network bandwidth and >> traffic >> patterns at an interface-level. Reveals which users, apps, and protocols >> are >> consuming the most bandwidth. Provides multi-vendor support for NetFlow, >> J-Flow, sFlow and other flows. Make informed decisions using capacity >> planning >> reports.http://sdm.link/zohodev2dev >> ___ >> Freedos-user mailing list >> Freedos-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-user >> > > -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Which freedos on 486
Hi Eric, I have tried the /FORCE:CHS and it did not help. Cheers, Dimitris On Wed, Jul 20, 2016 at 7:19 PM, Eric Auer wrote: > > Hi Dimitris, > > > I retried sys c: from the 2031 bootdisk and it failed to boot, hanging at > > Loading FreeDOS, hard drive working like mad, I rebooted with the same > > floppy, did the same thing, and it booted. Tried again with sys 3.6e, > > hang again, tried again with sys 2.6, was able to boot again. > > This is a bit confusing but it sounds like a problem with the way > that our FAT32 boot sector uses LBA. So with the new SYS 3.6e, you > should be able to boot with /FORCE:CHS (explicitly selecting the > CHS FAT32 boot sector: SYS 2.6 does not even have a LBA version). > > This will probably work with various, including newer (and better) > versions of the kernel.sys file: In earlier tests, you mentioned > that using SYS CONFIG to require pure LBA or pure CHS mode from a > kernel did not affect the ability of the kernel to use the drive. > > Regards, Eric > > > > > -- > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > reports.http://sdm.link/zohodev2dev > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Which freedos on 486
Hi, So now I have only the master HDD on primary IDE connected and the floppy. It did not change anything. I was able to confirm the CHS/settings - BIOS has a menu called IDE HDD AUTO DETECTION. When all the jumpers etc are correct, it will detect the drive and offer 3 options - LBA, LARGE, NORMAL, each with different CHS settings but same size. Only LBA results in fdisk detecting the HDD and proceeding, other modes cause FreeDOS to spit error messages about non LBA partition upon boot, and fdisk does not detect the HDD at all. Cheers, Dimitris On Wed, Jul 20, 2016 at 10:39 PM, Jerome E. Shidel Jr. wrote: > > On Jul 20, 2016, at 5:23 PM, Dimitris Zilaskos > wrote: > > Hi, > > On Wed, Jul 20, 2016 at 9:50 PM, Jerome E. Shidel Jr. > wrote: > >> On Jul 20, 2016, at 12:56 PM, Dimitris Zilaskos >> wrote: >> […] >> >> Dimitris >> >> >> I have a few silly questions. >> >> You have verified the drive has the correct jumpers set? >> > > Correct, master / slave > > > :-) > > >> You are not trying to use cable select mode? >> > > Nope > > > :-) > > > >> >> You are using the correct position on the IDE cable? >> > > Yes > > > :-) > > >> You are plugged into the primary controller? >> > > Yes > > > :-) > > > >> >> Is the BIOS configuration for the drive being set manually or using >> "auto" mode? >> > > This is actually a good question. It is user mode which would qualify as > manually, but I can't remember if the values for CHS were actually entered > manually by copying them from the labels, or using the auto detect BIOS > feature. I do recall it look a lot of effort to figure this out, as any > mistake and the system would not detect the hdds or boot altogether. > >> >> You mentioned “tertiary” at one point. How many drives? How many >> controllers? >> > > The sound blaster card has one IDE port that currently has 2 CD-ROM drives > connected in master/slave setup > >> >> Is the drive partitioned as a single disk or multiple partitions? >> > > single partition > > :-) > > >> It is not inside an extended partition? >> > > No > > :-) > > > >> >> If there are any other drives, are they partitioned and formatted for DOS? >> > > Yes, the slave drive is an old windows98 system with a fat32 partition. > > I can simplify the setup - remove all CDROM drives and the slave hard > drive and leave only one hdd and the floppy to see if there is any change. > > > It probably won’t help. But, It wouldn’t hurt to try. > > > Cheers, > > Dimitris > > > Mostly, I wanted to verify you weren’t using cable select. I’ve seen it > work great and I’ve seen it cause weird issues. > There are some strange jumper settings on some drives. Most just > master/slave. But others that plus single or multiple, LBA or not… > Sometimes you just remove all the jumpers, sometimes you hunt around in > you desk for an hour because you need just one more. > Oh, IDE was some much fun. Especially, when adding extra cards and raids. > > Anyhow, I figured I might as well play “20 questions” and rule out some of > the simple but often overlooked items. > > Jerome > > > > > -- > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > reports.http://sdm.link/zohodev2dev > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > > -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Which freedos on 486
Hi, On Wed, Jul 20, 2016 at 7:56 PM, wrote: > On Jul 20, 2016 12:57 PM, "Dimitris Zilaskos" wrote: > > > > Hi > > > > > > > Since I now have a bootable C: drive, can't we just compare the working > MBR/boot sector with the non working one? > > > > Cheers, > > > > Dimitris > > > > Would you please copy kernel.sys from the 2042 release to your C drive and > see if it boots. Do not run sys or anything else, just a simple copy. > This will help confirm if the issue is with the kernel or sys. It should > work. > Yes this works perfectly! I just copied kernel.sys from 1.2 boot floppy over the kernel.sys from 2031 and it worked! I was able to boot from C: with 2042 kernel. > If possible I would also appreciate if you could recap for me which > version of sys you ran and options that provided a booting system (kernels > don't necessarily relate to sys versions). E.g. sys 2.6 with command of > sys C: > sys c: , with sys version 2.6, works. > I may ask you to send me your boot sector privately. Latest sys can > easily save it. > Sure, this is no problem. Cheers, Dimitris -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Which freedos on 486
Hi, On Wed, Jul 20, 2016 at 9:50 PM, Jerome E. Shidel Jr. wrote: > On Jul 20, 2016, at 12:56 PM, Dimitris Zilaskos > wrote: > […] > > Dimitris > > > I have a few silly questions. > > You have verified the drive has the correct jumpers set? > Correct, master / slave > > You are not trying to use cable select mode? > Nope > > You are using the correct position on the IDE cable? > Yes > > You are plugged into the primary controller? > Yes > > Is the BIOS configuration for the drive being set manually or using "auto" > mode? > This is actually a good question. It is user mode which would qualify as manually, but I can't remember if the values for CHS were actually entered manually by copying them from the labels, or using the auto detect BIOS feature. I do recall it look a lot of effort to figure this out, as any mistake and the system would not detect the hdds or boot altogether. > > You mentioned “tertiary” at one point. How many drives? How many > controllers? > The sound blaster card has one IDE port that currently has 2 CD-ROM drives connected in master/slave setup > > Is the drive partitioned as a single disk or multiple partitions? > single partition > > It is not inside an extended partition? > No > > If there are any other drives, are they partitioned and formatted for DOS? > Yes, the slave drive is an old windows98 system with a fat32 partition. I can simplify the setup - remove all CDROM drives and the slave hard drive and leave only one hdd and the floppy to see if there is any change. Cheers, Dimitris -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Which freedos on 486
Hi On Wed, Jul 20, 2016 at 2:09 PM, Eric Auer wrote: > > Hi Dimitris, > > > So I did, with sys 3.6e - FreeDOS 1.2 pre floppy: > > > > sys c: /FORCE:CHS - system hangs on reboot > > sys c: /FORCE:LBA , followed by sys CONFIG c:\kernel.sys FORCELBA=1 > > GLOBALENABLELBA=1 > > > > - system tries to BOOT, hangs at Loading FreeDOS , the hard drive > > works like mad until I hit control-alt-delete > > (and the same with SYS 2.6 and kernel 2042 with DISabled LBA) > > What if you use /FORCE:LBA but without any SYS CONFIG? > Hangs right after Loading FreeDOS, hard drive works like mad > > And of course: What if you use SYS 3.6e but with some > older version of the kernel? sys 3.6e with kernel 2031 hangs at BIOS summary > > If the system hangs on reboot with the CHS boot sector, > it is possible that your FAT32 boot partition either is > outside the CHS-reachable area or that the MBR, BIOS and > DOS disagree about what the CHS geometry should be. But: > > On the other hand, you wrote that kernel 2031 boots for > you with SYS 2.6, while SYS 2.6 always uses CHS on FAT32! > > Note that SYS 3.6e also lets you use force options for > the BIOS disk number. In case something gets confused > by your relatively large collection of connected disks. > > > I retried sys c: from the 2031 bootdisk and it failed to boot, hanging at Loading FreeDOS, hard drive working like mad, I rebooted with the same floppy, did the same thing, and it booted. Tried again with sys 3.6e, hang again, tried again with sys 2.6, was able to boot again. Since I now have a bootable C: drive, can't we just compare the working MBR/boot sector with the non working one? Cheers, Dimitris -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Which freedos on 486
Hi, I have tried sys 2.6 with 2042, I checked and sys CONFIG reported both FORCELBA and GLOBALENABLELBA were set to 0. Reboot resuts in a hang at Loading FreeDOS, hard drive and the floppy leds are lit up and hard drive works like mad. Cheers, Dimitris On Wed, Jul 20, 2016 at 1:25 PM, Dimitris Zilaskos wrote: > Hi, > > > On Wed, Jul 20, 2016 at 12:58 PM, Eric Auer wrote: > >> >> Hi Dimitris, >> >> long analysis follows, some suggestions at the bottom of this mail :-) >> >> > Thank you for your reply. I tried few kernel and here are the results: >> >> I gather you mean "you tried the SYS of a few kernels together with >> the corresponding KERNEL versions"? My focus is on the SYS activity, >> as the kernel should at least show a version message before hanging >> as long as the boot sector put by SYS has done the correct stuff. >> > > I downloaded the zip file, extracted the contents of BIN on a floppy, > executed install.bat from the floppy inserted in the 486 system. Sometimes > I modified install.bat, others just ran sys c: from within the BIN folder, > sometimes I copied the bin folder to the 486 hdd, ran install.bat, rebooted > from floppy and then sys c:, reboot. I was not very consistent. > >> >> > 2041_86f16 : floppy boots but no hard drives detected >> >> If you only have FAT32 partitions, then using a kernel without >> FAT32 support would lead to that expected result, yes ;-) >> > > Ok, makes sense. > > >> >> Other versions, sorted (2020 is anycient anyway) from old to new: >> >> > 2030: BOOTS! >> > 2031_32: BOOTS! >> >> > 2032: hangs >> > 2032a: hangs >> >> > 2035a: boots, detects HDD, sys [...] hard drive fails to boot >> > 2039_86f32: as above >> > 2041_[3]86f32: as above >> >> In short, we introduced a bug in the SYS of version 2032? >> That would be 2003-09-21 while version 2031 is 2003-07-19. >> >> But your pictures on Google seem to say that version 2032 >> still is okay, while newer versions are not okay? >> > > I do not think this is correct. 2031 is the latest version that was able > to boot my system from hard drive. I am using the version referring both to > kernel.sys and the accompanying sys in the zip file where I got the kernel > from - probably this is confusing. > > >> >> > And that one results in a hang: >> > >> > https://drive.google.com/open?id=0B2zW1ur6Z_WedkQtSXBYMS1YN0U >> >> As Google is a pain for DOS users, a summary of what it says... >> >> SYS 2.8 detects FAT32, FAT at sector 3f+20, 0 root dir entries, >> FAT at sector 63+32, root dir at PREVIOUS + 0*2, kernel.sys has >> 45884 bytes, command.com has 92109 bytes... (date 2003-09-21) >> >> > This is a successfully sys c: output >> > >> > https://drive.google.com/open?id=0B2zW1ur6Z_WeX1pZSXktNTd3SFE >> >> SYS 2.6 (unknown date) kernel.sys 44900 bytes, FAT at sector 5f >> which is 3f+20, data at sector 603f, 0 root dir entries, 255 root >> dir sectors (really???), FAT at sector 487060009 = 63+32 (???), >> root dir at sector 1313429276 = PREVIOUS + 0*2, data starts at >> sector 1163081785 = PREVIOUS + 255, command.com is 92109 bytes. >> >> Note that the displayed numbers look very wrong, so SYS might be >> calculating bogus FAT32 parameters... Or maybe it only displays >> wrong values, while internally using correct values. This can be >> a side effect of compiling SYS with the "wrong" compiler in case >> of incomplete portability. The weird thing is that SYS works for >> you in version 2.6 :-) >> >> Checking the source code... >> >> > >> https://sourceforge.net/p/freedos/svn/1744/log/?path=/kernel/trunk/sys/sys.c >> >> 2009: Jeremy introduced a command line option to force CHS / LBA. >> >> 2004, 2009, 2010, 2011: Fixes to make things work for all compilers? >> >> 2007: Faster file copy, update FAT32 backup boot sector if needed. >> >> 2007: Fixes for FAT32 >> >> 2003-09-21: Metakern compatibility r702 >> >> 2003-08-08: Support for other sector sizes on FAT16, SYS 2.7 >> (note that the kernel itself only works for 512 byte sectors) >> >> 2003-06-16: This is version SYS 2.6 here. >> >> > >> https://sourceforge.net/p/freedos/svn/607/tree/kernel/trunk/boot/boot32.asm >> >> > https://sourceforge.net/p/freedos/svn/607/tree/kernel/trunk/sys/sys.c >> >> etc. Note that SYS 2.6 only supports CHS style boot for FAT32! >> >> I suggest the
Re: [Freedos-user] Which freedos on 486
Hi, On Wed, Jul 20, 2016 at 12:58 PM, Eric Auer wrote: > > Hi Dimitris, > > long analysis follows, some suggestions at the bottom of this mail :-) > > > Thank you for your reply. I tried few kernel and here are the results: > > I gather you mean "you tried the SYS of a few kernels together with > the corresponding KERNEL versions"? My focus is on the SYS activity, > as the kernel should at least show a version message before hanging > as long as the boot sector put by SYS has done the correct stuff. > I downloaded the zip file, extracted the contents of BIN on a floppy, executed install.bat from the floppy inserted in the 486 system. Sometimes I modified install.bat, others just ran sys c: from within the BIN folder, sometimes I copied the bin folder to the 486 hdd, ran install.bat, rebooted from floppy and then sys c:, reboot. I was not very consistent. > > > 2041_86f16 : floppy boots but no hard drives detected > > If you only have FAT32 partitions, then using a kernel without > FAT32 support would lead to that expected result, yes ;-) > Ok, makes sense. > > Other versions, sorted (2020 is anycient anyway) from old to new: > > > 2030: BOOTS! > > 2031_32: BOOTS! > > > 2032: hangs > > 2032a: hangs > > > 2035a: boots, detects HDD, sys [...] hard drive fails to boot > > 2039_86f32: as above > > 2041_[3]86f32: as above > > In short, we introduced a bug in the SYS of version 2032? > That would be 2003-09-21 while version 2031 is 2003-07-19. > > But your pictures on Google seem to say that version 2032 > still is okay, while newer versions are not okay? > I do not think this is correct. 2031 is the latest version that was able to boot my system from hard drive. I am using the version referring both to kernel.sys and the accompanying sys in the zip file where I got the kernel from - probably this is confusing. > > > And that one results in a hang: > > > > https://drive.google.com/open?id=0B2zW1ur6Z_WedkQtSXBYMS1YN0U > > As Google is a pain for DOS users, a summary of what it says... > > SYS 2.8 detects FAT32, FAT at sector 3f+20, 0 root dir entries, > FAT at sector 63+32, root dir at PREVIOUS + 0*2, kernel.sys has > 45884 bytes, command.com has 92109 bytes... (date 2003-09-21) > > > This is a successfully sys c: output > > > > https://drive.google.com/open?id=0B2zW1ur6Z_WeX1pZSXktNTd3SFE > > SYS 2.6 (unknown date) kernel.sys 44900 bytes, FAT at sector 5f > which is 3f+20, data at sector 603f, 0 root dir entries, 255 root > dir sectors (really???), FAT at sector 487060009 = 63+32 (???), > root dir at sector 1313429276 = PREVIOUS + 0*2, data starts at > sector 1163081785 = PREVIOUS + 255, command.com is 92109 bytes. > > Note that the displayed numbers look very wrong, so SYS might be > calculating bogus FAT32 parameters... Or maybe it only displays > wrong values, while internally using correct values. This can be > a side effect of compiling SYS with the "wrong" compiler in case > of incomplete portability. The weird thing is that SYS works for > you in version 2.6 :-) > > Checking the source code... > > > > https://sourceforge.net/p/freedos/svn/1744/log/?path=/kernel/trunk/sys/sys.c > > 2009: Jeremy introduced a command line option to force CHS / LBA. > > 2004, 2009, 2010, 2011: Fixes to make things work for all compilers? > > 2007: Faster file copy, update FAT32 backup boot sector if needed. > > 2007: Fixes for FAT32 > > 2003-09-21: Metakern compatibility r702 > > 2003-08-08: Support for other sector sizes on FAT16, SYS 2.7 > (note that the kernel itself only works for 512 byte sectors) > > 2003-06-16: This is version SYS 2.6 here. > > > > https://sourceforge.net/p/freedos/svn/607/tree/kernel/trunk/boot/boot32.asm > > > https://sourceforge.net/p/freedos/svn/607/tree/kernel/trunk/sys/sys.c > > etc. Note that SYS 2.6 only supports CHS style boot for FAT32! > > I suggest the following: Apparently the FAT32 boot sectors have > not changed since 2004, but SYS itself has evolved further. In > particular, try the newest SYS 3.6e which has two options for > /FORCE:LBA and /FORCE:CHS with obvious effects. Please try with > /VERBOSE and with > output.txt so you can paste results into a > mail, without Javascript-heavy DOS-unfriendly Google Drive pics. > > I see two possible problems: Either your BIOS supports LBA but > our FAT32 LBA boot sector is incompatible with it. In that case, > the /FORCE:CHS option for SYS will help you. Or SYS itself has > errors in calculating FAT32 parameters. Then both LBA and CHS > might be broken in certain versions of SYS, but should at least > be fixed again in newest versions. > > > > https://sourceforge.net/p/freedos/svn/1744/log/?path=/kernel/trunk/boot/boot32.asm > > > > https://sourceforge.net/p/freedos/svn/1744/log/?path=/kernel/trunk/boot/boot32lb.asm > > This tells me that the FAT32 boot sectors changed at those dates: > > 2004-01-24 different load seg and stack handling, no int 13.0 > (SYS 3.1, kernel 2.0.33, claims to improve FAT parameter calculation) > > 2003-09-21
Re: [Freedos-user] Which freedos on 486
Hi, Thank you for your reply. I tried few kernel and here are the results: 2041_86f16 : floppy boots but no hard drives detected 2041_86f32: boots, detects HDD, sys is successfull but hard drive fails to boot 2041_386f32: as above 2039_86f32: as above 2035a: as above 2020: fails to boot even from floppy-hangs at unable to open c:\freedos.log 2030: BOOTS! 2032a32:hangs 2032:hangs 2031_32: BOOTS! This is a successfully sys c: output https://drive.google.com/open?id=0B2zW1ur6Z_WeX1pZSXktNTd3SFE And that one results in a hang: https://drive.google.com/open?id=0B2zW1ur6Z_WedkQtSXBYMS1YN0U Cheers, Dimitris On Wed, Jul 20, 2016 at 12:04 AM, Rugxulo wrote: > Hi, > > On Tue, Jul 19, 2016 at 8:26 AM, Dimitris Zilaskos > wrote: > > > > I have LBA configured in the BIOS for the hard drives, mostly because it > > keeps BIOS boot and Windows 98 working. I was unable so far to find a > > working combination with different non LBA modes. I will retry sys c: on > a > > new FAT32 installation. > > Try different SYSs from different kernels (e.g. 2039, 2041). You > already tried 2042 and 2036, yes? Who knows, it's a long shot, but it > could be a rare bug / regression. > > https://sourceforge.net/projects/freedos/files/Kernel/ > > Heck, since you say you have Debian (but is that separate machine?), > you could try Eric's Sys-FreeDOS-Linux (Perl + NASM) there. > > > http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/sys/sys-freedos-linux/ > > > -- > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > reports.http://sdm.link/zohodev2dev > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Which freedos on 486
Hi, With /X and /NOABOVE16 there is no gibberish but a hang. The last message HimemX prints is KBC A20 method used. btmgr was a pain to install - does not compile on the Debian 8 system which is the only other system I have with working floppy drive. I did not try to install the rpm but what worked is running the dos binary from the 486 after copying it over there with a floppy and figuring out the Load error: no DPMI - get csdpmi*b.zip error I kept getting. I was unable to get it detect my CDROM drives so far. I will connect them to the primary IDE and see what happens. I have tried all sorts of CDROM I/O ports settings without luck for secondary and tertiary IDE. I have LBA configured in the BIOS for the hard drives, mostly because it keeps BIOS boot and Windows 98 working. I was unable so far to find a working combination with different non LBA modes. I will retry sys c: on a new FAT32 installation. Cheers, Dimitris On Tue, Jul 19, 2016 at 9:10 AM, Eric Auer wrote: > > Hi Dimitris and others, > > as I received some (aggressive) corrections from Jack and Johnson: > > Yes of course I can read manuals myself. The XMGR option /T0 means > 'No "E820h" nor "E801h" requests.' so please try if the two HIMEMX > options /X (no int 15.e820 requests) and /NOABOVE16 (no int 15.e801 > requests) options make things work even with HIMEMX :-) Remember to > update both the installer boot config and config on C: afterwards. > > My excuses for guessing that A20 issues might be the problem here. > Jack's implicit suggestion that the BIOS has int 15 bugs is better. > > Next topic: I do NOT claim that FDISK /MBR should help you. I only > replied to the other posting where somebody suggested that. I have > no opinion about which DOS brands should benefit from updating MBR. > But I wanted to warn about possible side effects of FDISK /MBR ... > > Third topic: 486 often can NOT boot from CD-ROM, but the Smart Boot > Manager is pretty cool! It can be installed to a boot floppy which > then helps you to boot from CD-ROM, even without full BIOS support: > > http://btmgr.sourceforge.net/about.html > > > > Now to reply to the other 486 related reactions on the mailing list: > > I see that you have not been able to make SBM work on your 486 yet, > but there could still be some trick to make it work even there :-) > > Also interesting that booting failed from FAT32 but not from FAT16: > It may also make a difference whether you use LBA or non-LBA for the > partition type. There also is a small chance that DOS and BIOS are > not agreeing about CHS geometry, although this should not happen. It > can be an idea to manually use SYS command line options to get boot > sectors for FAT32-LBA instead of FAT32-CHS or vice versa. > > As far as I remember, our FAT16 boot sector auto-selects CHS or LBA. > As Louis wrote, the default FAT32 boot sector may need LBA and your > BIOS may be without LBA or with LBA bugs. Try SYS-ing FAT32 to CHS. > > Cheers, Eric > > > > > -- > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > reports.http://sdm.link/zohodev2dev > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Which freedos on 486
Hi, No EDD here: ERROR: Your BIOS/INT13h doesn't support EDD extension. Cheers, Dimitris On Tue, Jul 19, 2016 at 7:16 AM, Louis Santillan wrote: > Dimitris, > > What does EDDINFO [0] display? > > > [0] http://rayer.g6.cz/programm/eddinfo.exe > > On Mon, Jul 18, 2016 at 10:56 PM, Mateusz Viste wrote: > > I might be missing the boat here, but what you describe vaguely look > > like a problem I had in some distant past, when I misconfigured my HDD > > in the BIOS. > > > > Perhaps you could check whether your drive's geometry is 100% correct in > > your BIOS? > > > > Mateusz > > > > > > > > > > On 19/07/2016 07:12, Dimitris Zilaskos wrote: > >> Hi, > >> > >> I was able to reinstall and boot successfully by performing an fdisk > >> without FAT32 support, and creating a FAT16 2GB partition. At least with > >> JEMM386, that is. So FAT32 support being the issue may be the case. > >> > >> Let me know if I can try anything else to confirm that. > >> > >> Cheers, > >> > >> Dimitris > >> > >> On Tue, Jul 19, 2016 at 6:03 AM, Dimitris Zilaskos >> <mailto:dimitr...@gmail.com>> wrote: > >> > >> Hi, > >> > >> On Tue, Jul 19, 2016 at 1:58 AM, Rugxulo >> <mailto:rugx...@gmail.com>> wrote: > >> > >> Hi, > >> > >> On Mon, Jul 18, 2016 at 7:21 PM, Dimitris Zilaskos > >> mailto:dimitr...@gmail.com>> wrote: > >> > > >> > Thank you for following up. fdisk reports that C: drive is > already active. I > >> > did run mbrzap it completed successfully but there has been > no change, > >> > system gets stuck right after BIOS summary table. > >> > >> What filesystem(s) are you using? FAT32, presumably. You said > >> you had > >> 4 GB and 6 GB HDDs, right? > >> > >> Sometimes it has been noticed that a FAT32 partition is created > with > >> plain type 0xB instead of 0xC (LBA), so you may have to change > that. > >> > >> http://help.fdos.org/en/hhstndrd/base/fdisk.htm > >> > >> I'm not entirely sure what is most informative or useful here: > >> "/STATUS"? "/XO"? "/SPEC"? > >> > >> Honestly, I think I just used BootMgr to change it: > >> > >> http://www.freedos.org/software/?prog=bootmgr > >> > >> (This may not be your problem, I'm just grasping at straws.) > >> > >> > >> > >> Indeed the partition type is 11. I have used fdisk to change that to > >> 12 but there was no change. I did a re-installation after the change > >> too. > >> > >> Cheers, > >> > >> Dimitris > >> > >> > >> > > > > > > > > > -- > > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > > patterns at an interface-level. Reveals which users, apps, and protocols > are > > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > > reports.http://sdm.link/zohodev2dev > > ___ > > Freedos-user mailing list > > Freedos-user@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/freedos-user > > > -- > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > reports.http://sdm.link/zohodev2dev > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Which freedos on 486
Hi, I will try to double check. It was difficult for me to find a working combination of CHS and mode. However Windows98 had no issues with identical settings. Best regards, Dimitris On Tue, Jul 19, 2016 at 6:56 AM, Mateusz Viste wrote: > I might be missing the boat here, but what you describe vaguely look > like a problem I had in some distant past, when I misconfigured my HDD > in the BIOS. > > Perhaps you could check whether your drive's geometry is 100% correct in > your BIOS? > > Mateusz > > > > > On 19/07/2016 07:12, Dimitris Zilaskos wrote: > > Hi, > > > > I was able to reinstall and boot successfully by performing an fdisk > > without FAT32 support, and creating a FAT16 2GB partition. At least with > > JEMM386, that is. So FAT32 support being the issue may be the case. > > > > Let me know if I can try anything else to confirm that. > > > > Cheers, > > > > Dimitris > > > > On Tue, Jul 19, 2016 at 6:03 AM, Dimitris Zilaskos > <mailto:dimitr...@gmail.com>> wrote: > > > > Hi, > > > > On Tue, Jul 19, 2016 at 1:58 AM, Rugxulo > <mailto:rugx...@gmail.com>> wrote: > > > > Hi, > > > > On Mon, Jul 18, 2016 at 7:21 PM, Dimitris Zilaskos > > mailto:dimitr...@gmail.com>> wrote: > > > > > > Thank you for following up. fdisk reports that C: drive is > already active. I > > > did run mbrzap it completed successfully but there has been no > change, > > > system gets stuck right after BIOS summary table. > > > > What filesystem(s) are you using? FAT32, presumably. You said > > you had > > 4 GB and 6 GB HDDs, right? > > > > Sometimes it has been noticed that a FAT32 partition is created > with > > plain type 0xB instead of 0xC (LBA), so you may have to change > that. > > > > http://help.fdos.org/en/hhstndrd/base/fdisk.htm > > > > I'm not entirely sure what is most informative or useful here: > > "/STATUS"? "/XO"? "/SPEC"? > > > > Honestly, I think I just used BootMgr to change it: > > > > http://www.freedos.org/software/?prog=bootmgr > > > > (This may not be your problem, I'm just grasping at straws.) > > > > > > > > Indeed the partition type is 11. I have used fdisk to change that to > > 12 but there was no change. I did a re-installation after the change > > too. > > > > Cheers, > > > > Dimitris > > > > > > > > > > > -- > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > reports.http://sdm.link/zohodev2dev > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Which freedos on 486
Hi, I was able to reinstall and boot successfully by performing an fdisk without FAT32 support, and creating a FAT16 2GB partition. At least with JEMM386, that is. So FAT32 support being the issue may be the case. Let me know if I can try anything else to confirm that. Cheers, Dimitris On Tue, Jul 19, 2016 at 6:03 AM, Dimitris Zilaskos wrote: > Hi, > > On Tue, Jul 19, 2016 at 1:58 AM, Rugxulo wrote: > >> Hi, >> >> On Mon, Jul 18, 2016 at 7:21 PM, Dimitris Zilaskos >> wrote: >> > >> > Thank you for following up. fdisk reports that C: drive is already >> active. I >> > did run mbrzap it completed successfully but there has been no change, >> > system gets stuck right after BIOS summary table. >> >> What filesystem(s) are you using? FAT32, presumably. You said you had >> 4 GB and 6 GB HDDs, right? >> >> Sometimes it has been noticed that a FAT32 partition is created with >> plain type 0xB instead of 0xC (LBA), so you may have to change that. >> >> http://help.fdos.org/en/hhstndrd/base/fdisk.htm >> >> I'm not entirely sure what is most informative or useful here: >> "/STATUS"? "/XO"? "/SPEC"? >> >> Honestly, I think I just used BootMgr to change it: >> >> http://www.freedos.org/software/?prog=bootmgr >> >> (This may not be your problem, I'm just grasping at straws.) >> >> >> > Indeed the partition type is 11. I have used fdisk to change that to 12 > but there was no change. I did a re-installation after the change too. > > Cheers, > > Dimitris > > -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Which freedos on 486
Hi, On Tue, Jul 19, 2016 at 1:58 AM, Rugxulo wrote: > Hi, > > On Mon, Jul 18, 2016 at 7:21 PM, Dimitris Zilaskos > wrote: > > > > Thank you for following up. fdisk reports that C: drive is already > active. I > > did run mbrzap it completed successfully but there has been no change, > > system gets stuck right after BIOS summary table. > > What filesystem(s) are you using? FAT32, presumably. You said you had > 4 GB and 6 GB HDDs, right? > > Sometimes it has been noticed that a FAT32 partition is created with > plain type 0xB instead of 0xC (LBA), so you may have to change that. > > http://help.fdos.org/en/hhstndrd/base/fdisk.htm > > I'm not entirely sure what is most informative or useful here: > "/STATUS"? "/XO"? "/SPEC"? > > Honestly, I think I just used BootMgr to change it: > > http://www.freedos.org/software/?prog=bootmgr > > (This may not be your problem, I'm just grasping at straws.) > > > Indeed the partition type is 11. I have used fdisk to change that to 12 but there was no change. I did a re-installation after the change too. Cheers, Dimitris -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Which freedos on 486
Hi, Thank you for following up. fdisk reports that C: drive is already active. I did run mbrzap it completed successfully but there has been no change, system gets stuck right after BIOS summary table. Cheers, Dimitris On Tue, Jul 19, 2016 at 12:29 AM, Jerome Shidel wrote: > > > On Jul 18, 2016, at 6:52 PM, Dimitris Zilaskos > wrote: > > Dear Jerome, > > From what I can tell I never get past the boot loader to be struck by > himemx. > > > Ok try this: > > Boot your modified FDI floppy. > It should detect FreeDOS has been already installed and go straight to the > command prompt. > > Run "MBRZAP" > This will launch a special part of FDI in advanced mode to force update > your MBR with the FreeDOS boot loader. > > --- > During investigations of systems that had boot loader issues not being > updated, I discovered that there is no way to force the sys command to > updated the MBR. Sometimes, it just won't do it regardless of what you tell > it to do. It can be forced using fdisk. > > There is another possible issue. Your MBR may be fine. However, FDI may > have not been able to identify the drive or partition that FreeDOS was > installed onto. You should run fdisk and verify that the FreeDOS partition > is set as ACTIVE. > > Jerome > > Sent from my iPhone, ignore bad sentence structures, grammatical errors > and incorrect spell-corrected words. > > Cheers, > > Dimitris > > On Mon, Jul 18, 2016 at 10:49 PM, Jerome Shidel wrote: > >> Did you change the installed config? >> >> It uses himemx as well. >> >> Sent from my iPhone, ignore bad sentence structures, grammatical errors >> and incorrect spell-corrected words. >> >> On Jul 18, 2016, at 3:46 PM, Dimitris Zilaskos >> wrote: >> >> Thank you all for your suggestions. What I have tried so far: >> >>* Getting rid of himemx: this works - the boot process continues and >> the installer tries to start. However the floppy drive works continuously >> like mad, screen updates are slow, and I the installation appears to be >> stuck in the 'Gathering information..' stage forever >>* Replacing himemx with XMGR.SYS /T0 (kudos to Jack): Boot process >> continues, everything is light speed fast compared to just getting rid of >> himemx. >>* Although installation of 1.2 finishes successfully, system fails to >> boot, hangs right after BIOS system summary is displayed. >>* sys c: does not help >>* UDVD2 is able to detect the CDROM connected to the SB16 IDE >> interface. Unfortunately only the CDROM drive that was supplied with sound >> card appears to work there (MATSHITA CR-581-M), connecting other CDROMs >> that can actually read modern CD-R causes the system to get stuck after >> memory test. So I have to use a 1998 HITACHI CDR-8435 attached to the >> secondary VESA Local Bus IDE for the installation. UDVD2 reports the SB16 >> CDROM drive in IDE1 - I would expect that to be IDE2 for tertiary IDE so I >> may need to play with jumpers. >> >> I will try to sort out why the boot loader fails. >> >> Thanks! >> >> Dimitris >> >> >> On Mon, Jul 18, 2016 at 5:04 PM, Don Flowers wrote: >> >>> Your driver is the problem this might be a case for the XCDROM.SYS >>> driver combined with SHCDX86.COM - A quick way to find out download >>> this file >>> >>> https://sourceforge.net/projects/xosl-ow/files/xosl-ow116/BootMedia/BootFloppy/ >>> and see if you have clean drive access. >>> >>> >>> On Mon, Jul 18, 2016 at 9:02 AM, Dimitris Zilaskos >>> wrote: >>> >>>> Hi, >>>> >>>> Thanks for the followup. Hitting F8 reveals HIMEMX triggering this >>>> problem: https://drive.google.com/open?id=0B2zW1ur6Z_WeSWtGNXN0NmxxaU0 >>>> >>>> I have observed that the gibberish stops given sufficient time: >>>> https://drive.google.com/open?id=0B2zW1ur6Z_WeVjVMalF6M2YtMTA >>>> >>>> Let me know what else I can try - I will recheck the floppies for >>>> starters in case they went bad and check the rest of your suggestions. >>>> >>>> Best regards, >>>> >>>> Dimitris >>>> >>>> >>>> On Mon, Jul 18, 2016 at 1:02 PM, Jerome E. Shidel Jr. < >>>> jer...@shidel.net> wrote: >>>> >>>>> >>>>> On Jul 18, 2016, at 7:51 AM, Dimitris Zilaskos >>>>> wrote: >>>>> >>>>> I have tried it please see t
Re: [Freedos-user] Which freedos on 486
Hi, fdisk /mbr:80 did not change anything. Here some BIOS screens: https://drive.google.com/open?id=0B2zW1ur6Z_Wed09TVi1YY3VNR2s https://drive.google.com/open?id=0B2zW1ur6Z_WeWDdxWXRrY2NpWEU https://drive.google.com/open?id=0B2zW1ur6Z_WeQ3ctSS14Z1RINlk Here is a video of the system booting from FreeDOS 1.2 floppy: https://drive.google.com/open?id=0B2zW1ur6Z_WeTEtKU1kyNGp3SWc Cheers, Dimitris On Mon, Jul 18, 2016 at 9:53 PM, Louis Santillan wrote: > Dimitris, > > For giggles, could you do two things? First, capture the BIOS screens > for booting and IDE/HD parameters. Second, after installing FreeDOS > to C: drive, run the command `fdisk /MBR:80`. > > On Mon, Jul 18, 2016 at 12:46 PM, Dimitris Zilaskos > wrote: > > Thank you all for your suggestions. What I have tried so far: > > > >* Getting rid of himemx: this works - the boot process continues and > the > > installer tries to start. However the floppy drive works continuously > like > > mad, screen updates are slow, and I the installation appears to be stuck > in > > the 'Gathering information..' stage forever > >* Replacing himemx with XMGR.SYS /T0 (kudos to Jack): Boot process > > continues, everything is light speed fast compared to just getting rid of > > himemx. > >* Although installation of 1.2 finishes successfully, system fails to > > boot, hangs right after BIOS system summary is displayed. > >* sys c: does not help > >* UDVD2 is able to detect the CDROM connected to the SB16 IDE > interface. > > Unfortunately only the CDROM drive that was supplied with sound card > appears > > to work there (MATSHITA CR-581-M), connecting other CDROMs that can > actually > > read modern CD-R causes the system to get stuck after memory test. So I > have > > to use a 1998 HITACHI CDR-8435 attached to the secondary VESA Local Bus > IDE > > for the installation. UDVD2 reports the SB16 CDROM drive in IDE1 - I > would > > expect that to be IDE2 for tertiary IDE so I may need to play with > jumpers. > > > > I will try to sort out why the boot loader fails. > > > > Thanks! > > > > Dimitris > > > > > > On Mon, Jul 18, 2016 at 5:04 PM, Don Flowers wrote: > >> > >> Your driver is the problem this might be a case for the XCDROM.SYS > driver > >> combined with SHCDX86.COM - A quick way to find out download this file > >> > >> > https://sourceforge.net/projects/xosl-ow/files/xosl-ow116/BootMedia/BootFloppy/ > >> and see if you have clean drive access. > >> > >> > >> On Mon, Jul 18, 2016 at 9:02 AM, Dimitris Zilaskos > > >> wrote: > >>> > >>> Hi, > >>> > >>> Thanks for the followup. Hitting F8 reveals HIMEMX triggering this > >>> problem: https://drive.google.com/open?id=0B2zW1ur6Z_WeSWtGNXN0NmxxaU0 > >>> > >>> I have observed that the gibberish stops given sufficient time: > >>> https://drive.google.com/open?id=0B2zW1ur6Z_WeVjVMalF6M2YtMTA > >>> > >>> Let me know what else I can try - I will recheck the floppies for > >>> starters in case they went bad and check the rest of your suggestions. > >>> > >>> Best regards, > >>> > >>> Dimitris > >>> > >>> > >>> On Mon, Jul 18, 2016 at 1:02 PM, Jerome E. Shidel Jr. < > jer...@shidel.net> > >>> wrote: > >>>> > >>>> > >>>> On Jul 18, 2016, at 7:51 AM, Dimitris Zilaskos > >>>> wrote: > >>>> > >>>> I have tried it please see the output attached. This is endlessly > >>>> scrolling after drives are detected. > >>>> > >>>> > >>>> > https://drive.google.com/open?id=0B2zW1ur6Z_WeY2tOSXpNT2g3NUJWMWx6bFZlSFBjamE3VEFr > >>>> > >>>> Unfortunately, that isn’t very helpful. > >>>> > >>>> When you boot the floppy, can you press F8 to walk through the > startup? > >>>> What item in the configuration > >>>> causes it to crash? > >>>> > >>>> Jerome > >>>> > >>>> > >>>> > -- > >>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and > >>>> traffic > >>>> patterns at an interface-level. Reveals which users, apps, and > protocols > >>>> are > >>>> consuming the most ban
Re: [Freedos-user] Which freedos on 486
Hi, On Mon, Jul 18, 2016 at 10:48 PM, Eric Auer wrote: > > Hi Dimitris, > > > * Getting rid of himemx: this works ... > > But very slow and lots of floppy access: I assume you booted from > floppy because the BIOS does not support CD boot and the CD also > needs to be some ancient model connected to the sound card? Then > I wonder if a newer model would work if connected to the normal > IDE controller which your 486 must already have. Because then it > may be possible to boot with a Smart Boot Manager floppy to CD... > If you have questions about SBM, Rugxulo could probably help ;-) > Indeed! Your assumptions are correct. Getting SBM installed to a floppy was tricky but I got it. However it does not detect any CDROM drives, no matter if they are connected on the SB16 IDE or the VL Bus Secondary IDE. I tried 1E0-1EFh I/O port range per http://support.creative.com/kb/ShowArticle.aspx?sid=3039 and looking at the SB16 jumpers but no luck. > > > * Replacing himemx with XMGR.SYS /T0 (kudos to Jack) > > Cool to know that XMGR works, but what does /T0 mean? Maybe there > is some option for HIMEMX which makes a similar selection, which > could make HIMEMX work as well? :-) > Jack told me /T0 helps with systems with less than 64MB RAM such as mine, > > > * Although installation of 1.2 finishes successfully, system fails > > to boot, hangs right after BIOS system summary is displayed. > > I agree that FDISK /MBR may help. It would replace existing boot > code in the MBR with a "normal" version. Note that if you have to > use something like OnTrack "drivers" hidden in the MBR to use the > full capacity of the harddisk (due to too old BIOS), then this can > overwrite the driver: You might have to install DOS and/or driver > again. > I tried it but nothing changed. I am not using any drives with OnTrack connected atm - I do have some that I may use later. > > > * UDVD2 is able to detect the CDROM connected to the SB16 IDE interface. > > > Unfortunately only the CDROM drive that was supplied with sound > > card appears to work there (MATSHITA CR-581-M)... > > See above :-) > > Cheers, Eric > This turned out to be a red herring, I was able to get all the CDROMS detected by UDVD2 while both of them sitting on the SB16 IDE in master/slave configuration. I suspect I did a mistake during my previous test. > > PS: You may also have a way to change A20 style in BIOS setup, > which can help HIMEMX and XMGR to work without magic options. > BIOS has a Fast and Normal setting for A20, it is currently set to Fast. Will try Normal later. Cheers, Dimitris -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Which freedos on 486
Dear Jerome, >From what I can tell I never get past the boot loader to be struck by himemx. Cheers, Dimitris On Mon, Jul 18, 2016 at 10:49 PM, Jerome Shidel wrote: > Did you change the installed config? > > It uses himemx as well. > > Sent from my iPhone, ignore bad sentence structures, grammatical errors > and incorrect spell-corrected words. > > On Jul 18, 2016, at 3:46 PM, Dimitris Zilaskos > wrote: > > Thank you all for your suggestions. What I have tried so far: > >* Getting rid of himemx: this works - the boot process continues and > the installer tries to start. However the floppy drive works continuously > like mad, screen updates are slow, and I the installation appears to be > stuck in the 'Gathering information..' stage forever >* Replacing himemx with XMGR.SYS /T0 (kudos to Jack): Boot process > continues, everything is light speed fast compared to just getting rid of > himemx. >* Although installation of 1.2 finishes successfully, system fails to > boot, hangs right after BIOS system summary is displayed. >* sys c: does not help >* UDVD2 is able to detect the CDROM connected to the SB16 IDE > interface. Unfortunately only the CDROM drive that was supplied with sound > card appears to work there (MATSHITA CR-581-M), connecting other CDROMs > that can actually read modern CD-R causes the system to get stuck after > memory test. So I have to use a 1998 HITACHI CDR-8435 attached to the > secondary VESA Local Bus IDE for the installation. UDVD2 reports the SB16 > CDROM drive in IDE1 - I would expect that to be IDE2 for tertiary IDE so I > may need to play with jumpers. > > I will try to sort out why the boot loader fails. > > Thanks! > > Dimitris > > > On Mon, Jul 18, 2016 at 5:04 PM, Don Flowers wrote: > >> Your driver is the problem this might be a case for the XCDROM.SYS driver >> combined with SHCDX86.COM - A quick way to find out download this file >> >> https://sourceforge.net/projects/xosl-ow/files/xosl-ow116/BootMedia/BootFloppy/ >> and see if you have clean drive access. >> >> >> On Mon, Jul 18, 2016 at 9:02 AM, Dimitris Zilaskos >> wrote: >> >>> Hi, >>> >>> Thanks for the followup. Hitting F8 reveals HIMEMX triggering this >>> problem: https://drive.google.com/open?id=0B2zW1ur6Z_WeSWtGNXN0NmxxaU0 >>> >>> I have observed that the gibberish stops given sufficient time: >>> https://drive.google.com/open?id=0B2zW1ur6Z_WeVjVMalF6M2YtMTA >>> >>> Let me know what else I can try - I will recheck the floppies for >>> starters in case they went bad and check the rest of your suggestions. >>> >>> Best regards, >>> >>> Dimitris >>> >>> >>> On Mon, Jul 18, 2016 at 1:02 PM, Jerome E. Shidel Jr. >> > wrote: >>> >>>> >>>> On Jul 18, 2016, at 7:51 AM, Dimitris Zilaskos >>>> wrote: >>>> >>>> I have tried it please see the output attached. This is endlessly >>>> scrolling after drives are detected. >>>> >>>> >>>> https://drive.google.com/open?id=0B2zW1ur6Z_WeY2tOSXpNT2g3NUJWMWx6bFZlSFBjamE3VEFr >>>> >>>> Unfortunately, that isn’t very helpful. >>>> >>>> When you boot the floppy, can you press F8 to walk through the >>>> startup? What item in the configuration >>>> causes it to crash? >>>> >>>> Jerome >>>> >>>> >>>> -- >>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and >>>> traffic >>>> patterns at an interface-level. Reveals which users, apps, and >>>> protocols are >>>> consuming the most bandwidth. Provides multi-vendor support for NetFlow, >>>> J-Flow, sFlow and other flows. Make informed decisions using capacity >>>> planning >>>> reports.http://sdm.link/zohodev2dev >>>> ___ >>>> Freedos-user mailing list >>>> Freedos-user@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/freedos-user >>>> >>>> >>> >>> >>> -- >>> What NetFlow Analyzer can do for you? Monitors network bandwidth and >>> traffic >>> patterns at an interface-level. Reveals which users, apps, and protocols >>> are >>>
Re: [Freedos-user] Which freedos on 486
Thank you all for your suggestions. What I have tried so far: * Getting rid of himemx: this works - the boot process continues and the installer tries to start. However the floppy drive works continuously like mad, screen updates are slow, and I the installation appears to be stuck in the 'Gathering information..' stage forever * Replacing himemx with XMGR.SYS /T0 (kudos to Jack): Boot process continues, everything is light speed fast compared to just getting rid of himemx. * Although installation of 1.2 finishes successfully, system fails to boot, hangs right after BIOS system summary is displayed. * sys c: does not help * UDVD2 is able to detect the CDROM connected to the SB16 IDE interface. Unfortunately only the CDROM drive that was supplied with sound card appears to work there (MATSHITA CR-581-M), connecting other CDROMs that can actually read modern CD-R causes the system to get stuck after memory test. So I have to use a 1998 HITACHI CDR-8435 attached to the secondary VESA Local Bus IDE for the installation. UDVD2 reports the SB16 CDROM drive in IDE1 - I would expect that to be IDE2 for tertiary IDE so I may need to play with jumpers. I will try to sort out why the boot loader fails. Thanks! Dimitris On Mon, Jul 18, 2016 at 5:04 PM, Don Flowers wrote: > Your driver is the problem this might be a case for the XCDROM.SYS driver > combined with SHCDX86.COM - A quick way to find out download this file > > https://sourceforge.net/projects/xosl-ow/files/xosl-ow116/BootMedia/BootFloppy/ > and see if you have clean drive access. > > > On Mon, Jul 18, 2016 at 9:02 AM, Dimitris Zilaskos > wrote: > >> Hi, >> >> Thanks for the followup. Hitting F8 reveals HIMEMX triggering this >> problem: https://drive.google.com/open?id=0B2zW1ur6Z_WeSWtGNXN0NmxxaU0 >> >> I have observed that the gibberish stops given sufficient time: >> https://drive.google.com/open?id=0B2zW1ur6Z_WeVjVMalF6M2YtMTA >> >> Let me know what else I can try - I will recheck the floppies for >> starters in case they went bad and check the rest of your suggestions. >> >> Best regards, >> >> Dimitris >> >> >> On Mon, Jul 18, 2016 at 1:02 PM, Jerome E. Shidel Jr. >> wrote: >> >>> >>> On Jul 18, 2016, at 7:51 AM, Dimitris Zilaskos >>> wrote: >>> >>> I have tried it please see the output attached. This is endlessly >>> scrolling after drives are detected. >>> >>> >>> https://drive.google.com/open?id=0B2zW1ur6Z_WeY2tOSXpNT2g3NUJWMWx6bFZlSFBjamE3VEFr >>> >>> Unfortunately, that isn’t very helpful. >>> >>> When you boot the floppy, can you press F8 to walk through the startup? >>> What item in the configuration >>> causes it to crash? >>> >>> Jerome >>> >>> >>> -- >>> What NetFlow Analyzer can do for you? Monitors network bandwidth and >>> traffic >>> patterns at an interface-level. Reveals which users, apps, and protocols >>> are >>> consuming the most bandwidth. Provides multi-vendor support for NetFlow, >>> J-Flow, sFlow and other flows. Make informed decisions using capacity >>> planning >>> reports.http://sdm.link/zohodev2dev >>> ___ >>> Freedos-user mailing list >>> Freedos-user@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/freedos-user >>> >>> >> >> >> -- >> What NetFlow Analyzer can do for you? Monitors network bandwidth and >> traffic >> patterns at an interface-level. Reveals which users, apps, and protocols >> are >> consuming the most bandwidth. Provides multi-vendor support for NetFlow, >> J-Flow, sFlow and other flows. Make informed decisions using capacity >> planning >> reports.http://sdm.link/zohodev2dev >> ___ >> Freedos-user mailing list >> Freedos-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-user >> >> > > > -- > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > reports.http://sdm.
Re: [Freedos-user] Which freedos on 486
Hi, Thanks for the followup. Hitting F8 reveals HIMEMX triggering this problem: https://drive.google.com/open?id=0B2zW1ur6Z_WeSWtGNXN0NmxxaU0 I have observed that the gibberish stops given sufficient time: https://drive.google.com/open?id=0B2zW1ur6Z_WeVjVMalF6M2YtMTA Let me know what else I can try - I will recheck the floppies for starters in case they went bad and check the rest of your suggestions. Best regards, Dimitris On Mon, Jul 18, 2016 at 1:02 PM, Jerome E. Shidel Jr. wrote: > > On Jul 18, 2016, at 7:51 AM, Dimitris Zilaskos > wrote: > > I have tried it please see the output attached. This is endlessly > scrolling after drives are detected. > > > https://drive.google.com/open?id=0B2zW1ur6Z_WeY2tOSXpNT2g3NUJWMWx6bFZlSFBjamE3VEFr > > Unfortunately, that isn’t very helpful. > > When you boot the floppy, can you press F8 to walk through the startup? > What item in the configuration > causes it to crash? > > Jerome > > > -- > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > reports.http://sdm.link/zohodev2dev > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > > -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Fwd: Which freedos on 486
Re-sending this as the attachment is caught up in moderation. -- Forwarded message -- From: Dimitris Zilaskos Date: Mon, Jul 18, 2016 at 11:36 AM Subject: Re: [Freedos-user] Which freedos on 486 To: "Discussion and general questions about FreeDOS." < freedos-user@lists.sourceforge.net> Thank you for your reply. Please see answers inline. On Jul 18, 2016 9:34 AM, "Louis Santillan" wrote: > > On Sun, Jul 17, 2016 at 5:21 PM, Dimitris Zilaskos wrote: > > Hi, > > > > I am trying to install FreeDOS on my old 486. Version 1.0 will boot from > > floppy (only with himem, emm3886 with crash), detect CDROM drive (only if > > connected on Vesa Local bus controller, not on SB16 IDE - tertiary ide IDE > > It is likely that you'll require you sound card manufacturer's CDROM > driver to have it recognize the IDE channel there. The VLB card is > likely recognized natively by the BIOS and/or registering itself in > such a way that its channels are "natively" available to the BIOS. > > > channel) , and install happily. However upon reboot it just hangs , without > > printing anything. > > Are you sys'ing the C: drive after install? Run `sys c:` after the > install program. I tried it, it completed successfully but there was no change. > > > > > > > Versions 1.1 and 1.2 floppy bootdisks either hang on boot printing odd > > characters or will not detect the CDROM. > > Which specific bootdisks do what? I have done a poor job recording that, sorry. > > > > > System is a 486DX4-100, 32 MB RAM.VESA Local Bus controller with primary IDE > > loaded with 2 HDD - 6 GB and 4 GB, secondary IDE the CDROM. BIOS supports > > boot only from floppy and hdd. SB16 CT2290 used to handle the CDROM drive > > via its IDE interface - now I moved the CDROM drive to the VESA card. > > Windows 98SE happily gets installed and works on this system. > > > > Win98SE has much more capable HW detection & driver routines. FreeDOS > (like all DOSes) depends on the BIOS and whatevers you supply it. > > > Is there a recommended strategy to get FreeDOS installed on such an ancient > > system? Did some research and tried several bootdisks that float around, > > nothing worked quite like FreeDOS 1.0. > > If you're willing to test FDI 1.2, download the beta boot floppy [0], > and the cdrom iso [1]. Make sure the boot floppy can recognize your > two hard drives and your CD-ROM. Add drivers and edit > autoexec.bat/fdconfig.sys as necessary (especially wrt to ensuring > CD-ROM access). Install FD 1.2 beta. `sys c:` at the end of your > install. > > [0] http://dnld.lod.bz/FDI-2016-07-17-0.pre.zip > [1] http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/cdrom . I have tried it please see the output attached. This is endlessly scrolling after drives are detected. https://drive.google.com/open?id=0B2zW1ur6Z_WeY2tOSXpNT2g3NUJWMWx6bFZlSFBjamE3VEFr Cheers, Dimitris -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] Which freedos on 486
Hi, I am trying to install FreeDOS on my old 486. Version 1.0 will boot from floppy (only with himem, emm3886 with crash), detect CDROM drive (only if connected on Vesa Local bus controller, not on SB16 IDE - tertiary ide IDE channel) , and install happily. However upon reboot it just hangs , without printing anything. Versions 1.1 and 1.2 floppy bootdisks either hang on boot printing odd characters or will not detect the CDROM. System is a 486DX4-100, 32 MB RAM.VESA Local Bus controller with primary IDE loaded with 2 HDD - 6 GB and 4 GB, secondary IDE the CDROM. BIOS supports boot only from floppy and hdd. SB16 CT2290 used to handle the CDROM drive via its IDE interface - now I moved the CDROM drive to the VESA card. Windows 98SE happily gets installed and works on this system. Is there a recommended strategy to get FreeDOS installed on such an ancient system? Did some research and tried several bootdisks that float around, nothing worked quite like FreeDOS 1.0. Best regards, Dimitris -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
