Install OS/2 after Windows 2000 on New Computer
Mark Ensminger
but I had no choice), I have been trying to install OS/2 onto a Dell
Optiplex GX270 that has Windows 2000 already loaded, with no success.
As this is a fairly new machine, I believe that the Win2000 is at the
highest service pack available. I don't have a list of the various
components, but I am pretty sure that audio, video, and networking are
all on the motherboard, along with the typical services. Still, given
that there is a report that says the machine is compatabile with OS/2
(or rather that a GX270N is, and I trust the report applies to my
model, which is listed as a "Series GX270"), I didn't expect serious
problems.
At originally configured, the machine has the hard drive as a single
partition of about 40 GBytes, formatted NTFS. I used PartitionMagic
7.0 to shrink the NTFS partition and to create space for both the boot
controller partition and the OS/2 partition. After taking a blind
path with BootMagic, I decided to stick with the tried and true Boot
Manager.
I have two separate problems. The first is that when using FDISK to
create the Boot Manager and OS2 partitions, I am unable to add the
Win2000 partition to the Boot Manager menu. That means that I can
only boot to the OS/2 partition. Fortunately, I have the emergency
PartitionMagic disks, so I can force the booting to occur to Win2000.
So I need a way to add the Win2000 partition to the Boot Manager menu.
The second, and much more serious, is that the OS/2 installation dies
late in the process. I boot to the Installation Diskette, then go to
Diskette 1, then Diskette 2. I choose Advanced Installation, choose
to execute FDISK, create and the partitions, set the OS/2 partition
installable, format the partition as HPFS. All of this appear to go
fine. With the CD in the reader, the files are copied, Diskettes 1
and 2 are re-inserted. Again, all seems well. I go through the
configuration choices on the first screen (English, standard keyboard,
PS/2 mouse, IDE CD-ROM (although it is actually a CD-RW), VGA, HP
printer, no multimedia), the second screen (none of these), the
optional bits, and the networking (no network adapter selected). It
goes through all of these just fine. The install is finally at the
boot where the re-boot occurs. It does, but then hangs at the logo
screen. Because I don't know much about the computer, I am at a loss
as to how to proceed. So I need some insight on the causes of the
hang and what drivers might be out-of-date, where and how to get them,
and how to install them during the installation process.
To anticipate some questions: I have no access to the Win2000
installation, and so cannot delete the partition and reinstall it
later. I can use only OS/2 Ver 4.0 at FixPak 14, as the software that
I need to run (a proprietary data collection and analysis package) is
not guaranteed to run on anything more advanced. My Boot Manager
partition seems to work (and not be thrashed by Win2000) and is
located at the beginning of the disk (it is 7 Mbytes). The OS/2
partition is below the 2 GByte boundary and the 1024 cylinder limit.
No, I will get no help from my IT department: they have no clue about
OS/2.
Thanks for any and all help.
Mark Ensminger
Sidney E. Mathious
before installing Windows 2000. With large drives, you make a disk
manager in the first partition, then the C: drive (where you will
install Windows 2000), then the D: drive where OS/2 will be installed.
After the partitions is created, you can go ahead and install Windows
2000, and then OS/2. OS/2 will find the D: drive where it will install
the OS.
Sidney E. Mathious
Mark Ensminger
Thanks for your reply. You are right, of course. However, I don't
have the option of installing Windows 2000 after installing OS/2. The
computer, which comes preloaded with Windows 2000, Service Pack 4, is
controlled by my IT department. They will not support the
installation of a second OS. They will not install Win2k after I have
installed OS/2, nor will they give me the disks necessary for me to do
the install. So I am stuck with the situation as described.
Mark Ensminger
Mark Ensminger
J. Rebel e-mailed me that I needed to update the hard disk drivers.
He suggested using Dani's drivers. I had in the meantime discovered
that I needed updated drivers and ended up using IDEDASD from IBM. I
am sure that his solution would have worked as well.
I still, though, cannot get the Win2k partition to be recognized by
Boot Manager. It looks like the only way to manipulate Boot Manager
is with FDISK. In FDISK, the only options that I have for the Win2k
partition is to delete it (a bad idea) or to make it bootable. Can
you advise on how to add this partition to the Boot Manager menu?
Thanks.
Mark Ensminger
G-J Rebel
Partition Magic for that.... Perhaps this is the problem, because of the w2k
sp4 installation with ntfs.... It's a long shot, but perhaps worth the try?
"Mark Ensminger" <markden...@compuserve.com> schreef in bericht
news:da366967.04061...@posting.google.com...
Mark Ensminger
I could try the conversion you suggest (from NTFS to FAT32), and check
if Boot Manager will recognize it. If it does, I could then convert
back to NTFS and see if Boot Manager still does. If so, then the
problem is solved. If not, I still have to convert the partition back
to NTFS, because that is the only hard disk file system my IT
department will support. So, do you know if the risks in performing
the conversions are minimal?
Thanks for your help.
Mark Ensminger
G-J Rebel
would be solved, I would not change back to ntfs again. I don't think your
IT department could have any problem with your fat32 file system as it does
not interfere with their systems... As far as I can see, anyway ;-).
Success!
"Mark Ensminger" <markden...@compuserve.com> schreef in bericht
news:da366967.04062...@posting.google.com...
Mark Ensminger
> Boot Manager.
Looking through other traffic in this group made me realize that the
whole partition had to reside within the 1024 cylinder limit. I had
thought that it had to start within the limit, but could cross it.
Shrinking the Win2000 partition to fit under the limit allowed FDISK
to add it to Boot Manager.
Problems solved. Thanks to all.
Mark Ensminger
Wolf Kirchmeir
Agreed, but in doing so you may end up with too-small a partition, esp.
since OS/2 must start within the 1024yl limit, and is much happeir when
it's entirely inside it. I have a 2MB partition for W2K, well inside the
1054 cyl limit, and it's too small. I do install apps on another
partition, but since pretty well all of them put stuff into C:/winnt/, I
have to be vigilant and clean up C: regularly. Besides, W2K is terrible
at maintaining the registry - not that OS/2 is exactly stellar at
keeping its *.ini files in order, but it does a much better job.
We need a radical rethinking of OSs, but that's another rant.
Mark Ensminger
on this drive contains almost 8 Gbyte. I set up OS/2 to be 2 Gbyte
(although I don't think I need anything that big) and Win2000 to be
the remainder. With all the software I am likely to be allowed
already loaded, I still have used only half of the Windows partition.
So I think for now it is big enough. If necessary, I can shrink the
OS/2 partition.
Sidney E. Mathious
the drive and use the first cd of OS/2 and install the partitions needed for
Windows and OS/2. You need a bootmanager partition which is small in size,
but controls which os you will boot to. Once you do that, you can reinstall
Windows 2000 onto the C: partition as normal, and OS/2 onto the D:
partition.
This partition setup worked for me and I used it in OS/2 v3 and v4 with
Windows on the same computer.
Sidney E. Mathious
"Mark Ensminger" <markden...@compuserve.com> wrote in message
news:da366967.04061...@posting.google.com...
Michael Ross
<math...@seark.net> wrote:
>You can install OS/2 on your drive with Windows 2000, but you have to erase
>the drive and use the first cd of OS/2 and install the partitions needed for
>Windows and OS/2. You need a bootmanager partition which is small in size,
>but controls which os you will boot to. Once you do that, you can reinstall
>Windows 2000 onto the C: partition as normal, and OS/2 onto the D:
>partition.
Not entirely true: I just installed OS/2 on a disk which already had
XP in one primary partition, and Win 2003 Datacenter in an extended
partition.
Installed OS/2 in one partition, Bootmanager in the last free primary
partition, and everything was fine.
No need to reformat or blow away windoze - the only gotcha is, the
partition numbers may have changed, so you may have to frell with the
windoze boot.ini file. You'll know this is the case if windoze comes
up with a 'can't find ntoskrnl.exe' message, or something similar,
when you try to boot it.
This can be a problem if windoze boot.ini is on an NTFS partition,
which you can't edit from OS/2 (I was unable to get the alleged OS/2
NTFS read-only IFS working at all; it locked the system solid when I
tried to access the NTFS drive). I got round it by using Partition
Magic to convert the NTFS partition to FAT32; the OS/2 FAT32 IFS
worked perfectly, and I could edit boot.ini.
I got Partition Magic to run by temporarily setting the active
partition back to the windoze partition (instead of Bootmanager) so I
could boot windoze and run it. I could just have edited boot.ini at
this point, within windoze, but I wanted to convert to FAT32 anyway to
move data between windoze OS/2.
M$ dropped HPFS for windoze after NT 3.51; did anyone else ever hack a
3rd-party HPFS for later versions of windoze?
'As I walk along these shores
I am the history within'