Re: [Freedos-user] FD 1.0 installation... very instable?
Am 02.08.11 04:08, schrieb e.a...@jpberlin.de: >> - network >> its a 3c905b. It should work using the NDIS driver included with > > That 3com series sounds classic, so I assume there will be a > direct packet driver on crynwr which does not need NDIS/ODI. Found a packet driver for the 3c905b-c family. Perhaps you like to try it? See: http://lazybrowndog.net/3c90xpd -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FD 1.0 installation... very instable?
Hi, On Tue, Aug 2, 2011 at 12:58 PM, Bernd Blaauw wrote: > Op 2-8-2011 4:08, e.a...@jpberlin.de schreef: >>> - install Freedos 1.1T3 > >>> Ran through in almost no time, wow! >>> I got the same error message from Jemm, but pressing ESC continued >>> booting the installer. >> >> Still sounds evil. I hope the installer can work without JEMM. > > This is actually JEMM reporting FreeDOS KEYB 2.0 crashing. I assume this is the KPDOS 2.6 vs. KEYB 2.0 bug I reported. (I suggest reverting to 2.5.) Or maybe it's something different. Whatever, it's August now, so maybe Aitor has more free time! ;-) > (networking is confusing) > (networking is still confusing) > (networking is still still confusing) Networking is confusing!!^_^ -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FD 1.0 installation... very instable?
Op 2-8-2011 4:08, e.a...@jpberlin.de schreef: >> - install Freedos 1.1T3 >> Ran through in almost no time, wow! >> I got the same error message from Jemm, but pressing ESC continued >> booting the installer. > > Still sounds evil. I hope the installer can work without JEMM. This is actually JEMM reporting FreeDOS KEYB 2.0 crashing. >> - network >> its a 3c905b. It should work using the NDIS driver included with >> Barts >> Network Boot Disk. Does it work with freedos out of the box or do I >> have >> to do this manually using this wiki page? > > That 3com series sounds classic, so I assume there will be a > direct packet driver on crynwr which does not need NDIS/ODI. Networking is a pain in DOS. Wired Network Interface Cards connected to motherboard through ISA or PCI interface will likely work. In most cases only drivers for the Novell stack (IPX/SPX, ODI ) and Microsoft TCP/IP , NDIS, MS-Client , SMB) seem to be available. Shim drivers exist to convert this to packet driver which most simple DOS networking programs understand. However I'm not sure if complete stacks have to be installed before the shims work or not (as neither the Novell nor MS stacks are freely distributable) Pure packet drivers for network cards seem hardly to exist. A 'universal UNDI packet driver' has existed but was a commercial product from a company named Emboot, no longer in existance. I'm currently experimenting with iPXE as a bootloader for starting FreeDOS installation. Already have it working, and it might support more network cards than normal dos packet drivers. > Bart and Veder have some network boot disks on that topic. and the 'http://reboot.pro' forums as well (formerly BootLand). -- BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FD 1.0 installation... very instable?
Hi JPT, > - freedos 1.1 successfully installed. Nice :-) > Was 3x128 + 1x256 = 640, but recognized only 384 MB. This might... Indeed odd. > - CPU clock rate too high for a lot of old dos software? > Do you think clocking down to below 500 Mhz might help? If your hardware supports ACPI, starting from newer socket 7 / pentium 3 afair, you can use FDAPM SPEEDn where n is a digit to throttle the system a bit. This halts the CPU and/or clock for N our of 8 time slices in hardware (e.g. 1/32768 seconds long) but for fast systems, it will just make games jumpy, not smoothly reduce the speed. Also, strong throttle makes things behave sluggish as it hinders timely IRQ handling. More modern methods such as reduction of clock and voltage together are not supported by FDAPM yet and often only allow a few speed steps. For example AMD cool n quiet might support only 100%, 80% and 40%. More old methods such as single stepping through all code can have compatibility problems and will waste a lot of CPU performance and energy in general... In the modern virtual computer case, you sometimes simulate the whole CPU anyway, so you already do waste host CPU performance but can use any speed. > Bart says so for his network boot floppy. Odd suggestion though ;-) > - A20 stuff... > especially the XMS/EMS driver loading seems to fail often. > I have in mind that A20 has to do something with EMS oder XMS or UMB? A20 only has to do with HMA, DOS=HIGH and with XMS. Many EMS drivers permanently switch the A20 on, or at least keep it on (should be default set by BIOS during boot) and then just simulate A20 switching. Also, switching off the A20 is only needed for some obscure old software while not accessing HMA, so if you have to revert to a setting (HIMEMX has quite many) which "solves" the A20 problem by keeping the A20 always on, you should be fine nevertheless. I agree that apart from XMGR, HIMEMX and similar can be an alternative. Try NOT to load any EMS / UMB driver (JEMM386, EMM386 etc) before you solve the XMS / HMA problem (HIMEM, XMGR...). A special case is JEMMEX which combines both "HIMEM" and "EMM386" in one driver, so you should NOT load HIMEM / XMGR before JEMMEX, or at least need not load them 1st. > And, A20 is some hack using the keyboard controller. > Since I attached an USB keyboard to a USB switch, for easily > switching > between computers... could this be a problem The USB itself no, but the fact that the BIOS tries to make the USB keyboard look like PS/2 by faking some keyboard controller activities, maybe yes... > - This time I partitioned and formatted the drive before booting the > installer. Very good idea and works well with GPARTED and other tools. > btw, the fdisk program contained on the floppy sucks. I agree, it mainly tries to look and feel like MS FDISK. > created a bad partition layout. have to move partitions now... > what about xfdisk instead? XFDISK is an idea :-) > - install Freedos 1.1T3 > Ran through in almost no time, wow! > I got the same error message from Jemm, but pressing ESC continued > booting the installer. Still sounds evil. I hope the installer can work without JEMM. > So where do you suggest to continue? Should I jump to the 1.0 > installer? If you want a big pile of software, you can manually unzip more packages from the 1.0 CD-ROM into your DOS directory, or use a more elegant "package install or update" tool which does almost the same but in addition automatically checks dependencies and runs post install batch scripts (not many packages use those). > or should I install manually? Could you point me to a tutorial for > manual install, or is it just "unpack anywhere", as we are used Basically yes, but it is often better to unpack things from the distro into the same DOS directory and keep the subdirectories structured the way they are in the zip files. > - network > its a 3c905b. It should work using the NDIS driver included with > Barts > Network Boot Disk. Does it work with freedos out of the box or do I > have > to do this manually using this wiki page? That 3com series sounds classic, so I assume there will be a direct packet driver on crynwr which does not need NDIS/ODI. The freedos.org page also links nice pages about networking. > > http://sourceforge.net/apps/mediawiki/freedos/index.php?title=Networking_FreeDOS_-_NDIS_driver_installation > > Which cards are known to be working? Got a few Realtek based > somewhere... Classic NE2000 compatible RTL80x9 and 100mbit/s RTL8139 cards work nicely with DOS drivers and the PCI config is plug n play for the driver. Not plug and play in the sense that DOS will automatically find the driver for you, just in the sense that the driver needs almost no command line options :-) > - pascal compiler freepascal, 32 bit, available for dos > - maybe basic compiler or interpreter freebasic, 32 bit, compiles, available for dos, has qbasic mode. > - maybe fortran compiler, if the old software has to be r
Re: [Freedos-user] FD 1.0 installation... very instable?
Hi, quick reply, On Sat, Jul 30, 2011 at 10:05 AM, JPT wrote: > > Rugxulo, you are right, I should do this in a more structured way. > expected to throw the CD in, and thats it. > > EDIT: current status is: > - hardware ok, maybe the memory was faulty, i have to verify this. > - freedos 1.1 successfully installed. > - Debian installer is currently downloading addtional packages. > next steps, as soon as debian is working: > - install additional dos packages > - make network work > > Details of what I have done yet: > > hardware > > - CPU and board should be rocking stable, had XP running for years > without probs. Sounds good. > - memory... > Was 3x128 + 1x256 = 640, but recognized only 384 MB. This might indicate > a problem. Removed all but 1x128 MB. Memtest runs fast now, > 20 mins for 2 passes. Everything ok. > I will reinsert and check some of the other memory modules later. > (I did memtest before without error, but who knows...) Hope no problems there, but lacking any reason to worry, I guess it's fine. ;-) > - disk, ontrack is running, 2h. > No error. Does this computer's BIOS need it?? Shouldn't it be new enough to not need it? (Well, I just blindly assume you know otherwise.) > I have my rescue floppies and CDRWs always at hand, but the labels > aren't matching the content any more, for most of them :) Yeah, I have too many (usually unlabeled) floppies, heheh. ;-) > - CPU clock rate too high for a lot of old dos software? > Do you think clocking down to below 500 Mhz might help? > Bart says so for his network boot floppy. Hard to imagine for "normal" stuff, but it depends. Some games are pickier than others. Other stuff (TP7 unpatched) might also complain. > - A20 stuff... > especially the XMS/EMS driver loading seems to fail often. It shouldn't. At least XMS should "just work". EMM386 is quirky, so I'm not too too surprised there. > I have in mind that A20 has to do something with EMS oder XMS. (or UMB?) > And, A20 is some hack using the keyboard controller. > Since I attached an USB keyboard to a USB switch, for easily switching > between computers... could this be a problem, eg in the BIOS USB > Keyboard code? It could indeed be a USB keyboard / BIOS conflict. Try unplugging it (if you can) and seeing if that helps. > Now to the software. > - This time I partitioned and formatted the drive before booting the > installer. > btw, the fdisk program contained on the floppy sucks. I assume you mean FD FDISK 1.31? A la "looks like classic MS" one? > created a bad partition layout. have to move partitions now... What exactly does that mean? You had a pre-existing one that it corrupted? (I hope we're using "latest" 1.31 here.) TestDisk can sometimes recover lost partitions. Otherwise, we might need to add a tool to backup the MBR / partition table before mucking with it. (IIRC, both WDE and BOOTMGR can do so if you tell them to manually.) > what about xfdisk instead? Already in the works (right, Bernd?). There's also SPFDISK, which is allegedly better for SATA, but that one's SF site seems to have disappeared. > - Install debian... for having less trouble with partitioning in the > future, and to verify the hardware. Sounds good, you don't need to hog the whole drive with FreeDOS anyways. ;-) > - install Freedos 1.1T3 > Ran through in almost no time, wow! Yeah, it's not including everything and the kitchen sink (for now), just the basics. > I got the same error message from Jemm, but pressing ESC continued > booting the installer. I do wonder what is being used there. Hopefully "X=TEST I=TEST" in particular. We've got to be careful on newer computers, might even want to do "X=E000-EFFF". (Ideally, there should be a "safe" and/or "no EMS" option in CONFIG.SYS.) > So where do you suggest to continue? Should I jump to the 1.0 installer? > or should I install manually? Manually is fine if you can workaround the partition issues you mentioned. > Could you point me to a tutorial for > manual install, or is it just "unpack anywhere", as we are used from old > dos? fdisk (create FAT on primary active partition) format sys a: c: install whatever else you want / need > - network > its a 3c905b. It should work using the NDIS driver included with Barts > Network Boot Disk. Does it work with freedos out of the box or do I have > to do this manually using this wiki page? > http://sourceforge.net/apps/mediawiki/freedos/index.php?title=Networking_FreeDOS_-_NDIS_driver_installation Most likely manually. Ugh, all that networking stuff is extremely confusing (to me), but hopefully someone else here can guide you better. But try this packet driver: http://www.crynwr.com/drivers/ http://www.crynwr.com/drivers/3c509116.zip > Which cards are known to be working? Got a few Realtek based somewhere... Pretty much whatever Crynwr has (see above). > Regarding your other questions. > >> "Production" meaning what? Dunno, not sure it's been verified for >> military use. ^_^ > > well, w
Re: [Freedos-user] FD 1.0 installation... very instable?
Op 30-7-2011 17:05, JPT schreef: > Was 3x128 + 1x256 = 640, but recognized only 384 MB. This might indicate > a problem. Removed all but 1x128 MB. Memtest runs fast now, > 20 mins for 2 passes. Everything ok. > I will reinsert and check some of the other memory modules later. > (I did memtest before without error, but who knows...) Not all memory modules are created equally indeed, layout and chip density matters a lot. > > - disk, ontrack is running, 2h. > No error. > I have my rescue floppies and CDRWs always at hand, but the labels > aren't matching the content any more, for most of them :) Typical hehe. What's this Ontrack thing you're running? Hope it's not that crappy 'disk drive overlay' software that was used ages ago to have system BIOS work together with harddisks that had a relatively huge capacity. > - CPU clock rate too high for a lot of old dos software? > Do you think clocking down to below 500 Mhz might help? > Bart says so for his network boot floppy. No idea. Shouldn't matter much unless running into some Pascal programs that haven't been fixed yet, or in programs speeding up whenever the CPU is more powerful. > - A20 stuff... > especially the XMS/EMS driver loading seems to fail often. > I have in mind that A20 has to do something with EMS oder XMS. (or UMB?) > And, A20 is some hack using the keyboard controller. > Since I attached an USB keyboard to a USB switch, for easily switching > between computers... could this be a problem, eg in the BIOS USB > Keyboard code? A20 was keyboard hardware related but typically it's used whenever providing extended memory, while also unlocking 64 kilobytes of HMA, often best used by DOS=HIGH in config.sys. As I've experienced issues earlier with that, you could try DOS=LOW. Other options might be performing a clean boot, and either skip loading memory driver, or load it from commandline: DEVLOAD XMGR.SYS or JEMMEX.EXE LOAD > btw, the fdisk program contained on the floppy sucks. > created a bad partition layout. have to move partitions now... > what about xfdisk instead? If you really have a Disk Overlay program running (Ontrack, Compaq stuff etc) then that might explain a lot. There's always some Linux bootCDs like Parted Magic for example. Maybe UltimateBootCD (UBCD) is of help as well. > - Install debian... for having less trouble with partitioning in the > future, and to verify the hardware. Good step. I wonder if a Win98 bootdisk gives you the same issues as the FreeDOS one does (provided it contains FDISK in the first place) > - install Freedos 1.1T3 > Ran through in almost no time, wow! It's a small disk still. Glad it works mostly for you. > I got the same error message from Jemm, but pressing ESC continued > booting the installer. > So where do you suggest to continue? Should I jump to the 1.0 installer? > or should I install manually? Could you point me to a tutorial for > manual install, or is it just "unpack anywhere", as we are used from old > dos? Do what you think it's best. It's rather complicated to explain stuff from this point on as the FD1.0 installer might ruin FD1.1 settings and files, and lacks a lot of flexibility that I've added recently. You'll have to find the INSTALL.EXE in D:\FREEDOS\SETUP\INSTALL\ and find out it's options. Could swear I had a batchfile somewhere for that, but oh well. -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FD 1.0 installation... very instable?
Rugxulo, you are right, I should do this in a more structured way. expected to throw the CD in, and thats it. EDIT: current status is: - hardware ok, maybe the memory was faulty, i have to verify this. - freedos 1.1 successfully installed. - Debian installer is currently downloading addtional packages. next steps, as soon as debian is working: - install additional dos packages - make network work Details of what I have done yet: hardware - CPU and board should be rocking stable, had XP running for years without probs. - memory... Was 3x128 + 1x256 = 640, but recognized only 384 MB. This might indicate a problem. Removed all but 1x128 MB. Memtest runs fast now, 20 mins for 2 passes. Everything ok. I will reinsert and check some of the other memory modules later. (I did memtest before without error, but who knows...) - disk, ontrack is running, 2h. No error. I have my rescue floppies and CDRWs always at hand, but the labels aren't matching the content any more, for most of them :) - CPU clock rate too high for a lot of old dos software? Do you think clocking down to below 500 Mhz might help? Bart says so for his network boot floppy. - A20 stuff... especially the XMS/EMS driver loading seems to fail often. I have in mind that A20 has to do something with EMS oder XMS. (or UMB?) And, A20 is some hack using the keyboard controller. Since I attached an USB keyboard to a USB switch, for easily switching between computers... could this be a problem, eg in the BIOS USB Keyboard code? Now to the software. - This time I partitioned and formatted the drive before booting the installer. btw, the fdisk program contained on the floppy sucks. created a bad partition layout. have to move partitions now... what about xfdisk instead? - Install debian... for having less trouble with partitioning in the future, and to verify the hardware. - install Freedos 1.1T3 Ran through in almost no time, wow! I got the same error message from Jemm, but pressing ESC continued booting the installer. So where do you suggest to continue? Should I jump to the 1.0 installer? or should I install manually? Could you point me to a tutorial for manual install, or is it just "unpack anywhere", as we are used from old dos? - network its a 3c905b. It should work using the NDIS driver included with Barts Network Boot Disk. Does it work with freedos out of the box or do I have to do this manually using this wiki page? http://sourceforge.net/apps/mediawiki/freedos/index.php?title=Networking_FreeDOS_-_NDIS_driver_installation Which cards are known to be working? Got a few Realtek based somewhere... Regarding your other questions. > "Production" meaning what? Dunno, not sure it's been verified for > military use. ^_^ well, we are still using an old 486 with DOS 5 for some special hardware and software (which partly was ported from apple II a long time ago) since the 14" monitor broke down yesterday and the 200 MB harddrive broke down half a year ago... we have to go to slighly newer hardware that is able to run at least a linux, and has got some interfaces for backup. > It would also help to know what big apps you've tried (or primarily > want) to run, just to know what you expect to work. I need: - pascal compiler - maybe basic compiler or interpreter - maybe fortran compiler, if the old software has to be recompiled - network would be nice - some basic linux tools, eg vim, df, du, dd, wget... > EDIT: Oh yeah, you'd need working network, that's kinda arcane. But if > it works (by some miracle) ehm, so network won't work?:( Well, so far for now. I continue with debian install... Thanks for all that help! JPT -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FD 1.0 installation... very instable?
> I try to install Freedos good, but what exactly ??? > on a P3-800, Asus Cubx board, Intel i440BX > chip, 384MB of RAM. And I am frustrated by now Excellent BUG report :-( > I got about 30 crashes. 1.0 distro is obsolete, overloaded and buggy ... > Is it wise to uses freedos 1.0 for production environment? YES, if you care to tune it, or even better, get kernel 2040 and other updates. > May I use FAT32 for primary partition? YES (only 28 bits used). -- ~~~ wow ~~~ -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FD 1.0 installation... very instable?
At the risk of being redundant, I'll add some comments here: On Sat, Jul 30, 2011 at 4:48 AM, JPT wrote: > > You have to subscribe to this list, to be able to post? > Ok, I did so and sent my email again... > > I try to install Freedos on a P3-800, Asus Cubx board, Intel i440BX > chip, 384MB of RAM. And I am frustrated by now. :( Sounds like a good setup. Sorry you've had troubles, though. Hardware is annoying sometimes. :-( EDIT: Dare I ask, but what OS did this machine run originally? Win98? WinXP? Have you tried any others lately (Haiku, Linux)? > I got about 30 crashes. Whoa, that's way too many, that's not normal. You probably made a few mistakes (or ran into a few corner cases). I don't think that's ideal, so you can probably minimize most (all?) of that with careful planning. > I was able to solve some of them, but... > If the install is that instable, what about the system? > Is it wise to uses freedos 1.0 for production environment? "Production" meaning what? Dunno, not sure it's been verified for military use. ^_^ Anyways, to be honest, 1.0 is "old" (!), from 2006, so try upgrading to latest stuff (not quite 1.1 but very close). > May I use FAT32 for primary partition? else the drive will already be > heavily loaded after installation... Yes, FAT32 should work fine. > Crashes for example > - on installation bootup freecom loading crashes, if drive C is not > formatted. which prevents formatting... You're booting from CD, I presume? Basically, you need to "fdisk" (create active primary FAT partition), reboot, "format", "sys a: c:" (which copies kernel, command, and boot sector), and then add whatever. > - the floppy created from the installation menu does not boot at all (3 > dots is all i get) Probably just old versions. But also try F8 to minimize some things that may be causing problems. > - installation in oracle virtualbox seems not to be able to load the > network driver correctly. which hardware should I select in the VB config? I've not (yet) used VirtualBox with FreeDOS + networking, but I *think* AMDPD.ZIP is your friend here. > - installation crashes with some memory error while installing some > packages... Weird, shouldn't do that. Well, just try installing manually. And if you try again (not suggested, but ...), please tell us the exact error message (or others). > Yes, I did successfully run memtest and harddrive tests. Good to know. > Do you have any idea how to successfully install Freedos? > Should I try the 1.1 installer? But the 1.1 iso image does not contain > all packages? Considering all the trouble you had, and considering that 1.1 test #3 is "latest", you should probably try that. Else just install manually. I almost want to suggest you just boot a minimal floppy to see how well that goes. It would also help to know what big apps you've tried (or primarily want) to run, just to know what you expect to work. > Is there something like a package manager, you may invoke after > successfull installation? In this case, I might try a minimal > installation, and install the other packages in several iterations... Yes, barely, but I'm not sure it's updated. At least I never used it. And the repo is outdated. I would suggest just manually adding what you want. But first try 1.1 test #3. Or not, who cares, it's your life. ;-) EDIT: Oh yeah, you'd need working network, that's kinda arcane. But if it works (by some miracle) > thank you very much :) Keep us posted. And do post precise error messages and details (if possible). (combining e-mails): >>> - installation in oracle virtualbox seems not to be able to load the >>> network driver correctly. which hardware should I select in the VB config? >> >> AMD PCNET or NE2000 likely, maybe the Intel card. I haven't got much >> experience with VirtualBox, sorry. > > I found a lot of docs on network. I start with Barts network bootdisk > now, to find a working driver. after that, I check Freedos networking again. "pcisleep l q02" (or something like that, I may be remembering incorrectly) and checking http://pciids.sf.net online should help. Or use "dmesg" under Linux. Or try Georg's NICSCAN. http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/system/pcisleep/ http://www.georgpotthast.de/sioux/packet.htm -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FD 1.0 installation... very instable?
Thanks for the quick answer. I ll try your suggestions. find a few comments on your answers below: Am 30.07.2011 12:08, schrieb Bernd Blaauw: >> - the floppy created from the installation menu does not boot at all (3 >> dots is all i get) > > I'll look into that. 3 dots usually means bootsector loads but can't > find kernel (kernel.sys) mh... seemed to me, it did not do anything except bootsector write on creating the floppy. ie, there is no kernel.sys >> - installation in oracle virtualbox seems not to be able to load the >> network driver correctly. which hardware should I select in the VB config? > > AMD PCNET or NE2000 likely, maybe the Intel card. I haven't got much > experience with VirtualBox, sorry. I found a lot of docs on network. I start with Barts network bootdisk now, to find a working driver. after that, I check Freedos networking again. JPT -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FD 1.0 installation... very instable?
Op 30-7-2011 11:48, JPT schreef: > You have to subscribe to this list, to be able to post? > Ok, I did so and sent my email again... Most mailinglists require so, or an administrator to approve messages before they show up. Some lists indeed accept mail from unsubscribed people. > I got about 30 crashes. > I was able to solve some of them, but... > If the install is that instable, what about the system? > Is it wise to uses freedos 1.0 for production environment? Strange that it's that unstable for you. > May I use FAT32 for primary partition? else the drive will already be > heavily loaded after installation... Ofcourse, use FAT32 as you please. Almost all programs succesfully work with it. > Crashes for example > - on installation bootup freecom loading crashes, if drive C is not > formatted. which prevents formatting... That's strange. > - the floppy created from the installation menu does not boot at all (3 > dots is all i get) I'll look into that. 3 dots usually means bootsector loads but can't find kernel (kernel.sys) > - installation in oracle virtualbox seems not to be able to load the > network driver correctly. which hardware should I select in the VB config? AMD PCNET or NE2000 likely, maybe the Intel card. I haven't got much experience with VirtualBox, sorry. > - installation crashes with some memory error while installing some > packages... Maybe a result of earlier non-loading memory managers? > Yes, I did successfully run memtest and harddrive tests. > > > Do you have any idea how to successfully install Freedos? > Should I try the 1.1 installer? But the 1.1 iso image does not contain > all packages? You can install using the FreeDOS 1.1 test3 ISO image, feedback is welcome. Installation afterwards of programs from FD1.0 should also be possible. If you've got 1 CD-drive, copy D:\FREEDOS\SETUP\ODIN\INSTALL.EXE to C: drive. Next insert FD1.0 disc and do a CDD D:\FREEDOS followed by C:\INSTALL > Is there something like a package manager, you may invoke after > successfull installation? In this case, I might try a minimal > installation, and install the other packages in several iterations... We've got a package manager (FDPKG/FDUPD) but I'm not sure it works. To my knowledge it depends on WATT32 WGET or CURL, instead of MTCP's HTGET.EXE or FTP.EXE > thank you very much :) You're welcome, I hope you've got more luck with the FreeDOS 1.1 test ISO. Generally the idea is to have a formatted C: drive before performing installation :) If you want to prepare the harddisk in a fast way, get the new 1.44MB floppy image, as it contains the needed FDISK/FORMAT/SYS tools to get a very basic FreeDOS working (after which the CD install should also work). Bernd -- Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
