Re: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s
get a copy of darik's boot and nuke and erase the hard disk, single pass, no verification. when loading the cd, use only the xms option, NO EMM386! then xfdisk the disk using the default choices, except when it comes to write the partition table, then choose yes. then format the disk using the format command. then try to install it (freedos) again. this has always worked for me. i must add, though, do these steps exactly right, else the whole implementation is broken and you'll have to start over again. you can write me direct if you like, my email appears below. the problem is not insurmountable, it's common with v1.0, and 1.1_test3.iso cd works better at installing system. you can add the other stuff from the 1.0 implementation later. eufdp...@yahoo.com eufdp...@yahoo.com eufdp...@yahoo.com eufdp...@yahoo.com eufdp...@yahoo.com From: Anton Vernigor smm...@gmail.com To: freedos-user@lists.sourceforge.net Sent: Tuesday, October 18, 2011 5:00 PM Subject: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s Dear all! I’m trying to install FreeDOS (fdbasecd.iso) on a real (not virtual) machine for the first time, and I’ve met some problems. At first I couldn’t install FreeDOS at all, despite it was installed on VirtualBox flawlessly. Installation went well, no errors or warnings, and after the final reboot I got blank black screen with no reaction to any input, only power button could help. It seems it was fixed with another options used while partitioning the disc, but I’m not sure what certain option did the job. But after all I still see some strange behavior in just installed system. If I choose default second option in startup menu (Load freeDOS with EMM386+EMS and SHARE), the screen gets filled with error message, and I still see no reaction on keyboard or trackpad. Screen looks like this. Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: Bad or missing command interpreter: ÉÉÉ Enter the full shell command line: The other strange thing is that first (Load FreeDOS with EMM386, no EMS (most UMBs), max RAM free) or third (Load FreeDOS including HIMEM XMS-memory driver) option in startup menu works normally, as I see (not investigated seriously, but at least it looks so). Fourth option can’t be chosen at all. So as I’m new to this kind of OS I ask where can I read about this problem with second menu option and how can I try to fix it, if it’s possible? Just for now I’ve edited fdconfig.sys to hide menu and use the third option by default, but it doesn’t look like a good solution. What kind of hardware info may be helpful for solving this problem? Thanks! -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct___ Freedos-user mailing list
Re: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s
Em 18-10-2011 22:34, Rugxulo escreveu: On Tue, Oct 18, 2011 at 5:56 PM, Alain Mouetteala...@pobox.com wrote: Em 18-10-2011 20:33, Rugxulo escreveu: BTW, call me naive, but does that above line even give you any UMB space?? If not (and NOEMS), why use EMM386 at all?? (Just use XMS.) :-/ Other things did not work anly with XMS, among other things emm386 puts the machine in protected mode, this helped something... Eh? That would be weird. Hmmm, now that I think about it, I think CWSDPMI (and/or other DPMI hosts) can't handle fragmented XMS (or hog it all for themselves), so shelled out apps don't have anything to use. Perhaps you're relying on that? In that case, yes, the 4 kb pages help, oddly enough. Otherwise it's not so recommended (esp. since EMS isn't as widely used in most modern DOS apps), as you probably already know, esp. regarding DPMI 1.0 extensions and CWSDPMI r7. And es, you are right, it gave me no UMB, which in that situation is just a minor annoyance. My program is 32 bits so it does not need much lower memory. DJGPP, perhaps? If OpenWatcom, you could (should) try a different extender (DOS/32A or Causeway). I use OpenWatcom, with Causeway. I tried WDOSX and DOS4G but they were not as relyable as Causeway. I guess UMBPCI is out of the question?? Completly, it is hardware dependant and does not behave well on unknown hardware. I tried but could not find a range to exclude that worked and would leave me some UMB :( I find that hard to believe. Basicaly due to lack of time. It was kind of a emergency rescue... But luckily FreeDOS is pretty efficient anyways (at least with XMS available). :) Alain -- The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Ciosco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s
Hi, tocayo, ;-) On Tue, Oct 18, 2011 at 4:00 PM, Anton Vernigor smm...@gmail.com wrote: I’m trying to install FreeDOS (fdbasecd.iso) on a real (not virtual) machine for the first time, and I’ve met some problems. At first I couldn’t install FreeDOS at all, despite it was installed on VirtualBox flawlessly. Installation went well, no errors or warnings, and after the final reboot I got blank black screen with no reaction to any input, only power button could help. Must be MBR or boot sector issue. (Perhaps an FDISK bug??) It seems it was fixed with another options used while partitioning the disc, but I’m not sure what certain option did the job. fdisk /mbr perhaps?? But after all I still see some strange behavior in just installed system. If I choose default second option in startup menu (Load freeDOS with EMM386+EMS and SHARE), the screen gets filled with error message, and I still see no reaction on keyboard or trackpad. Screen looks like this. If you're using FreeDOS 1.0 (2006), you may want to upgrade your EMM386 to JEMM. http://www.freedos.org/software/?prog=jemm386 http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/emm386/jemm386/JEMM575B.zip http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/emm386/jemm386/JEMM575S.zip I suggest JEMM386 X=TEST I=TEST or similar (see its README.TXT). The other strange thing is that first (Load FreeDOS with EMM386, no EMS (most UMBs), max RAM free) or third (Load FreeDOS including HIMEM XMS-memory driver) option in startup menu works normally, as I see (not investigated seriously, but at least it looks so). Sounds like an EMM386 bug. I know I don't speak for everybody, but I'll try anyways: nobody uses old EMM386, use new JEMM386.;-) Fourth option can’t be chosen at all. You can edit it by hand (if savvy enough). So as I’m new to this kind of OS I ask where can I read about this problem with second menu option and how can I try to fix it, if it’s possible? http://home.mnet-online.de/willybilly/fdhelp-dos/ N.B. to others, the news item has long ago scrolled off the main page, so we need to not forget to proofread this (FDhelp) one of these days! Just for now I’ve edited fdconfig.sys to hide menu and use the third option by default, but it doesn’t look like a good solution. What kind of hardware info may be helpful for solving this problem? Just upgrade to JEMM386 first, then we'll see. Though I would also suggest getting kernel 2040, but I don't think that specifically will fix anything here. http://sourceforge.net/projects/freedos/files/Kernel/2040/ke2040_86f32.zip/download http://sourceforge.net/projects/freedos/files/Kernel/2040/ke2040s.zip/download -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s
Thanks! Looks like it helped! I didn’t upgrade to kernel 2040 yet, but I’m going to do it soon. Is it possible to download and install some beta version? I often see mentions of 1.1 on the internet, but there is no link to download it from freedos.org, and I’m not brave enough to download it from unknown location. And I also have a problem with accessing my DVD drive, maybe I’ll fix it myself, or ask here again in a few days if nothing helps. Thanks again for your help. On 19 окт. 2011, at 00:20, Rugxulo wrote: Hi, tocayo, ;-) Just upgrade to JEMM386 first, then we'll see. Though I would also suggest getting kernel 2040, but I don't think that specifically will fix anything here. http://sourceforge.net/projects/freedos/files/Kernel/2040/ke2040_86f32.zip/download http://sourceforge.net/projects/freedos/files/Kernel/2040/ke2040s.zip/download -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s
= = W A R N I N G = = Em 18-10-2011 19:20, Rugxulo escreveu: If you're using FreeDOS 1.0 (2006), you may want to upgrade your EMM386 to JEMM. http://www.freedos.org/software/?prog=jemm386 http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/emm386/jemm386/JEMM575B.zip http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/emm386/jemm386/JEMM575S.zip I suggest JEMM386 X=TEST I=TEST or similar (see its README.TXT). JEMM is not a replacement of EMM386. I used it this year and lost many user's databases. Jemm is too much optimized an this is hardware dependent, it does not work alike on all machines. I reverted to EMM386 and everything is running smoothly again. I am responsible for just ove 100 (ONE hundred) DOS machines running 24/7 with heavy database usage. The other strange thing is that first (Load FreeDOS with EMM386, no EMS (most UMBs), max RAM free) or third (Load FreeDOS including HIMEM XMS-memory driver) option in startup menu works normally, as I see (not investigated seriously, but at least it looks so). Sounds like an EMM386 bug. I know I don't speak for everybody, but I'll try anyways: nobody uses old EMM386, use new JEMM386.;-) I use and it old stable and relyable. On 2 new machines (last+this month) I had problems with X=TEST, I made it work with EMM386 NOEMS X=C000-EFFF NODISABLEA20 NOVDS /VERBOSE this was apparently due to some periferal in UMB not detected Alain Fourth option can’t be chosen at all. You can edit it by hand (if savvy enough). So as I’m new to this kind of OS I ask where can I read about this problem with second menu option and how can I try to fix it, if it’s possible? http://home.mnet-online.de/willybilly/fdhelp-dos/ N.B. to others, the news item has long ago scrolled off the main page, so we need to not forget to proofread this (FDhelp) one of these days! Just for now I’ve edited fdconfig.sys to hide menu and use the third option by default, but it doesn’t look like a good solution. What kind of hardware info may be helpful for solving this problem? Just upgrade to JEMM386 first, then we'll see. Though I would also suggest getting kernel 2040, but I don't think that specifically will fix anything here. http://sourceforge.net/projects/freedos/files/Kernel/2040/ke2040_86f32.zip/download http://sourceforge.net/projects/freedos/files/Kernel/2040/ke2040s.zip/download -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s
Hi, On Tue, Oct 18, 2011 at 5:10 PM, Alain Mouette ala...@pobox.com wrote: = = W A R N I N G = = = = ACHTUNG = = Em 18-10-2011 19:20, Rugxulo escreveu: If you're using FreeDOS 1.0 (2006), you may want to upgrade your EMM386 to JEMM. I suggest JEMM386 X=TEST I=TEST or similar (see its README.TXT). JEMM is not a replacement of EMM386. I used it this year and lost many user's databases. Jemm is too much optimized an this is hardware dependent, it does not work alike on all machines. Nothing works the same on all machines, esp. since we all use various PCs from different OEMs. It could be a BIOS bug, your error, some other software error, etc. Let's not be too hasty to blame JEMM (or Japheth) as most of us use it without problems. Granted, if it doesn't work for you, don't use it. But a nice, clear bug report (or even patch) would be ideal. ;-) I reverted to EMM386 and everything is running smoothly again. I am responsible for just ove 100 (ONE hundred) DOS machines running 24/7 with heavy database usage. There were several bugs in that old version that Japheth has fixed. So really neither is perfect (what is?). I use and it old stable and relyable. Except when running spellcheck. ;-) On 2 new machines (last+this month) I had problems with X=TEST, I made it work with EMM386 NOEMS X=C000-EFFF NODISABLEA20 NOVDS /VERBOSE this was apparently due to some periferal in UMB not detected Did you use X=TEST alone or X=TEST I=TEST ?? I think he was going for more MS-like auto-detection there, which is why it's slightly different handling now. (And for instance, I think one of the big issues with old EMM386 was heavily incomplete [broken?] VDS.) BTW, call me naive, but does that above line even give you any UMB space?? If not (and NOEMS), why use EMM386 at all?? (Just use XMS.) :-/ -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s
Hi, On Tue, Oct 18, 2011 at 5:09 PM, Anton Vernigor smm...@gmail.com wrote: Is it possible to download and install some beta version? I often see mentions of 1.1 on the internet, but there is no link to download it from freedos.org, and I’m not brave enough to download it from unknown location. 1.1 isn't finalized as everybody is too busy, too few developers and volunteers. But you can grab test 1.1 #3 here (from News Archive post July 27 of this year): http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.1-test3/ It lacks a lot of stuff, pretty minimalist, but that's the idea. Anyways, you probably don't need most of it since a good portion is the same. And I also have a problem with accessing my DVD drive, maybe I’ll fix it myself, or ask here again in a few days if nothing helps. Try upgrading to these (though sadly all hardware is different): http://johnson.tmfc.net/dos/driver.html http://johnson.tmfc.net/dos/shsucdx.html -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s
Op 19-10-2011 0:33, Rugxulo schreef: BTW, call me naive, but does that above line even give you any UMB space?? If not (and NOEMS), why use EMM386 at all?? (Just use XMS.) :-/ On my real hardware, JEMM seems to have more succes initialising things while various XMS drivers and/or FreeDOS kernel hang. Likely some A20 thing, as DOS=LOW seems to work. I've got no idea what the cause or difference is, lacking time to research it. Someday I'll set up MSDOS as reference system to exclude FreeDOS kernel/shell as cause. Loading an XMS driver after autoexec.bat has been processed, is possible ofcourse, but still a waste of low memory (primary shell can't reload, nor kernel system data). Anyway, if Alain can afford to experiment with JEMM (and is willing to), by all means go for it. For now though, never change a winning system. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s
I had already told Eric that this was useless... Alain Em 18-10-2011 20:33, Rugxulo escreveu: Hi, On Tue, Oct 18, 2011 at 5:10 PM, Alain Mouetteala...@pobox.com wrote: = = W A R N I N G = = = = ACHTUNG = = Em 18-10-2011 19:20, Rugxulo escreveu: If you're using FreeDOS 1.0 (2006), you may want to upgrade your EMM386 to JEMM. I suggest JEMM386 X=TEST I=TEST or similar (see its README.TXT). JEMM is not a replacement of EMM386. I used it this year and lost many user's databases. Jemm is too much optimized an this is hardware dependent, it does not work alike on all machines. Nothing works the same on all machines, esp. since we all use various PCs from different OEMs. It could be a BIOS bug, your error, some other software error, etc. Let's not be too hasty to blame JEMM (or Japheth) as most of us use it without problems. Granted, if it doesn't work for you, don't use it. But a nice, clear bug report (or even patch) would be ideal. ;-) I reverted to EMM386 and everything is running smoothly again. I am responsible for just ove 100 (ONE hundred) DOS machines running 24/7 with heavy database usage. There were several bugs in that old version that Japheth has fixed. So really neither is perfect (what is?). I use and it old stable and relyable. Except when running spellcheck. ;-) On 2 new machines (last+this month) I had problems with X=TEST, I made it work with EMM386 NOEMS X=C000-EFFF NODISABLEA20 NOVDS /VERBOSE this was apparently due to some periferal in UMB not detected Did you use X=TEST alone or X=TEST I=TEST ?? I think he was going for more MS-like auto-detection there, which is why it's slightly different handling now. (And for instance, I think one of the big issues with old EMM386 was heavily incomplete [broken?] VDS.) BTW, call me naive, but does that above line even give you any UMB space?? If not (and NOEMS), why use EMM386 at all?? (Just use XMS.) :-/ -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s
Usefull part bellow: Em 18-10-2011 20:33, Rugxulo escreveu: On 2 new machines (last+this month) I had problems with X=TEST, I made it work with EMM386 NOEMS X=C000-EFFF NODISABLEA20 NOVDS /VERBOSE this was apparently due to some periferal in UMB not detected Did you use X=TEST alone or X=TEST I=TEST ?? I think he was going for more MS-like auto-detection there, which is why it's slightly different handling now. (And for instance, I think one of the big issues with old EMM386 was heavily incomplete [broken?] VDS.) BTW, call me naive, but does that above line even give you any UMB space?? If not (and NOEMS), why use EMM386 at all?? (Just use XMS.) :-/ Other things did not work anly with XMS, among other things emm386 puts the machine in protected mode, this helped something... And es, you are right, it gave me no UMB, which in that situation is just a minor annoyance. My program is 32 bits so it does not need much lower memory. I tried but could not find a range to exclude that worked and would leave me some UMB :( Alain -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Problem with running FreeDOS on HP Compaq 6720s
Hi, On Tue, Oct 18, 2011 at 5:56 PM, Alain Mouette ala...@pobox.com wrote: Usefull part bellow: Cooll ... Em 18-10-2011 20:33, Rugxulo escreveu: BTW, call me naive, but does that above line even give you any UMB space?? If not (and NOEMS), why use EMM386 at all?? (Just use XMS.) :-/ Other things did not work anly with XMS, among other things emm386 puts the machine in protected mode, this helped something... Eh? That would be weird. Hmmm, now that I think about it, I think CWSDPMI (and/or other DPMI hosts) can't handle fragmented XMS (or hog it all for themselves), so shelled out apps don't have anything to use. Perhaps you're relying on that? In that case, yes, the 4 kb pages help, oddly enough. Otherwise it's not so recommended (esp. since EMS isn't as widely used in most modern DOS apps), as you probably already know, esp. regarding DPMI 1.0 extensions and CWSDPMI r7. And es, you are right, it gave me no UMB, which in that situation is just a minor annoyance. My program is 32 bits so it does not need much lower memory. DJGPP, perhaps? If OpenWatcom, you could (should) try a different extender (DOS/32A or Causeway). I guess UMBPCI is out of the question?? I tried but could not find a range to exclude that worked and would leave me some UMB :( I find that hard to believe. But luckily FreeDOS is pretty efficient anyways (at least with XMS available). -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
