Hi, I'm trying to install OS/2 Warp 4.52 from the Convenience Pack 2 CD's, but whenever I boot from the disks and enter the LVM stage, it doesn't recognize my hard drive, only my CD drive. It's a 300GB drive... I thought the Convenience Pack's were supposed to be able to recognize larger disks? Also, it gave me an error that "One or more partitions on the disk may be corrupt". Again, I've been reading a new driver is needed, but I thought that because I was using the CP2 disks I wouldn't need that?
I also tried creating the boot disks provided by WarpDoctor.com but they gave me an error when I booted up (something about not being able to use the disk, and it set off my computer speaker into an endless beep).
I have the partition I want to install OS/2 on as the fourth primary partition. First I tried setting the partition label to HPFS; then FAT-16, both didn't work.
Any ideas on what might be going wrong?
BTW, I just inserted a 30GB drive for kicks, and I noticed that when the CD was booting it said that a certain driver (int13 or something) recognized an 8GB or larger drive, but still the LVM doesn't display the drive.
Most likely you have a SATA driver in your system and MCP only very limited to not does not support this (the version of ibm1s506.add).
You need to create bootlfoppies and put these drivers on it:
http://hobbes.nmsu.edu/download/pub/os2/system/drivers/storage/danis506r185.zip
http://hobbes.nmsu.edu/download/pub/os2/system/drivers/storage/daniatapi040.zip
But you can also purchase eComStation www.ecomstation.com.
Best regards,
Roderick Klein
Mensys
P.S. I work for Mensys, the company that makes eComStation so the suggestion is complete independed.
Thanks, actually it's not SATA, it's IDE. Also, I tried the danis driver before, and I replaced the ibm506 driver with it and modified the CONFIG.SYS file on the floppy, but when I inserted the disk, it wasn't reading correctly.
I erased all of the partitions on the 30GB drive, made it the only hard drive plugged in, and labeled it as a FAT16 partition, and now when I boot the OS/2 disks I get a red screen with the message "Error 9 returned from LVM.DLL".
EDIT: I just tried it again (the Danis driver). I put "SET COPYFROMFLOPPY=1" and replaced the ibm506.add entry with the Danis driver, but after all three disks were inserted, it said "unable to operate hard disk".
Re:
Quote from: Patrick_ on 2008.10.17, 20:38:15
Hi, I'm trying to install OS/2 Warp 4.52 from the Convenience Pack 2 CD's, but whenever I boot from the disks and enter the LVM stage, it doesn't recognize my hard drive, only my CD drive. It's a 300GB drive... I thought the Convenience Pack's were supposed to be able to recognize larger disks? Also, it gave me an error that "One or more partitions on the disk may be corrupt". Again, I've been reading a new driver is needed, but I thought that because I was using the CP2 disks I wouldn't need that?
I also tried creating the boot disks provided by WarpDoctor.com but they gave me an error when I booted up (something about not being able to use the disk, and it set off my computer speaker into an endless beep).
I have the partition I want to install OS/2 on as the fourth primary partition. First I tried setting the partition label to HPFS; then FAT-16, both didn't work.
Any ideas on what might be going wrong?
Is the above not a typical example for asking (IBM's Developers and other OEMs involved with the production and release of this Operating System) the question since they are the ones with access to the Source-Codes of the OS: What is wrong "
HERE?"; and, how problems like these can be fixed. And, just maybe, these are some of the reasons for the "slow" uptake of OS/2?. 8)
Regards.
SAB
Old topic, throws everyone encountering it because not obvious. I installed on a 60G without the new drivers on floppy, though installed them later because faster.
First, HPFS has a limit of 64G. You'll need to partition the drive.
Second, more major, whether 30 or 300, you must use DOS 6.22 to get rid of previous partitioning. Just use it to make a 2G partition that LVM finds, then you can resize it up to 64G.
Start here:
http://www.os2world.com/component/option,com_smf/Itemid,63/topic,1042.0/
Particular attention to #10. DOS 6.22 is essential unless you start with a truly bare new drive. Nothing else, no other technique, works that I've found.
Quote from: ddan on 2008.10.18, 03:34:07
Old topic, throws everyone encountering it because not obvious. I installed on a 60G without the new drivers on floppy, though installed them later because faster.
First, HPFS has a limit of 64G. You'll need to partition the drive.
Second, more major, whether 30 or 300, you must use DOS 6.22 to get rid of previous partitioning. Just use it to make a 2G partition that LVM finds, then you can resize it up to 64G.
Start here:
http://www.os2world.com/component/option,com_smf/Itemid,63/topic,1042.0/
Particular attention to #10. DOS 6.22 is essential unless you start with a truly bare new drive. Nothing else, no other technique, works that I've found.
Given the approach needed above it is anyone's guess why IBM lost out to Microsoft in the "FINANCIAL AND BANKING" communities around the world in those bygone days. ;)
DFSEE works every time, it's just exceedingly daunting to use.
Re:
Quote from: Saijin_Naib on 2008.10.18, 09:12:56
DFSEE works every time, it's just exceedingly daunting to use.
Perhaps, one of the reasons why "IBM" et al have all but given up on it. ???
Well, Saijin_Naib, another one-line input that subtracts and distracts. Whether your intent or not, that's the effect. Let me be clear that it's the BREVITY of your post that I object to here. Please take time to consider whether you ADD anything with a post. Casually throwing out a possible but expert level solution does not help someone just trying to get the basics going as quickly as possible.
To use DFSEE, one would have to boot DOS at least. So, instead of a minute with its simple FDISK, you advise fooling around with the "exceedingly daunting" DFSEE? -- Of course having downloaded and unpacked it first, then read its extensive detailed instructions, nearly all of which are for exotic options. -- And use of DFSEE is certainly dangerous in the given situation of multiple partitions.
Back to Patrick: if you use DOS 6.22 to prepare a DOS-bootable partition and check that you can actually boot from it, all after should go smoothly with CP2, BUT with multiple partitions, you're going to run into a major tangle. When experimenting with ANY OS, you should always use a spare drive, nothing else on it, all other drives physically disconnected. I'm sure you know, but perhaps got carried away with enthusiasm.
Thanks guys. I clipped my HD to 2GB with a jumper setting, and all went well, but when trying to copy NAMECHANGE.EXE the installer gave me this error: http://service5.boulder.ibm.com/pspsdocs.nsf/c7a34b35e55986f9862563cc00604815/bfb716a4d766404a862563fb004d2f14?OpenDocument; and then wouldn't continue. I would assume I can just follow the instructions there, modifying the CONFIG.SYS and making a new disk with the changes?
Hey Patrick, take a look here:
http://www.dfsee.com/dfsee/cdrom.php
This is the site for the DFSEE FreeDOS bootable CD-ROM and Floppy disk Images. I'd suggest that if your OS/2 4.52 has IBM JFS support you install on that or use the eComStation Bootable JFS. If you use these methods you will have a volume of the full size of the drive that will be much, much faster than HPFS is.
Now, to use DFSEE you will need to merely follow the on-screen prompts and take your time. The only possible difficulty will be in the beginning when it asks you whether you want DMA or BIOS defined drive support. I find that the BIOS one, though "slower" yields less frustration. Your mileage may of course vary. You can then use DFSEE to make, format, and add all of your partitions to the IBM Boot Manager (which DFSEE can also install and configure) with relative ease. Just try and read each menu carefully and you will find where you need to go. That's how I learned as the documentation would need to be read on another computer at the same time I'd be working which is just not possible for me now. In any case, good luck. I think you should use the eComStation Bootable JFS if only to have an easier time than having to divvy up your 300gb drive into little HPFS ready chunks.
Patrick: you're winging it, man! Going where no OS/2er has gone before! NAMECHANGE.EXE in The Google gets 10 hits, none obviously useful. A search of my CP2 installation turns up no such file, nor have I ever encountered it. You may have found a situation where the driver queries the drive for actual size but BIOS believes it's smaller.
Seriously, if you ignore what I know works -- after all, I'm only running CP2 on a 60G that I re-used after DOS 6.22 FDISKing -- and even ignore Saijin_Naib's LONG way that'd eventually work -- then I can only wonder why you've asked for advice.
saborion2, I make an exception to my own and other's resolve to ignore you to note that you fail the Turing test: no human would make ANY connection between my post and the random news item that you posted. I could write a REXX program that could make your post above. -- Having determined that you are clearly not human, reckon I'm free from here to exercise my wit without any accusation of a personal attack being even possible.
But just this once I'll also be serious with you: what has happened to you? I ran across some of your old posts, and you were cogent and helpful. But now you're just a rather lame troll, neither interesting enough nor clever enough to draw anyone out. I for one would welcome the old saborion2 back...
Quote from: ddan on 2008.10.19, 01:29:53Seriously, if you ignore what I know works -- after all, I'm only running CP2 on a 60G that I re-used after DOS 6.22 FDISKing -- and even ignore Saijin_Naib's LONG way that'd eventually work -- then I can only wonder why you've asked for advice.
Well, see, by the time you all had posted your suggestions, I had already clipped my drive. I *will* try DOS 6.22 FDISKing it, though. Also, I may have been wrong about NAMECHANGE.EXE, it was probably something else... ;)
BTW, that link I provided is dead, you have to remove the ';' at the end. My question is, on my OS/2 disk there are a couple of CONFIG.SYS files. Which one should I modify as the link suggested I do? There's
one under the "bootimgs" folder and one under the "os2image/disk_1" folder. Will modifying both of these work?
I should also note that I tried booting my system after the error occurred during installation (again, it looked like it had only a few more files until it was done) but it gave me an error about PRINT01.DLL, another DLL, and some bad entry in CONFIG.SYS and then wouldn't boot further. I tried modifying the CONFIG.SYS file in the command prompt from the installation disk but couldn't find it on the installed drive (C:).
Patrick: I'm a bit less amiable than my usual surly self this weekend, for no particular reason (though there is a pesky robot attempting to hijack this thread). Sorry as appropriate. I'm willing to advise, BUT I'm cursed with only being able to tell you what has worked for me. I stick to safe and simple.
Now, here again, I don't believe that you have to bother config.sys at all, and that you're going on a snipe hunt with that, and I'm simply not going to follow you. From what you've said, that you got to LVM, then evidently your hardware doesn't have any problems getting to points that in my experience mean that all will go well once you've done FDISK as I describe.
As I mentioned in my first post, you don't yet believe that the cause is SIMPLE, that LVM isn't able to touch drives that it doesn't like the partitioning of, when its exact purpose is to SET that, but it's typical from what I've seen, one of the charming quirks of OS/2.
With an high degree of interest in OS/2 Convenience Pack 4.52... (and this exercise/undertaking by Patrick) does anyone know if any support whatsoever (paid engagements...) is currently being provided by IBM or Serenity/Mensys to clients still depending on/running OS/2 Convenience Pack 4.52?
Thanks.
SAB
Well, via IBM you're able to open support case for a fee and as well they have special support contracts available to handle specific needs. But, the price for the last type of contract is quite expensive. I would assume that Mensys would be able to offer some kind of support as well; but I can't recall that I've seen anything about this. Guess that Roderick at Mensys can enlighten us on this topic.
Patrick,
This is a wild guess... but OS/2 may be balking at the fact that the hard drive is "clipped" to 2GB... OS/2 v4.52 stops relying on the BIOS once the boot loader and IDE drivers load - and may be bypassing it for setting up it's own drive geometry. That would be a possible cause for the problems you are experiencing (especially if clipping support isnt properly/fully working on the drive). It may be trying to read or write to areas outside of the 2GB boundary via it's on geometry mapping algorithms. You may be able to determine if this is the cause by adding the /V parameter to the IBM1S506.ADD driver and seeing what it tells you (check the geometry information - it will tell you what the drive reports, and how it is mapping it, and what of the space it is able to map using it's own geometry). A better scenario that would resolve it, assuming my wild guess is correct starts next:
Setting the drive to normal (full capacity) and then following ddan's or Saijin's suggestions will work. dfSee is actually pretty easy - you just need to create the bootable media (instructions on the page Saijin provided) - and it works flawlessly in every event I have used it. Simply delete all partitions on the drive, and re-start the OS/2 installer. OS/2 will take care of the rest. No need to go through the daunting steps of setting up the partitions using dfSEE... just delete the old ones.
A copy of XP will work as well... boot off the CDs, have it remove all partitions, and when it offers to create a NTFS partition, take the disk out, turn the machine off and start the OS/2 install (the key being to take the disk out and turn off/restart between the partition deletion phase and the partition creation phase).
Failing having a DOS 6.22 copy, dfSEE is probably the easiest, and least likely to cause trouble.
As for installing, you can simply set up a boot partition for OS/2 using HPFS - just keep it under 60GB. I find 30-40 seems best. Over that, dont panic when a format seems to finish and continue formatting (it doesnt seem to register the percentage formatted correctly - but does correctly know when it is finished).
The remaining space can then be allocated to JFS (or multiple HPFS partitions under 64GB, or a combination thereof). There is no bootable JFS with v4.52 - though you can modify the disks to utilize it for a boot partition, it may be a real pain (no... it will be a real pain).
Just remember to install BootManager first if you intend to use it. Even if you are not booting to multiple OS's, I find it handy, as I can "auto-reboot" the computer by simply calling "SetBoot /B" from a command prompt or script - that little gem requires BootManager to be installed though (which is why I install it on all my machines, even though I dont run anything but OS/2 on them). You can then trigger a reboot any variety of ways for any variety of reasons.
And as a usability note, I would ensure that you to make at least one JFS partition - it is the only way you will have support for files over 4GB - and is the preferred partition for apps like Firefox, Virtual PC, Ceres Sound Studio and others. In addition, you can set larger amounts of memory to the cache (HPFS is limited to 2MB - which is useless nowadays).
Hope some of that helps,
Robert
Quote from: saborion2 on 2008.10.23, 07:10:02
With an high degree of interest in OS/2 Convenience Pack 4.52... (and this exercise/undertaking by Patrick) does anyone know if any support whatsoever (paid engagements...) is currently being provided by IBM or Serenity/Mensys to clients still depending on/running OS/2 Convenience Pack 4.52?
Thanks.
SAB
A more thorough answer could be provided by you indicating what type of support you need. For instance, defect support? Additional drivers? Added functionality? Or simply support to maintain, install and/or keep various OS/2 systems running on v4.52?
I support and maintain various v4.52 and eCS v1.2MR installs - and IIRC, I am not the only one in the NY area who does. (for the first 3 above, it would probably be IBM, Serenity, Mensys, eComStation.ru or some of the gang here - for the last scenario, your options expand greatly).
Perhaps if you provide a better idea of what type of support you need (and the geographic location), others may be able to better direct you to a person or business who can help.
Robert
Quote from: ddan on 2008.10.20, 04:59:27
Patrick...
As I mentioned in my first post, you don't yet believe that the cause is SIMPLE, that LVM isn't able to touch drives that it doesn't like the partitioning of, when its exact purpose is to SET that, but it's typical from what I've seen, one of the charming quirks of OS/2.
ddan is entirely correct (which I only point out because it seems you - quite logically - think something so simple cannot be the issue at hand - unfortunately LVM is far from logical in it's (lack of) handling of "unknown" partition types).
LVM will fail with all sorts of spectacular, and not so spectacular errors depending on what unknown (to LVM) file system type it encounters. Every time I re-purpose an XP drive to OS/2 (I sometimes buy used drives and for a while many of the new drives I was buying came pre-formatted FAT32 or NTFS), I run into the same problem - and various errors about not being able to operate the disk, and even occassionally, LVM reporting incorrect disk and partition sizes for the unsupported partitions. Invariably, most of the time it ends with the red screen of nonsense about (paraphrased) "not being able to operate the disk", or "no (space to create a) bootable partition big enough (must be at least 120GB)" message.
One additional note though, LVM will also report errors in non-existant partitions for things like media bays (card readers, etc) with nothing in them. Ignore those errors. Those seem to usually show up as 96MB "corrupt" (per LVM) partitions. They are simply the BIOS's pointer to those media slots (if I understand it correctly). Occassionally, the same occurs with certain CD-RW and DVD-R/RW drives that have weird cache segments/memory that act almost like a second drive - again, ignore those errors... the actual hard disk should be partitionable and work fine (assuming you follow ddan's and/or saijin's steps below).
Robert