Hello Simon, Hello Jim, Hello FreeDOS developers, today i was just in attempting of doing the trick for installing FreeDos 1.0 from the official "full" CD ISO image into a VMware image.
That far the installer has the habit of growing the harddisk image to its maximum size on install. Thus the 8 GB default was not that desireable. Thus reconfigured my player to only offer 300 MB and it now looks like the installer is behaving nicer. Backside: this first harddisk will not be able to grow. Whats else is worth a note for the install? - no mouse support for the installer (always needed hooking in the keyboard to the session) - a distinct query for any package category (barely an unattended install) - BIOS setting on new VMware placed harddisk in front of CD drive for boot (but might be specific to my setup activity) - ip configuration failed at DHCP (might be any reason, from NAT/Bridge mode of VMware to own LAN) - gem clone asked some extra questions after the install i hat 99 MB free. sufficient. but the session hooked up with emm386 and opcode failures. switching to the next best boot option fixed that for me. And then i tried out this: - arachne web browser offered up to 1024x768 resolution but was not able to get a connection, probably due to missing IP config - the GEM gui ran but resolution was not that impressing, gem post-config scripts failed and lots of them were put into c:\ playing around with exchangeable media showed me that VMware floppys are unformatted on startup even if FreeDos allows labeling on thos bare media. helpful floppy image editing tools were WinImage and magicISO. a few traps and config options later i went to the nicscan info program and to the mTCP suite. further i added volkov commander (getting its 10 years aniversary of no-releases soon but still works very nice. only FreeDos alias definitions seemngly wont work from its shells.) seeing a higher versioned packet driver for the vmware AMD PCnet32 hardware emulation from Georg Potthast (having further pcnetodi) made me put this as a packet driver into the virtual machine setup. after switching VMware back to NAT suddenly the DHCP, DNS and ping commands worked from the commandline (part of mTCP). so i gave arachne a second chance - and voila even that worked for me. having my install now "damaged" a bit and not having done a "clean" freeze after first startup (due to a bit lack of my main harddisk) tells me i should not publish that result to the world since its a bit too altered now. That far that good. Just wanted to share my observations as they might be of some help for you and other people. regards, Alex. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
