last updated at 23 Dec, 2006 18:09 (1 times)
Doug_M (22 Dec, 2006 11:22):
I'm having problems installing Warp 4 on my thinkpad 390E. I have the updated install disk 1 and 2. Regardless, the install always fails at disk 2 where is says "loading system files. please wait...".
Installing W4 Merlin into a TP600e caused similar problems some years back. Like yourself, I downloaded the "updated" diskettes from an IBM site; memory is short, I can not recall the URL.
Notwitstanding, I re-updated my downloaded diskettes with the IBM provided file IDEDASD.EXE --that version from around 2002. Do a search for the file in the internet. Please follow the instructions and rename the file DASD16.DMD to OS2DASD.DMD; disregard the file DASD32.DMD since it is to be used with WSEB (Aurora) only.
Doing a quick search in my archive of oldie stuff, I located the two floppies that I used back then. I will upload them and provide you with a link and password --when OS/2 is open sourced and meritocracy rules its development and not "ownership" of the code, I will not have to do this anymore.
Notwithstanding, if you decide to download the diskette images that I made with the utility SAVEDSKF.EXE, please use LOADDSKF.EXE to place the contents into your appropriately labeled diskettes.
Additionally, please understand thay although today I tested the images under VirtualPC/2 and they executed correctly, you download them at your own risk and I do not make explicit and/or implicit warranty that those images will even perform satisfactorily in your system.
With those issues behind and if you still decide to download the images, here is how you uncompress them:
LOADDSKF.EXE OS2W4D1.DSK A:
and
LOADDSKF.EXE OS2W4D2.DSK A:
assuming, of course that your floppy drive is your drive A:
Pleas make sure that your BIOS is set to support floppy, in some Thinkpads you have to explicitely select the floppy support (even if emulated) otherwise the OS/2 booting process will stop somewhere along the way.
If everything goes correctly, you should see the following:
Merlin Initial
Insert diskette 2
..Loading
Insert your CDROM
Additionally, if you are not successful, you may want to add the parameter below in the Config.sys of your diskette 1 to force the floppy. Some of those machines had some issues that were resolved thus.
To your floppy statement in your config.sys that reads like this:
BASEDEV=IBM1FLPY.ADD
Add the following so that it now will read like:
BASEDEV=IBM1FLPY.ADD /FORCE:1 /U:0 /F:1.44MB
Best of Luck
!