|
From: Heiko Z. <he...@zu...> - 2003-08-12 15:07:40
|
Bruce Smith wrote: >>>However, I was bummed to find out that I cannot set the memory >>>to anything smaller than 32MB in VMware 4. :-( >>> >>> >>VMWare 3 complained too, but after the error message I could press OK >>again and it saved it. >> >> > >I haven't got VMware 4 to save it. It automatically changes it back to >32MB if I input anything smaller. > You can try to set the OS within VMware to MSDOS or something. I think VMware behaves differently then. >>>What's the minimum memory usage down to these days? >>> >>> >>Good question. >> >> > >The next time you test it, please let me know. I'm curious. > I think the lowest I got it working was 16 MB. Unfortunately you can set the memory in VMWare only in 4 MB increments and when I recall it correctly, it refused to boot with 12 MB >>>Also, copying the config files to a blank floppy is still broke. >>>I can take a look at it, if you're done with the boot script??? >>> >>> >>Yes I'm done with the boot script. >>The shell we currently use has a very limited "read" command. >> >> > >Does ash support functions? >The error message said it couldn't find the proc "ask_yes_no". > I don't know. >I have a delay before I can do much with this. My main development PC >blew a CPU yesterday. I don't think I've EVER seen a CPU go bad before, >in ANY PC I've ever seen! I'm amazed. This one even died while the >system was up and running (not powering up)! Good UPS conditioned power >too. It's not that old of a PC either. (1.7G P4) Strange ... > > That sucks ! cya Heiko |