OS2World OLD-STATIC-BACKUP Forum
OS/2 - Technical => Setup & Installation => Topic started by: BookWorm on 2009.07.13, 17:29:48
-
I am trying to install Warp 4.52 (*not* 4.0!) to an "80" (actually 76) Gig hard drive. The drive *will* be partitioned like this:
Boot Manager
Windows - 8 Gig primary partition
Linux - 8 Gig primary partition
OS/2 - 8 Gig logical drive
Rest of the drive - logical drive shared by everything
But I keep getting some baloney about bootable partitions having to start and end in the first 1024 "cylinders".
How do I repair OS/2 so it will install as easily as that other os?
-
(1) Patch installation diskettes with Dani drivers. I am sure you can use the last version because 4.52 is, in fact, eCS.
(2) The "1024" cylinders condition is not topical any more. This was a condition for running W3 and W4 with their native HD drivers (ibm1s506.sys, LBA mode). You cannot run big discs in LBA, that's why the native drivers are useless to you and you need Dani drivers.
(3) Reconsider the size of your winblows partition. My experience: winblows will fill the 8 GB partition rather quickly. All those "patches" and "service packs" will do it easily. I recommend 16 GB if you can sacrify them.
(4) Reconsider the size of your OS/2 partition. For the operating system itself, 2 GB is more than enough. Make this partition HPFS. Create a (logical) partition for OS/2 data and user apps and make it JFS.
(5) Linux. Which one? My experience with Debian: 8 GB root is not enough unless you plan /usr and /home partitions.
-
Get UPDCD from http://www.updcd.tk/ (http://www.updcd.tk/) and install it - assuming you have a working version of OS/2.
Then get DaniATAPI040.zip and DaniS506r185.zip from hobbes and use UPDCD to apply them and make a bootable cd for you. That way you should not have problems installing beyond the 1024 cylinder limit.
Assuming you have OS/2 4.52 on the two CDs from IBM i.e. ACP2 then you should not be having any problems with HD size as it installed without problems on a 120 GB drive for a friend when his 80 GB went south.
Like Radek I would also question your partitioning layout.
Windows will need more than 8 GB unless you are installing 98. XP will be happy with 20 GB if you are going to use to do any work. Vista would need a shoe horn to fit in that 8 GB.
8 GB for OS/2 will work if you split it into a 1 to 2 GB boot partition with the rest for apps and data.
I have SuSE linux 11 on a 12 GB partition working without problems. Remember to put the boot loader in the root partition and NOT the MBR, you can add it to boot manager and all will work without problems.
I assume when you say the remainder of the drive - about 20 GB - is to be shared by all three OSs that it will be formatted
FAT32 which means you will need to get the fat32 ifs driver from netlabs. ftp://ftp.netlabs.org/pub/fat32/fat32_09121.zip (http://ftp://ftp.netlabs.org/pub/fat32/fat32_09121.zip)
BTW Radek eCS is based on OS/2 not the other way round.
-
Warp 4.52 should not have a problem with drives of 80GB (or larger for that matter), nor should it have the cylinder limit. Perhaps it is the setup I use though: I install Boot Manager in the first sectors of the drive, then the boot partition after it, and have not run into a size limit. No driver change was necessary.
Now, on SCSI drives, yes, I do run into that issue.
-
I have one more suggestion:
If You plane to ever attach more HDD's in system, then it is better to have OS/2 installed on primary partition. Just mine experience.
-
I decided to settle for 2 gig per boot partition, and all programs & data will go in the 70 gig FAT32 partition. Later, when I get a 320 gig drive, I'll remember those Dani upgrades.
Linux stinks. I installed it (Red Hat/Fedora Core 1) and it killed the boot manager, stole OS/2's partition, and trashed everything it didn't use. I won't be installing it on this computer.
-
Debian is installable :) You can also get it in the OS/2 boot manager menu. A summary of my experience:
(1) Select "install". Do NOT select "graphical install" and similar offers. "install" is menu-driven, not command line driven.
(2) If you install Debian on a new disc, install root on a primary partition. The Linux "fake partition" (a primary partition created on a new disc if you start with a logical partition) is incompatible with the OS/2 one. You can install, you can run but you will have big problems with LVM and you will fix it with DFsee. For safety, try to install on primary at any rate. Also, make a note what is you root (sdb1, etc.) :D You will need this info later when it is unaccessible :D
(3) Do not make root bootable!
(4) Do not install GRUB in the MBR! Install GRUB in the root partition. You need to decline the default offer and select "Advanced Options" for it. Sure, you know which partition is your root ... :D
(5) Finish installation and reboot. You get BM without your Debian. Okay, start OS/2, run LVM, find Debian's root by size and type (type 83), make it bootable and add it to BM menu. That's all. Reboot.
-
BookWorm, it is not a good idea to put all your OS/2 programs on a FAT32 partition for two reasons.
a) Fat32 is not a native OS/2 file system - it requires a third party IFS driver which is reasonable but not something I'd rely on for everyday working.
b) Because windows stole a lot of ideas from OS/2 there are a large number of system files that share the same names on both systems. While OS/2 is less likely to get confused windows is more likely to overwrite files without asking - then you get chaos.
I did warn you not to let linux put GRUB in the MBR. You have now seen what happens when you do. Radek has given a good outline of what to do with Debian linux, most others are very similar.
-
Instead of wasting one partition to OS2 Boot Manager make use of Air-Boot (http://air-boot.sourceforge.net/) which installs to MBR and works fine with OS2, Win, Linux, etc.
-
AAAAAAAAAAAAAAAAAAAAAGGGGGGGGGGHHHHHHHHHHHHHHH!!!!!!!!!
(Sorry. I've been doing a lot of that lately. It's all MicroSoft's fault.)
I installed Windows 2000. It said it would have to disable the boot manager, but I could re-enable it with the disk management tool. When I couldn't find the disk management tool, I reinstalled the boot manager after rebooting from the OS/2 CD's. Now every time I boot Windows 2000, it disables the boot manager making the computer unbootable until I reinstall the boot manager again.
Now that I have finally found the disk manager tool, how do I fix the boot manager? Have I ruined it with all that booting and reinstalling? The windows tool doesn't seem to know what to do with it, and thinks it's a fat partition!
-
Instead of re-installing Boot Manager; install Air-Boot instead; does the same work, less hassle and more features.
-
Hi, BookWorm!
This is a known issue, which is caused by Windows 2000, as Microsoft itself confirmed:
http://support.microsoft.com/kb/265003/uk
Just either install Win2K SP2 (or later, of course) or download this fix, where you'll find an updated Win2K fastfat.sys:
http://os2site.com/sw/util/disk/boot/bofixw2k.zip
Good luck!
-
The other thing to do is get DFSee and use it to set boot manager w2k proof. Once that is done you should have no more problems.
All the reinstalling of boot manager shouldn't cause any problems other than hair loss as you keep pulling it out.
DFSee http://www.dfsee.com/ (http://www.dfsee.com/) will run under various OSs but use it under OS/2 - dfsos2.exe. You will find what you need in the drop down menu under Mode=FDISK - BMGR W2K, chs & I13X fix - select the disk with boot manager on - wait a few seconds for confirmation and your troubles should be over.
Kim, the one problem with Air-Boot is that it won't let you do an advanced install with OS/2. While it is fine for anyone with a mature system if you are experimenting and using extended partitions it does not help and OS/2 will want to install boot manager anyway.
-
> Just either install Win2K SP2 (or later, of course)
I'll see if I can download that in ME, then reboot and install it in 2k. If not (and I suspect not) this is going to be the biggest pain in the butt since I was a kid and had to put up with a little sister.
> or download this fix, where you'll find an updated Win2K fastfat.sys:
Oh, thanks a lot. "Windows 2000 cannot boot because C:\WINNT\System32\fastfat.sys is missing or corrupted."
Oh, well, at least now I have something to keep it from accidentally booting 2k and messing things up before I get it fixed.
How the bleep did MicroSoft stay in business after 1995 anyway?
-
Get SP4 Update Rollup 1, dont mess with updating file by file because clearly, you did it wrong.
-
> .... W2k works incredibly well.
Usually.
> Better than eCS with out any doubt in my mind.
:o That's a surprise. Maybe it's a good thing I stuck with Warp 4.52?
> You should not have downloaded just a new filesystem driver without first getting w2k to SP4 level atleast
He didn't tell me that. I was just trying to get it stable so when I install the service pack, and reboot at least twice, I wouldn't have to reinstall the boot manager each time.
Oh well, I'm getting used to it. Sorry I'm so grouchy.
-
No problem. SP4 Update Rollup 1 will patch 2k to all the latest fixes, and anything you could need to patch will be taken care of for you minus the possibility for the trouble you've listed above.
I've had very serious issues with eCS on my machine here in terms of hard freezes (possibly shared memory area being depleted despite 2gb of RAM and a pagefile) and other issues with ACPI (hard locks, IRQ usage at 100% on boot, not shutting down properly, not going into/out of standby) and other things. eCS is my toy, Windows is where I do work (and game). But in any case, see if you can restore the fastfat driver from booting to the w2k install cd and copying it back over, then get the SP4 Update Rollup 1 package and let it do the work for you.
You don't have to install the Bootmanager, windows does nothing but take the "active partition" flag off the boot manager. It does not mess it up, it does not change its entries. It does this so the install process can complete without being interrupted. Simply use DFSEE or any other partition management software to restore the Active Partition flag back to the Boot Manager partition.
-
Hi,
If Xp work as previous Windows releases (NT 4) then you should just have to open up the partition manager and set the boot manager as active. But don't take my word for it...but as said, NT 4 worked that way.
//Jan-Erik
-
That's correct but when you start winblows2000 next time, the BM partition gets deactivated again so that you will reactivate BM every time you start winblows. I had these winblows on my comp along with OS/2 before and I had to install SP2 to get rid of the deactivation error.
Do not install SP3. You will not get deactivated but you get problems with network for a change. SP2 or SP4. But this is not the only problem with winblows2000!
In my experience, this winblows fouls all partitions it finds during installation. Naturally, without any notice. Moreover, it puts inconsistent info into MBR so that OS/2 FDISK will refuse to have anything common with such disk. You will need to fix MBR info using DFSee. Do not create partitions from winblows! Create partitions from OS/2, then return to winblows and install/format. Therefore:
(1) Start with a clean disk.
(2) Start OS/2 installation and create a partition for winblows. Do not create any other partition.
(3) Write changes to the disk, Ctrl-Alt-Del, start winblows installation.
(4) Install winblows on the just created partition. Winblows cannot foul anything because there is no other partition to foul.
(5) Install SP2.
(6) Start OS/2 installation, install BM, put winblows into the BM menu.
(7) Continue with installing other operating systems ...
Ufff ...
-
I should tell you all something before I make myself look any stupider. :-[
This forum is all the documentation I have.
No books. No manuals. No instructions. Not even OS/2 for Dummies. (But I think that will be my next eBay purchase.)
Basically what I'm doing is every time I install, it's like running though a large warehouse with no lights. Each time I know where what I ran into last time was, get past it, and crash into something else.
Now, I'm going to erase all partitions, reinstall one careful step at a time, and if I don't find any books on eBay or online, I'll come crying to you *again*.
Thank you for all the help so far, and again, sorry for being such a #%$& grouch.
-
I sincerely doubt that Radek, seeing as it has NEVER reset the active partition flag when I boot back and forth to/from Windows. I know, I used to dual-boot eCS/2k and eCS/XP. It will only remove the Active partion flag from the Boot Manager partition during the Install phase, it will NOT mess up the partitions and it will NOT touch the boot manager. It simply removes the flag. Use DFSEE and reset the flag, and nothing to worry about. Oh, you will have to add LVM info to the Win partition (after install) though as Win is not LVM aware (nothing other than OS/2 really is anyway).
Stop spreading misinformation.
-
I sincerely doubt that Radek, seeing as it has NEVER reset the active partition flag when I boot back and forth to/from Windows. I know, I used to dual-boot eCS/2k and eCS/XP. It will only remove the Active partion flag from the Boot Manager partition during the Install phase, it will NOT mess up the partitions and it will NOT touch the boot manager. It simply removes the flag. Use DFSEE and reset the flag, and nothing to worry about. Oh, you will have to add LVM info to the Win partition (after install) though as Win is not LVM aware (nothing other than OS/2 really is anyway).
Stop spreading misinformation.
This is NOT misinformation. Search the web, or look at the court case in the US against Microsoft. They did indeed do this. This may not be your experience because they eventually patched/fixed various releases due to the legal troubles.
For instance, in a quick search, the first result that came up was this:
http://www.computing.net/answers/os2/dual-boot-os2-warp-4-and-win2k/898.html
(Response #2)Win2000 Killing OS/2 Boot Manager
Source: Bob Bencivenga (benji00@mediaone.net)
Since the release of Win2000 there has been alot of discussion about
how Win2000 will kill the BM for OS/2 every time you boot Win2000. In
looking through the news groups today I stumbled across this bit of news
which should help everybody. The following is the text of how to fix it.
Saijin, just because someone says something "bad" about Windows does not mean it's "misinformation"
-
Alright, my bad. I guess 8 years ago this was true.
Put it this way:
Win2k Pro SP4 and XP Sp1/2/3 will NOT ruin the boot manager.
-
Alright, my bad. I guess 8 years ago this was true.
Put it this way:
Win2k Pro SP4 and XP Sp1/2/3 will NOT ruin the boot manager.
Yeah... the sad thing, and the reason this is still relevant, is that many people with machines that run either XP or Win2K still have to use their original install discs when they need to reinstall it (for instance, for purposes like below) - which will result in the problems indicated below.
That's the thing... it is great it's been "fixed" but the information is still relevant to the many people who bought a machine or OS disks before that time. Ah well...