• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu

Installing Warp 4.52 to an 80 Gig drive

Started by BookWorm, 2009.07.13, 18:29:48

Previous topic - Next topic

BookWorm

> .... 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.

Saijin_Naib

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.

jep

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

Radek

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 ...

BookWorm

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.

Saijin_Naib

#20
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.

RobertM

Quote from: Saijin_Naib on 2009.07.21, 03:13:17
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)
Quote
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"


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


Saijin_Naib

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.

RobertM

Quote from: Saijin_Naib on 2009.07.22, 23:45:01
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...


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|