I am having great success with both eCS 1.2R and also Warp 4.52, so I think it odd that Warp 4 is giving me a fight.
My host OS is Ubuntu 8.04. I have been using the 2232 build.
The specs can be found here:
http://www.lueckdatasystems.com/OS2_eCS_eComStation_Preloaded_Workstation_Computer
I found mention of a 2234 build, so I found a link to download that version and tried it as well. (Purged the old package, installed the new one, and tested booting my previously created VM.) Same crash, so here are the details when running 2234:
1) Transfered the DSK files for the boot process to the Linux filesystem, renamed them from .DSK to .FDD, and they work beautifully as Parallels FDD images!
2) I updated the IBM1S506.ADD and IBMIDECD.FLT to the version that eCS 1.2R installed, removed un-needed drivers from CONFIG.SYS, Added COPYFROMFLOPPY=1, and commented out the extra snoopers in the SNOOP.LST file. (I booted an eCS 1.2R VM session, mounted the FDD image, and found that I can make changes to the FDD images that are saved to the FDD file!)
3) I created an ISO of the Warp 4 CD with the CD unmounted, dd if=/dev/scd1 of=Warp4.ISO bs=2048
4) I make it through the text part of the install, reboot, and then when booting from the HDD it gets the attached trap 000d screen.
I have attached our customized disk1_cd.fdd and also a screen shot of the trap 000d screen.
Like I said, eCS 1.2R and Warp 4.52 are rock solid stable, so I find the fight that Warp 4 has put up most odd indeed.
Suggestions? TIA!
My host OS is Ubuntu 8.04. I have been using the 2232 build.
The specs can be found here:
http://www.lueckdatasystems.com/OS2_eCS_eComStation_Preloaded_Workstation_Computer
I found mention of a 2234 build, so I found a link to download that version and tried it as well. (Purged the old package, installed the new one, and tested booting my previously created VM.) Same crash, so here are the details when running 2234:
1) Transfered the DSK files for the boot process to the Linux filesystem, renamed them from .DSK to .FDD, and they work beautifully as Parallels FDD images!
2) I updated the IBM1S506.ADD and IBMIDECD.FLT to the version that eCS 1.2R installed, removed un-needed drivers from CONFIG.SYS, Added COPYFROMFLOPPY=1, and commented out the extra snoopers in the SNOOP.LST file. (I booted an eCS 1.2R VM session, mounted the FDD image, and found that I can make changes to the FDD images that are saved to the FDD file!)
3) I created an ISO of the Warp 4 CD with the CD unmounted, dd if=/dev/scd1 of=Warp4.ISO bs=2048
4) I make it through the text part of the install, reboot, and then when booting from the HDD it gets the attached trap 000d screen.
I have attached our customized disk1_cd.fdd and also a screen shot of the trap 000d screen.
Like I said, eCS 1.2R and Warp 4.52 are rock solid stable, so I find the fight that Warp 4 has put up most odd indeed.
Suggestions? TIA!