Hey guys,
I'm trying to install OS/2 Warp 3 for the first time onto a 'blade retail' PC. (Intel 865 board, 2.8GHz P4, 80GB HDD, 512 DDR400 RAM)
After running through the installation floppies it loads the setup off the CD and then prompts about partitions.
NOW! I delete all partitions and then Warp 3 only picks up around 13GB of the drive. (Was less at first - around 8GB - Tried to update the HDD Drivers on stiffy)
If I try and partition the HDD on another OS/2 PC (Dell) I can partition it correctly (2 X 8GB partitions) but as soon as I try and install OS/2 Warp 3 on it on the Blade PC, it tells me the partition might be corrupt.
Any help guys? (I'm going to try and install OS/2 Warp 3 on another PC now to see if the floppies are faulty/outdated)
You must patch the installation diskettes and replace ibm1s506.sys and few other drivers by better ones. Go to Hobbes and download Daniela's drivers. With W3, perhaps, download some older versrions of the driver. AFAIK, you need to replace ibm1s506, os2dmd, ibmatapi and, perhaps os2cdrom drivers. The best thing to do is to download everything that belongs to selected version of the driver and patch everything you find in your config.sys and you have downloaded.
If you download some newer version then ibm1s506 can already include some of the drivers listed above. You will need to comment out the corresponding drivers from your config.sys. Check readme of the driver for details. Note also, that the new drivers are bigger and that they need not fit on your installation diskette. You can delete tedit (along with accompanying files) from the diskette, it is on the second diskette again. You can also delete SCSI drivers for HW you do not have in your machine.
W3 drivers are ususable with contemporary HDs. The know only LBA and are completely unprepared to big HDs. On the other hand, I run W3 with a 13 G Caviar without any problems long ago. With DANI drivers, of course :)
Hi,
The issue you're having does sound like a driver issue. I've got a Warp 3 install on a machine with a 250 GB hard disk, it is possible to make it work. But it takes quite a bit of trickery.
First, it is correct that you need to dump the ibm1s506.add and replace it with danis506.add (that is, presuming it is either a IDE or a SATA hard disk. If it is SCSI, it'll all depend on a few other things). There's also an update for os2dasd.dmd - you can use danidasd.dmd (search on Hobbes). I can't remember if you also need daniatapi.flt or not. I'm going from memory here, I'll have to take a look at that server to be sure.
A few other things. Warp 3's fdisk can't handle large hard disks. Use something like DFSee to create your partition. Also, for Warp 3 the boot partition must be within the first 1024 cylinders of the drive (I think that's what the limit on location is, I can't recall 100%, I admit I'm writing this reply from memory). Anyways, that does mean making your boot partition somewhat small (set it to be around 1 GB for boot and you should be okay). You can always make the rest of the drive another partition for data.
Another thing to remember - Warp 3 out of the box supports FAT and HPFS, you can also add other file systems such as Fat32 with the IFS driver for that. But, for your data partition - HPFS (which is your best choice out of those 3) does have a limit of 64 GB per partition, and I generally don't recommend an HPFS partition over 60 GB as I've had problems with HPFS partitions bigger then that. Since your HDD is an 80 GB, you'll end up with a couple of HPFS partitions for data. Not a huge deal, but something to be aware of.
Another point, if I recall correctly some of the later versions of the DANIS drivers didn't work with the early Warp 3 kernel. So you may have to put a newer kernel (if you can, pull the one off FP40) on your boot disks to make it work. You might also have to interrupt the install process after its stage "1" and boot back to a command prompt just to dump the newer kernel on to the hard disk (unless you're working with an updated install CD that you've made with something like Updcd, you'll likely end up with whatever kernel is on the original install CD)
Anyways, that should help a little. If you have a running copy of Warp 4, you might be best to just use Updcd to create an updated Warp 3 install CD. Then you not only get an install that might actually complete without having to nurse it the whole way through (I've got a build of Warp 3 somewhere with updated drivers), but you also get it on a bootable CD - no need for floppies!
Best of luck!
And additionally, find the SETCOPYFROMFLOPPY line and change the 0 (zero) to a 1 (one) so it copies the drivers from the floppies instead of the CD - otherwise, it will install the IBM drivers.
Also, to make things easier, you can rename the Dani driver to the same name as the IBM one...
simply rename danis506.add to ibm1s506.add and replace the old ibm1s506.add with it.
One other point, you will probably have to have the boot partition (and Boot Manager, if you are installing it) in the first 8GB of drive space.
The Daniatapi.FLT should not be needed for IDE drives...
I *think* you can replace the os2dasd.dmd/ibmdasd.dmd driver with the danidasd.dmd driver in the same fashion as you should for the ibm1s506.add driver (ie: rename the dani driver and replace the original with it).
I cannot recall if Warp 3 used ibmdasd.dmd or os2dasd.dmd - pretty sure they all use OS2DASD.DMD but an updated package (ie: newer drivers) is named IBMDASDx.
So, that gives you two routes... replace the dasd and ide drivers with the Dani ones by renaming the dani ones and copying over the originals (and changing the setcopyfromfloppy line) - or find the updated IBM drivers for both and install those.
Best,
Robert
Wow guys, thanks for all the info. I'll give it a go today and get back to you :)
Probably a stupid question, but here I go...
How do I go about the floppies that don't have enough space on them?
Edit: nvm, I found an article that specified that I can wipe some of the A* ADD drivers and disable them in the Config.sys
OK! I've patched the floppy disk with the danis506r185 driver coupled with the daniatapi040 driver because my CD-ROM wasn't working without it :)
(IDE 80GB HDD, IDE CD-ROM)
I use FDISK on another machine and partition the drive correctly (8GB for the primary, and 8GB for the logical - I need nothing more)
As soon as I try and install warp3 it tells met that FDISK encounters an error (Standard or advanced)
FDISK on the installation CD tells me I've got 33GB space in total.
Edit1: When I let OS/2 handle the partitions on it's own it creates a partition the site of 8032MB and gives a format error (Something about the size being greater than 35MB)
Edit2: But I can format the drive manually with the format utility on the cd... (Format c: /fs:hpfs)
Edit3: When trying to install now onto that partition I get an error "OS/2 Installation program does not recognize the file system on drive C"
Edit4: I've confirmed the command "SET COPYFROMFLOPPY=1" is the first entry in my config.sys on the installation floppies.
Edit5: I don't know what changed, but I can see my whole drive now :o But I'm still having the issue @ Edit1 (\OS2IMAGE_001 - Greater than 35MB primary partition exist - Formatting fixed disk)
Edit6: I've updated to danidasd144 as well, no change
to 5: Which HD driver are you using now? 185 is the latest version of the driver so that it need not work with W3, especially with W3 without fixpacks. 144 should be "old enough" to work with W3. Note that daniatapi 040 is also the newest version of the atapi driver, which works with danis506 ver. 185 and which DOES NOT work with older versions. If you use 144, you will need an odler version of the atapi driver, too. Also, in the old days existed idedasd (or so) driver, which might be needed for your IDE hdd and cd. Naturally, the Daniela's fashion of it. Check your config.sys whether it specifies such driver and if it does then search Hobbes.
The problems with format seem to be a result of using too new HW with too archaic operating system :) First, if the two partitions you have mentioned are intended for system and user data then you don't need such big system partition. 2 GB system is more than enough even for contemporary eCS. Even DOS should be able to operate and format a 2GB partition so that the 2 GB size could point to causes of problems more precisely. I recommend the following:
(1) Create a 2 GB partition for your operating system.
(2) Install.
(3) Create the data partition(s) from the installed operatiing system.
If you pass, you may experiment with upgrading. You will need FP-many. FP40 has been mentioned by Fahrvenugen. I am not an expert in W3 fixpacks. Between (2) and (3), download sfix41 from Hobbes (to avoid diskette orgies when installing a fixpack) and install the fixpack. You should be able to use more up to date drivers and system apps now.
Thanks for the reply. F.I.Y.
With the latest versions I actually get this far:
Advanced Installation -> Accept the Drive -> "WARNING: The OS/2 Installation program does not recognize the file system on drive C"
I just ignore that error and continue the installation.
It stops however at around 75% of the copying with an error: "The system cannot find the file specified."
I'm now using Dani1S506 v1.6.6 with daniatapi0314 & danidasd144. (Eldest I could find)
Now it complains about os2cdrom.dmd on startup and it doesn't find the CD-ROM drive...
OS/2 is tiresome! ???
Try jjscdrom.dmd, it's an enhanced os2cdrom. It is often used on eCS along with Daniela's drivers so that it should work. jjscdrom is in drivers/cdrom. Choose a version which comes from a similar time as your HD driver.
Charl, os/2 isn't tiresome :) You are trying to use a 15 years old version of the operating system with current HDs, CD and so on. Expect problems - and big problems :) That you were able to pass so far is a little miracle :) An example: try to install windows 98 on a similar HW.
I've tried jjscdrom.dmd with no success
Anything else? :-\
Hi Charl,
If you can wait a few days I will get out my Warp3 Connect boot disks that I modified to be able to boot with modern (about 2 year old now) hardware. I should be back at the office early next week so can get the disks then.
Going from memory you have to find the Dani drivers about three back from the latest ones and remove all reference to the ibmatapi.flt and ibmcd.flt from the config.sys. I think you also need to edit the snoop list but I will know for sure when I get my disks, actually only disk2 (the second disk).
ivan
I'm more than willing to wait Ivan, Thanks!
Hi,
Okay, I had some spare time last night, so I pulled out one of my spare computers and decided to try a "fresh" warp 3 install using the original CD and boot floppies that came with the box. No updated CD's... I documented my process. I'll note that it took several false-starts to figure this out.
First, a bit of information on this machine:
Its got an Asus board, P5GD1, with an Intel P4 - 3.0, the one with the hyper-threading
Its got a SATA drive with an 80 GB Western Digital.
Intel chipset in it, and 512 MG DDR RAM
Its not the latest speed-demon, but only about 4 years old.
The OS: OS/2 Warp 3 Connect, Red Spine on CD (the original IBM spring 1995 release)
I admit that I cheated a little bit. I used my Warp 4 CD (the one with the updated install stuff on it) to boot to a command line and then used FDISK to install - boot manager, plus a 1 GB primary partition on the drive, added the partition to BM and made it startable. Without having the partition on the drive already I doubt I would have been able to get the install to finish.
I also had a spare computer up and running to help with getting boot floppies fixed and stuff.
So here's what I went through.
1. Copied both install and disk 1 to spare floppies
I found that the install floppy just caused a boot-loop on my PC, so I:
2. Downloaded wfwin10.zip from Hobbes
3. Ran that against Disk 0 and 1
4. Downloaded idedasd.exe from service.boulder.ibm.com. This contains a number of needed update files for large hard disks.
ftp://service.boulder.ibm.com/ps/products/os2/os2ddpak_cur//idedasd.exe
5. Extracted IDEDASD.EXE into a directory
With files in IDEDASD:
6. Deleted dasd32.dmd (this one works on warp 4.52 and such, but won't work on Warp 3)
7. Renamed dasd16.dmd to os2dasd.dmd (this is the DMD needed for Warp 3!)
8. Copied os2dasd.dmd, ibm1s506.add, ibmatapi.flt, ibmidecd.flt, and os2cdrom.dmd to Disk 1
---Found I didn't have enough space on Disk 1. Made space - deleted the readme on that disk, also some of the unneeded .ADD files, removed reference to those ADD files in the config.sys on Disk 1. Copied the above files to Disk 1
9. downloaded Danis506.add Version 1.7.9, copied that to disk 1
You can find it here:
http://www.os2site.com/sw/drivers/ide/index.html
10. Edited the config.sys on disk REMed out ibm1s506.add, added BASEDEV=DANIS506.add
11. Added SET COPYFROMFLOPPY=1 to config.sys on disk 1
12. Booted to disk 0, disk 1, ran through Advanced installer
13. After advanced installer Part 1 finished (the text screen installer), it would not boot (just loop booted)
14. Booted with floppies again to get to the install text screen, used F3 to get to a command prompt
15. Used attrib -r -s -h off the OS/2 install CD (found in the debug folder) to remove read-only permissions on c:\os2krnl, c:\os2ldr, and c:\os2ldr.msg
15.1 - created a backup folder on my C: drive and copied those 3 files to that backup
15.2 - Copied os2krnli from Disk 0 to c:\os2krnl (note the slight name change in the file! The lack of the "i" on the end tells the loader not to load off disks!), os2ldr and os2ldr.msg to c:\
16. Edited c:\config.sys with tedit and REMed out BASEDEV=IBM1S506.add
17. Copied all .dmd files from Disk 1 to c:\os2\boot
18. Copied danis506.add to c:\os2\boot
19. Copied all .dll;s from disk 1 to c:\os2\dll
20. copied all .ifs's to c:\os2\boot and c:\
21. Rebooted off hard disk, install continued with part 2
22. Did NOT install networking at this point when it asked (I figured that can always be installed later, best get the desktop up and running)
23. Install completed stage 2. Allowed system to reboot again.
23. After install, edited c:\config.sys and re-added basedev=ibmidecd.flt (the installer removed that, and without it my CD drive wasn't being seen)
24. I now had a running Warp 3 system on a relatively newer computer.
25. I then installed Fixpak 40, MPTS, TCP/IP, EMX Runtime, SNAP, etc.
Note: One thing I did discover is that there is a setting in the BIOS:
Microcode Updation
When this was Enabled, I was getting a trap on DOSCALL1.DLL
When I disabled this, Warp 3 will boot.
This is not an issue with Warp 4! Only seems to be an issue with Warp 3.
I should note, my Warp 4 install CD (updated with Updcd and Danis) had no trouble installing on this computer. I did a test install with it, and it just happily found the hard disk, no issues partitioning, and the install went fine.
However Warp 3 is old enough that you do have to nurse it through an install to get it running on newer hardware.
Good luck!
If you've installed Boot Manager, make sure that you make the primary partition smaller than the 8032. I generally pick 8000 and let it size it on the correct block boundary.
Fahrvenugen: Wow, thank you for that detailed information!
Quote13. After advanced installer Part 1 finished (the text screen installer), it would not boot (just loop booted)
Is this after the installer copies the files to the HDD?
(Because my installation crashes around 70% copying files to the HDD)
Edit: Also, I feel guilty for asking, do you think it's possible for you to create floppy images for me and upload to a public server?
Hi,
So if I'm understanding correctly, it goes into the blue text-based install screen (part 1 of the install), gets to around 70%, and gives you the "can not find the specified file" error.
Okay, if I recall it is somewhere around the 70% point where it starts reading files off the floppy drive (the boot disk and disk 1). Also if I recall correctly (I vaguely remember getting this error several years ago) there are some files that *must* be on those disks when it reaches that point of the install, even though OS/2 doesn't use them (don't ask me to recall which file in particular it is looking for). What I think I did to get around it is...
-Have a copy of the *original boot disk* and the *original disk 1* on floppy
-Also have the modified boot disk and disk 1
-Use the modified boot disk and disk 1 to start the install process
-Once the install process reaches the point of starting to copy stuff from the CD, swap the modified Disk 1 from the floppy with the original Disk 1
-When it asks for the install disk and disk 1, use the originals
-Once it completes part 1, then reboot from the modified boot disks and perform steps 14 - 20 from the above
If course the other thing to consider - if it is reading from the CD at the point the error comes up, you might have a bad CD (or a CD that is missing some file)
Fahrvenugen, you are amazing for remembering :)
It went past the 70% mark and completed the first part of the setup.
Unfortunately for me, I'm unable to work on this for now. (I've got more pressing concerns)
I'll work on it again next week.
Thanks again all!
Ok! Sooo I made time for this because I was very optimistic :)
When I try and boot off the HDD after part 1 of the installation, the PC just doesn't boot.
It just sits at the place you expect the OS/2 Warp 3 screen.
So I boot off the floppies and do the changes you recommend. (I copied the ADD files as well and changed the config.sys as well)
No luck! Still just sits like it wants to boot, but doesn't.
Any insight? (I'm going to take a look at the issue again tomorrow)
Hi again,
It *might* need an sysinstx command
To do this, boot from your boot floppies (the updated ones)
When you get to the install screen asking for easy install / advanced install, hit F3 to go to a command prompt.
Switch to your C: drive, enter:
c:
Pop your Disk 0 (the boot disk) into Drive A
Then type:
a:sysinstx c:
It should give you some message about transferred system files.
Also, check your config.sys file on the C drive (use tedit) and you can try REMing out some of the unneeded .FLT device drivers. I know the ones for SONY can cause trouble.
You can do the same with a lot of the .ADD's. Out of these, you for sure need danis506.add and ibm1flpy.add. The rest you can probably rem out.
If that doesn't work, I'll have to go through the process again on my test machine and see if I missed anything.
Admittedly, getting Warp 3 to install on modern hardware isn't for the faint of heart!
QuoteAdmittedly, getting Warp 3 to install on modern hardware isn't for the faint of heart!
That's no lie!
I'm going to give it a go this morning and will give feedback as soon as I can.
Ok! Sooo...
I REMed out:
BASEDEV=SONYCDS1.FLT
BASEDEV=SONY535.ADD
BASEDEV=SONY31A.ADD
I also tried the a:sysinstx c: and I get the following error message:
The type of file system for the disk is HPFS.
The system files have been transferred.
I'm sorry to burden you with the OS/2 issues :(
Edit: lol, I thought that was an error message... Maybe I should read, or maybe I'm just expecting the OS not to work. Must be my negativity ;D
hehe, anyways, it's still standing still at the point where it's suppose to boot.
I've tried a clean install without the boot loader partition as well (Same issue)
Try FDISK and set the partition as... Startable (I think... it's either that or Bootable).
BUT, if BootManager is still installed, set THAT partition as Bootable, and then go into your Boot Manager options and select the boot partition there.
Remember to save all changes before exiting and then reboot.
Hey RobertM,
FDISK reports that the partition status is 'Startable'
Also that Access is 'C: Primary' with FS Type 'HPFS'
Partition size is 8001MB
Hi Charl,
Sorry it has taken longer than anticipated to get back to you - unfortunatly work must come first even though I'm supposed to be retired.
First up, Fahrvenugen set out most of what you have to do in extremely good detail. The one thing we did to stop the problem of the installer not finding files on disk 1 was to use a stub with the name of each file we removed.
Concerning the not booting problem you have. Did you read the readme in the idedasd package especially the section on large hard disks? If not do so and you may find the answer to your problem. I have never installed OS/2 on a partition larger then 2 GB - warp 3 is more than happy on a 1 GB partition - in fact the two working boxes we have here with warp 3 connect on them have the boot partition set at 600 MB on 80 GB drives.
Charl,
Try a smaller partition for your boot partition. I've never tried installing Warp 3 on anything bigger then a 1 GB partition, but I do know there are partition size limitations beyond which it just won't boot.
Ive found that for Warp 3, a 500 MB boot partition is one of the best sizes. Room for the entire OS (which even with fixpaks and all the networking stuff installed is still a max of about 100 MB), room for a few core apps, and then if it happens to lose power or that machine gets rebooted without a proper shutdown, the Drive C only takes a few minutes to go through the chkdsk, and if you're lucky the data partition might not have a dirty flag and not go through chkdsk.
And trust me - that's an important thing to consider. I've had situations where my 60 GB (data) partition took over 20 minutes to chkdsk after an improper shutdown and the dirty flag remained on!
Thanks all for the input!
I'll give it a go this morning :)