OS2 World Community Forum
OS/2, eCS & ArcaOS - Technical => Setup & Installation => Topic started by: _AP on October 14, 2024, 10:06:23 pm
-
Hi. I successfully installed OS/2 Warp 4.52 (14.086) on my Thinkpad T42p.
I had some issues at first but resolved then with the Scitech video driver. I tried to figure out my boot situation from other posts here, but was getting a bit overwhelmed. I was hoping someone might be able to offer advice for my particular case.
I partitioned the drive into 3 primary partitions. Windows, OS/2, and BeOS. Then I made 4 logical partitions for Haiku, and other projects that I hadn't gotten to. I installed OS/2 to partition 2, and it was working up until I installed the BeOS Bootman. Boot Manager installs into the MBR, and boots the partition. I'm assuming OS/2 boot manager also installs to the MBR, because I was unable to use the BeOS boot manager to boot the OS/2 partition. No errors occur, it just appears to be in bootable.
Is there an advanced way to install OS/2 to not use the MBR? I want to use BeOS as I already know it can boot my other partitions.
Some options I think I have:
Can I use some boot manager like Lilo installed into a different partition to boot OS/2? (I can use this for other OS's.
Can OS/2 be booted from a PCMCIA to CF card that I have in the Thinkpad? I'm unable to see it from OS/2 and don't know if there is a driver I need.
Is there a way to install the OS/2 booter directly into the OS/2 partition, and if so, how would I do that?
I appreciate any help to my long winded question. :-)
-
OS/2 needs to know which drive it is booted from. The standard way is to install BootManager in a small primary partition using LVM. You could chain boot it from your Bootman, I've done similar with Grub, or use it to boot all OS's. The newer way is to install AirBoot into the MBR, which would break your Bootman.
Understand that OS/2 is picky about the partition layout, it has to be CHS partitioned (unless using the latest ArcaOS) and the way for OS/2 to co-exist with other operating systems is that all partitioning has to be done with OS/2 tools, LVM with Warp 4.52. during this process BootManager can be installed and the OS's can be added. Afterwards you can use the other operating system tools to change partition type, format etc
If you don't want to start over, DFSee, dfsee.com (http://dfsee.com) might be able to save you by fixing the CHS values to how OS/2 likes them, shrinking a partition so have room for BootManager and IIRC, installing BootManager. Unluckily I don't think dfsee supports the BEOS file system so you would have to shrink the Windows partition and you still need a primary for BootManager.
Also a good idea to have a FAT32 partition for sharing data between the operating systems, FAT32 support has to be added to OS/2 after install, or use a FAT partition, which means for OS/2 8.3 name limits.
No you can't boot OS/2 from a CF card unless the hardware presents as an IDE drive.
BTW, Lenovo has (had?) a SNAP build for T42's, at least those with an ATI video display, also a sound driver. Don't know the URL as it has been a long time since I installed it to my T42. You can also use the Uniaud sound driver and the SNAP you have does work besides DPMS support.
Edit: feel free to ask more questions
-
Thanks. I was able to get the video drivers all set with the snap driver.
I don't want to use OS/2 boot manager, as the BeOS boot manager can already boot everything else in any other file system. I couldn't find a way to have a different partition for the booting of OS/2. I may be able to make that work if I add that booting partition with bootman.
I think this computer does show the CF card as an ide drive in its PCMCIA adapter, but so far I can't see the drive in OS/2. Only Windows. I may be missing a driver, but I feel like it should exists since my computer is officially supported by OS2, unless they neglected that.
Can grub be installed into the root of a partition? I can't mess with MBR for BeOS sake.
Thanks for the tip on shared drive. I often do that where possible, but usually I use FTP.
-
Both BootManager and Airboot can boot any file system as long as you use OS/2 tools for setting things up. I use Airboot to boot everything om my MBR drives, including BeOS and Linux. I used to use BootManager but it can't handle drives over 500GB or so. While BootManager needs a primary partition (as small as you can make it works), Airboot installs in the MBR
IIRC, if OS/2 is installed on a primary and is given the C: drive letter, you can get by without a bootmanager. I guess that is why OS/2 was working fine until you installed Bootman which likely wiped out the LVM info that OS/2 needs on the MBR. I have always installed OS/2 on an extended partition and never as C:
I don't have experience with PCMIA but likely the drivers install too late in the boot process to use for booting.
Grub can be installed in an EBR rather then the MBR, it's how I install it so I can chain load it.
As I said, it should be possible to install BootManager in a small primary, OS/2 in an extended partition and use Bootman to boot to BootManager which then loads OS/2. With a zero timeout you wouldn't even notice it.
-
I don't really know what LVM does to MBR, are you saying I should install BeOS bootman first, then install OS/2, with its boot manager being in a smal primary partition, and then BeOS bootman can boot that partition which points to OS/2 partition?
Do I have to pay attention to any installable vs star table with the two OS2 partitions?
-
I'm not totally sure what LVM does with the MBR as well. Generally LVM stashes some data in the MBR/EBR about drive letters, newer OS/2 lets you assign any drive letter you want to a partition, whereas older (Warp 4 or earlier) just assigned drive letters under the same rules as DOS. It also allows JFS volumes to span partitions.
Yes, I think that installing Bootman first, then BootManager in a small primary. OS/2 can be installed anywhere on the size of HD you likely have with the T42 and will install to an extended partition fine.
I don't know anything about Bootman and whether it respects reserved space in the MBR so guess you will have to test.
-
Wow. Thanks. I tested it out in a virtual machine (install takes a while with physical CD). I used BeOS to make a BeOS partition, OS/2 Boot manager partition (drive setup had this option), and a HPFS/NTFS partition. This does not format it. I actually couldn't format as HPFS or OS/2 Boot manager.
Then I installed BeOS, and it's boot manager.
Then I installed OS/2. I setup the one partition as C. I couldn't set up one as "startable" and one as "installable". I would like to know that process even though I may not need it now.
At this point OS/2 was booting, and seemed to have messed up the BeOS bootman in the MBR. However after reinstalling BeOS, and it's bootman, it was able to boot OS/2. It didn't seem like I needed the separate OS/2 boot partition. I can tell better about the process for those who may need it after I install on the Thinkpad.
-
Good, I'm somewhat surprised that OS/2 was happy with using BeOS to partition, OS/2 is picky and it is usually recommended to use OS/2 to do all the partitioning.
I've never actually installed OS/2 4.5.2, with OS/2 3 or 4 you use fdisk and can set the partitions startable or installable. I'd assume it would be similar but using LVM. eCs and ArcaOS have updated disk managers and installers. Also bootable JFS so no need for HPFS.
-
I'm running into some issues with Windows XP and OS/2. They aren't playing nice. Neither one seems to want to install to anything other than C:
How can I install OS/2 Warp 4.52 to D: I can set D: to startable, but not installable I'm LVM.
I have
16GB Windows XP
8GB OS/2
40GB BeOS
Logical
32GB Haiku
20GB Slackware
If I install OS/2 first, on C:, Windows XP will only install to C:, and I can't change the drive letter during installation. So I would like to install OS/2 to D:, if I can't install XP to D:.
-
Can you hide the XP volume from OS/2? Otherwise I think you will have to install boot manager before you can make D: installable
-
I'm running into some issues with Windows XP and OS/2. They aren't playing nice. Neither one seems to want to install to anything other than C:
How can I install OS/2 Warp 4.52 to D: I can set D: to startable, but not installable I'm LVM.
I have
16GB Windows XP
8GB OS/2
40GB BeOS
Logical
32GB Haiku
20GB Slackware
If I install OS/2 first, on C:, Windows XP will only install to C:, and I can't change the drive letter during installation. So I would like to install OS/2 to D:, if I can't install XP to D:.
Hum!
What was your latest boot partition via your boot manager ?
If it was C:, try to change it one time to D: and only after try to install OS/2 from the DVD.
I had something like you using airboot with already defined partitions and resolved it changing selected partition under airboot first.
-
Hmm. I didn't think to change the drive letter in XP first. I think it's not simple as registry issues can happen. I'll go that route and let you know how it goes.
The BeOS boot manager just boots based on partition number. I'm
Not sure what the OS/2 boot manager does. When the windows boot manager is active just booting XP, it's just the default setup with the first partition being C:, until OS/2 interferes. I think if I can successfully get XP booting with D:, I should be all set.
-
What's the problem with installing both OS/2 and XP to C:? They both use their own drive letter logic and neither one should know (or care) what drive letter the other thinks it has.
-
I seem to be unable to do so. I also can not have XP as a non C: drive it seems. What's the exact process I should follow? I can't find it anywhere online.
Edit: I just found out you can manually create a volume/lvm in LVM. If I select the CD or any other volume, I can "Create Volume" and set it to be able to be made bootable. Then I could select the partition for OS2. After that I can change the drive letters the way I want, with the XP partition hidden. I'm not sure why I was missing this and why it only had this issue when I got Windows XP involved.
Edit 2: I remember now. I had formatted with BeOS the OS2 partition type as OS2 boot manager, or as some other non windows partition. I did this because my first failure had Windows XP install boot files into C, and Windows system files into "D" which was my planned OS2 partition. I did this to prevent Windows from seeing it during install.
OS2 not seeing the partition as something it could use, didn't create the LVM compatibility volume for it. I didn't know until now how to manually create.
I'll let you all know how it went.
-
OK maybe I need more help. After the install of OS/2, Windows XP now sees that drive as C:, and sees its own drive as D:, and is unable to boot. How can I change letter for Windows XP
Edit: I would just test, but the OS/2 boot situation is messed up. I don't want to reinstall. Can I fix the MBR for os2 without reinstall?
-
Update. I used gparted to set flags on the os2 partition. I set the hidden flag. This fixed Windows XP. Can OS2 still boot from a hidden partition? Are there any other issues with this?
-
The rule is to never use other then OS/2 tools to partition etc. With care, you can do some things with other tools such as gparted but you are in danger of screwing up the partition tables or the dlat data that OS/2 4.5+ needs to figure out the LVM info.
OS/2 can boot from a hidden partition with the right boot manager such as AirBoot, otherwise you have to test.
-
Now that you have XP booting, you should be able to use its disk tools to remove the drive letter assigned to the OS/2 partition from XP's view point and then if needed, unhide the OS/2 partition.
-
Can airboot install into the root partition, or does it need the mbr?
-
Airboot installs into the MBR. IBM's Boot Manager installs into a minimal sized primary.
For your set up, what I would do is use OS/2 LVM to partition something like,
primary bootmanager 8MB (one cylinder, the smallest that LVM will allow)
primary XP 16GB
extended OS/2 8GB
extended BeOS 40GB
extended 32 GB Haiku
extended 20GB Slackware,
Adding the planned partitions to bootmanager.
Then I would carefully install the other operating systems, usually using the advanced option so you only reformat the partitions and perhaps change the partition type.
I've never installed BeOS, I'm assuming it will install in an extended.
I did install Haiku once out of curiosity, things went smoothly, though I can't remember much about it besides no problems.
Slackware, you will have to be careful to just initialize the partition, put grub or lilo in the EBR, not the MBR, and perhaps use fdisk to change the type. And what about a swap partition? A 2 GB one perhaps?
XP, I've never installed, Win2K said during install it noticed boot manager and suggested that I use its disk manager to make boot manager bootable. Much better then Win95, which at the end of install informed the user that the OS/2 partition was now gone. In reality a minute in fdisk brought it back.
OS/2 has always been particular about partitioning, everything has to align with a cylinder boundary while other OS's will try to use all the space even if it means a partition ends in a weird spot as OS/2 sees it. Sometimes you end up with a functioning OS/2 but LVM won't run. With OS/2 4.5+ and LVM, we also need the LVM info saved in the MBR/EBR, what drive letter we have assigned and some other stuff about JFS. Whether Bootman touches that part, I don't know.
Edit: I'd assign the OS/2 partition as E: that way a shared partition can be D:
-
Windows has its own equivalent to LVM, called Logical Disk Manager. It's been a while since I used XP, but IIRC you can open it by right-clicking on "My Computer", choosing "Manage", and scrolling through the options tree on the left until you find the Logical Disk Manager (ISTR it's hidden under a folder in a slightly non-obvious place).
From there you can remove any XP-assigned drive letter from a partition.
If OS/2 still can't boot, then what you will want to do is: from OS/2 boot media (e.g. the install CD), go into LVM and make sure the OS/2 volume has a drive letter.
-
Hmm. I didn't think to change the drive letter in XP first. I think it's not simple as registry issues can happen. I'll go that route and let you know how it goes.
The BeOS boot manager just boots based on partition number. I'm
Not sure what the OS/2 boot manager does. When the windows boot manager is active just booting XP, it's just the default setup with the first partition being C:, until OS/2 interferes. I think if I can successfully get XP booting with D:, I should be all set.
Sorry, not changing drive letter but just boot into the partition you will install OS/2 because this partition already was defined If I correctly understand it. I wrote D: because you wrote installing OS/2 to D: (drive letter is LVM added during install)
Boot one time (from under you boot manager) into the partition you will install OS/2 (if this partition is empty, boot will fail but the boot manager has it taken as boot partition, than boot on the DVD and install OS/2 (it should see the latest boot partition used from under you boot manager)
-
Here are the steps I followed to get BeOS, OS/2, and Windows XP booting with the BeOS boot manager.
1: Use BeOS to partition the drive. Intel partition map.
Primary:
Windows XP (partition type NTFS/HPFS)
OS/2 Boot manager of about 200MB. Probably can be smaller. (Partition type OS/2 boot manager)
BeOS partition (type BeOS)
Extended:
I used the rest type NTFS/HPFS.
Intitialized BeOS as BeOS File System, 2048. Initilized 200MB primary OS/2 partition as FAT16. (this removed OS/2 boot manager from "type" but maybe this isn't necessary.)
Set sizes you want.
2: Booted from OS/2 boot disk, then inserted second disk. Used LVM.
- Assigned first partition C: in Logical view
- Deleted 4th primary partition in Physical view. Created 4 logical partitions for myself. 1st for Haiku, 2nd 8GB for OS/2.
I may have saved and exited and rebooted here. Then repeated steps to get to LVM.
- Created new volume. I think I said can be made bootable. Picked 2nd 200MB primary partiton. Finished with F6. Letter P:
- Created new volume. I think I said doesn't need to be made bootable, and selected compatability volume. I chose the 8GB second exteneded partition. I think i was able to make startable but not sure. Maybe I set the 200MB P: partition as startable. Set letter for extended OS2 partition to O:
Maybe I rebooted here. I forget when to do it, but I was able to set O: as installable or startable, and install boot manager to P: This part is most confusing for me and I think you have to get things in the right order.
I then installed OS/2 onto O: after rebooting.
3: After installing, I booted from the BeOS cd. I found out that OS2 didn't install into that 200MB partition. It installed into a 7.4MB partition/space that it created where the BeOS partition was. So no more BeOS partition. I'm going to retry after testing BeOS boot menu with that 7.4mb partition.
What a mess!
Next steps I thought was going to happen:
3: After install, I booted using the BeOS CD, installed BeOS, and it's boot manager. I set up the boot entries. Removed the OS/2 logical partition as an option. Called the 200MB primary partition with the boot manager "OS/2 Warp". After installing the boot menu, I was able to boot OS/2 and BeOS from the BeOS boot manager.
4: I then installed Windows XP into the first primary partition. (C:) Then I used the BeOS boot CD to boot into the BeOS partition (space for boot options). I used terminal and the command "bootman" to reinstall boot manager the same way, picking Windows, OS/2 boot manager, and BeOS partitions as boot options, and excluding the OS/2 logical partition where OS/2 lives. I can also add Haiku and Slackware here if I want.
-
Airboot installs into the MBR. IBM's Boot Manager installs into a minimal sized primary.
For your set up, what I would do is use OS/2 LVM to partition something like,
primary bootmanager 8MB (one cylinder, the smallest that LVM will allow)
primary XP 16GB
extended OS/2 8GB
extended BeOS 40GB
extended 32 GB Haiku
extended 20GB Slackware,
Adding the planned partitions to bootmanager.
Then I would carefully install the other operating systems, usually using the advanced option so you only reformat the partitions and perhaps change the partition type.
I've never installed BeOS, I'm assuming it will install in an extended.
I did install Haiku once out of curiosity, things went smoothly, though I can't remember much about it besides no problems.
Slackware, you will have to be careful to just initialize the partition, put grub or lilo in the EBR, not the MBR, and perhaps use fdisk to change the type. And what about a swap partition? A 2 GB one perhaps?
XP, I've never installed, Win2K said during install it noticed boot manager and suggested that I use its disk manager to make boot manager bootable. Much better then Win95, which at the end of install informed the user that the OS/2 partition was now gone. In reality a minute in fdisk brought it back.
OS/2 has always been particular about partitioning, everything has to align with a cylinder boundary while other OS's will try to use all the space even if it means a partition ends in a weird spot as OS/2 sees it. Sometimes you end up with a functioning OS/2 but LVM won't run. With OS/2 4.5+ and LVM, we also need the LVM info saved in the MBR/EBR, what drive letter we have assigned and some other stuff about JFS. Whether Bootman touches that part, I don't know.
Edit: I'd assign the OS/2 partition as E: that way a shared partition can be D:
I have installed Slackware with Lilo before, and into the EBR or root of drive. So that's not a problem. I could install BeOS on an extended partition, but I don't want to take any chances. Haiku can go into there though, as that's less of a hassle to reinstall. Also, I don't use swap on any of my operating systems and haven't had a problem yet. I don't know what kind of wear that will put on the SSD, and IDE SSDs aren't cheap or abundant.
The previous post I made is still a work in progress.
-
What are the instructions for installing OS/2 on a logical volume, with the boot manager in a primary partition. The rest of the things I can figure out after. Even if I wanted to dual boot with Windows XP. Lets say partition 1 is XP, partition 2 is OS/2 boot manager, logical partition 1 is OS/2. I assume booting from partition 2 should be able to use that to boot logical partition 1. I just don't know the steps.
-
Start LVM, use arrow key to highlight the volume you want to install on. Press enter. Then if everything is good with your partitioning, do "Set the volume installable", "Set the volume startable", "Add the volume to boot manager menu". Might have to "Change the volume drive letter" first. You may want to press F3 and save the changes at some points.
If you can not select the installable etc, "Delete the volume", "Create a new volume" first. May be asked to reboot during this process, though after pressing F3 and save.
If that doesn't work, it is possible that the partition table is corrupt from the LVM's point of view.
After installing XP, you may have to use the Windows disk manager to set the Boot Manager startable or whatever the term is.
Windows and OS/2 will both install a swap file by default, assuming your computer has 2GB (or even 1GB) of ram, OS/2 will seldom or never actually swap. Don't know about XP, likely more aggressive using swap.
Edit: Not sure about the OS/2 volume being set startable, perhaps jsut the boot manager being startable is good enough. Been a long time since I"ve manually done this, ArcaOS has the Installation Volume Manager which is better then LVM
-
So I think I did the best I could.
I used virtualbox commands to use the physical drive as a VMDK. I used BeOS to partition the drive, but OS/2 probably would've worked also. 3 primary partitions, 4 logical. I discovered it really doesn't matter. I installed BeOS and OS/2 in primary partitions, as well as the OS/2 boot manager that really wants a primary partition. I setup partitions for KolibriOS, Slackware, Haiku, and XOSL (just in case).
After competing the setup of OS/2, and installing the BeOS boot manager, it worked. I could use the BeOS boot manager to boot the OS/2 partitions. Finished up, but the drive in the laptop, and... no luck. Doesn't load either OS/2 Boot or Install partition.
Im sure there is an answer, idk what a different computer or drive would change. I have only been able to get it working on a virtual machine with a virtual drive or physical drive.
I used XOSL. It takes over the MBR, while also being installed in a logical partition. It also cannot boot the OS/2 partition or OS/2 boot manager, however, it can boot "Original MBR" which boots the OS/2 boot manager. It works out that way, so I have the 5 operating systems working on XOSL, but it's not as nice and pretty as BeOS boot manager. If the MBR gets messed up, just use the OS/2 CD to set boot manager startable with LVM, or reinstall if necessary. Then use XOSL cd (freedos) to restore XOSL to the partition.
XOSL boots original MBR, BeOS, And Haiku fine. It also boots KolibriOS and Slackware using their own LILO installations.
-
Damn. I don't know what I did, but the partition table got corrupt somehow. I've tried several times again, and now I have this newer issue of partition table getting corrupt. I only used LVM for partitioning. I formatted some partitions with BeOS or Slackware and cfdisk, but I should be able to, otherwise dual boot wouldn't be possible since OS/2 can only format FAT and HPFS.
I did install XOSL which modifies the MBR, but I did that before and it was fine.
-
Maybe you should be using more than one disk, that way they don't mess each other up.
-
It's obnoxious because I had it working briefly the way I wanted. I was just stupid when I wanted to make a shared partition for file transfer between OSs. It's a laptop. I do have a spare drive sled somewhere, so I might do it that way at this point.
-
Hi. I got it working. Not exactly sure how. I installed BeOS, OS/2, and OS/2 boot manager in the three primaries. Then installed the BeOS boot manager. That worked and I was able to multi-boot everything.
Then I had issues with booting FreeDOS on a logical partition. I then deleted the boot manager from inside the OS/2 OS with the GUI LVM, moved some partitions to make a FreeDOS primary, redid the BeOS boot manager, and I can still boot OS/2. It's all great and I'm not sure how. I did use a fresh drive with same model, maybe some MBR code or partition table was screwed up that wasn't getting repartitioned correctly even from scratch.
Now if someone could point me in the direction of installing fix paks? I can find information on them, but not the fixpaks themselves. Thanks for everyone's advice on the booting.
-
Now if someone could point me in the direction of installing fix paks? I can find information on them, but not the fixpaks themselves. Thanks for everyone's advice on the booting.
https://public.dhe.ibm.com/ps/products/os2/fixes/
https://public.dhe.ibm.com/ps/products/mpts/fixes/
https://public.dhe.ibm.com/ps/products/tcpip/fixes/
-
Here's a fairly good guide, though many links are broken, it does give you the files to google or translate from ftp to https. There's also some programs floating around to bypass the need for floppies, probably on hobbesarchive, hopefully others have a better memory then me.
Edit: forgot the URL, http://web.archive.org/web/20060926004818/www.warpupdates.mynetcologne.de/english/site_contents.html (http://web.archive.org/web/20060926004818/www.warpupdates.mynetcologne.de/english/site_contents.html)
-
Thanks for those links. I did see the one. The major fix paks shown for a T42p are XR_D003 driver pack and XR_C005 fixpak. These seem to be restricted. Any good source for these?
-
Well. I was able to install the major fixpaks successfully. However, I installed the usb driver, and now my usb mouse doesn't work. USB in general doesn't work. Usb 10.162. EDIT: I fixed this by rem-ing the related lines in config.sys.
Also, how would I install Ethernet Intel 1000 drivers? I have a e1000.os2 file, e1000.msg, e1000.nif, and protocol.ini.
Thanks for the help so far. I also have an issue where I tried to install UN02334, and now it says "a previous installation of service is still pending" system must be rebooted. On boot, I do see something about not able to call IBMCSFLK.exe.
-
Try Lars's USB drivers, http://hobbesarchive.com/Home/Download?path=/Hobbes/pub/os2/system/drivers/usb/usbdrv251.zip (http://hobbesarchive.com/Home/Download?path=/Hobbes/pub/os2/system/drivers/usb/usbdrv251.zip).
I forget the exact command, but you should have a program object MPTN or such that will allow you to install the network drivers in system setup.
-
USB drivers seem to work and be installed. I can still use mouse, but no usb drive yet.
The locked file device driver is loaded, happens on boot, I can't service the system with CSF because the update is still pending. Any way to clear lending updates?
-
You probably need to edit config.sys to clear the locked file driver, which leaves you wondering if it did its thing.
Now we have the unlock utility, "unlock foo.dll" will load foo.dll into memory allowing it to be replaced. Still need to reboot or reset the WPS in some cases to actually use the new DLL. Can't remember the package it came in so I'll attach it.
You will need a FAT32 driver for USB drives, https://trac.netlabs.org/fat32 (https://trac.netlabs.org/fat32), you should also install warpin to install wpi packages, http://hobbesarchive.com/Home/Download?path=/Hobbes/pub/os2/util/archiver/warpin-1-0-26.zip (http://hobbesarchive.com/Home/Download?path=/Hobbes/pub/os2/util/archiver/warpin-1-0-26.zip)
Note that generally, USB drives need to be formatted with CHS correct and maybe LVM info added as OS/2 can't handle large floppy format (no partition tables) over 2GB. Lars's USB stack does have a filter to overcome that limitation.
You also might want to update your kernel, https://www.os2site.com/sw/upgrades/kernel/index.html (https://www.os2site.com/sw/upgrades/kernel/index.html), make sure you use the same (SMP, UNI, W4) as you're currently using. Find out what you are using with the bldlevel command,
W:\>bldlevel OS2KRNL
Build Level Display Facility Version 6.12.675 Sep 25 2001
(C) Copyright IBM Corporation 1993-2001
Signature: @#IBM:14.204#@_SMP IBM OS/2 Kernel
Vendor: IBM
Revision: 14.204
File Version: 14.204
Description: _SMP IBM OS/2 Kernel
Unluckily you can't get that late of a kernel without ArcaOS.
-
I have 14.103 I believe, after updating with the C005 fixpak.
Would unlocking that driver resolve CSF pending update?
-
There's 104 kernel, 105 also floating around IIRC.
Unlocking would allow you to manually update the driver.
-
Here is what I get in boot. I unlocked the boot drive recursively with that utility. Still occurs.
-
What happens if you manually run ibmcsflk.exe? Do you have ibmscflk.dll in o:\os2\dll? Try copying the DLL to O:\os2\install
-
1 of 3.
-
2 of 3.
-
3 of 3. I did copy that DLL and have the same result. It seems like IBMCSFLK.LST might be locked.
-
Actually maybe it just can't find IBMCSFLK.LST. Search turns up nothing.
-
The two lines I rem'd relate to this.
After I rem that, things seem fine on boot, but I can't install anymore CSF service fixpaks because there is still one "pending". That happens even with original Config.sys from original
Install.
I would just try to do the install again, but CSF complains about the pending.
-
Strange, corrupted file? Here's mine from Warp v4+updates, when I run it, it goes to a full screen for a few seconds and then cleanly exits here.
-
Same issue even with those. What is IBMCSFLK.LST? It seems like the exe calls that?
I'm about to just reinstall, but don't want to mess up my multi-boot.
-
I'd assume that IBMCSFLK.LST contains the files to be replaced and their replacements.
-
Maybe that was never generated as part of the update, and that's why there is still an update. I don't think I have that. I'll check it out and see, if not, I'll just give in and reinstall.
Thanks for all the help, and Happy New Year.
-
So I did a reinstall. Still worked out well with the multi-boot. Maybe the trick is to do the partitioning from within OS/2, instead of the installer. So install, boot, do necessary partitioning like removing the boot manager partition.
Anyway, I did the reinstall. Got some new errors. Also it seems quite slow now, but maybe that's my imagination. The error I got was trying to install C005 fixpak. (D003 same thing). Complains about CSF_SEL.000 file. I can't find this file. The reader included with the FIX.CMD tool suggests it happens after attempting to use CSF 1.37b after 1.44, but I did it the same way as last time as far as I know. What a mess!
-
Oh, I fixed it. How? Well, I just tried it again today and it's working. I tried many times and many reboots yesterday and same issue. Did absolutely nothing today but try it and it worked.
-
So the update that caused a problem last time worked out fine this time.
Regarding fixpaks C005 and C006, I read that C006 could cause issues. Is there any reason I should update? Will I miss out on anything or have any issues not updating?
-
C006 was unfinshed, so without reason to update, probably best not to. You still might want to update to the last available kernel, 104 I think.
-
Thanks. This page: https://www.os2world.com/wiki/index.php/Updating_OS/2_Warp_4.52
Lists apars not included in fixpaks. I can not find these in any of the archives. Should I have them?
I appreciate your help. Regardless of updates, I'm looking forward to actually using the OS, not just try to get it working. I should probably watch some tutorials because the UI is somewhat foreign to me.
-
C006 was unfinshed, so without reason to update, probably best not to. You still might want to update to the last available kernel, 104 I think.
A final version was made of fixpak 6. Its was just never made available to SWC members best I can tell. Only for a few companies best I can tell.
Roderick
-
Thanks. This page: https://www.os2world.com/wiki/index.php/Updating_OS/2_Warp_4.52
Lists apars not included in fixpaks. I can not find these in any of the archives. Should I have them?
I appreciate your help. Regardless of updates, I'm looking forward to actually using the OS, not just try to get it working. I should probably watch some tutorials because the UI is somewhat foreign to me.
Most of those apars don't look too bad. The bugs that were still there include various parts of the OS that aren't SMP safe, the first one that showed up when people started going multi-core was tcpip32.dll being linked to the single thread library instead of the multi-thread library, there is a patched version floating around. The big ones are in how the kernel handles high memory, memory between 1GB and around 3.5GB. For example the kernel didn't deallocate memory if you loaded a DLL into the high memory arena and then removed it so you would have zombie memory holes. Arca Noae has patched the kernel to fix most of these but the license from IBM says they can only distribute kernels with ArcaOS, so no kernel fixes for you.
-
Update to 14_104a worked. Thanks.
Side note, what unzip program is the best? I have been unsuccessful unzipping anything.
-
Perhaps this one, http://hobbesarchive.com/Home/Download?path=/Hobbes/pub/os2/util/archiver/Info-Zip_Unzip_6-00.exe (http://hobbesarchive.com/Home/Download?path=/Hobbes/pub/os2/util/archiver/Info-Zip_Unzip_6-00.exe)
Not sure of its dependencies, likely at least libc.
Long term you might want to consider installing ANPM as a package manager and install zip from there.
Start here, https://www.arcanoae.com/wiki/anpm/ (https://www.arcanoae.com/wiki/anpm/) you also should have warpin, which I think I posted the link to already.
-
Thanks for that. That's helpful, although I did figure it out in the meantime. So I can now unzip things, but I'd like to look into that.