Re: Boot jfs in the bootmanager...

Rich Walsh wrote:
On Thu, 6 Sep 2007 01:58:16 UTC, "James J. Weinkam" <jjw@xxxxxxxxx> wrote:

To be more specific here is what happens when the eCS2.0RC2 installation on the JFS volume will not boot: The bootmanager screen appears and I select the JFS installation. The boot blob appears with a line at the bottom about the eCS JFS boot code. The eCS logo appears.

Following this one of two things has happened on each of many attempts:

1. The eCS logo stays on the screen and nothing happens. Ctrl-Alt-Del does nothing. Power down in necessary

2. The ACPI driver loads, followed by the message, "This driver is licensed only for use with e Com Station. The system is unable to operate your hard drive, the system is stopped." Again power down is necessary.

The "OS/2 is unable to operate..." message is the result of letting older
versions of OS/2-eCS autocheck your v2.0 drive. The boot sector doesn't
look right to a non-bootable version of JFS, so it "fixes" it, rendering it
unbootable. On your older installations, you have to change the JFS /AUTOCHECK
parameter from '*' to an explicit list of drives that excludes the bootable
volume.

E.g., my eCS 2.0 rc2 drive is letter 'K', so the IFS line for my primary
system (on an HPFS drive F:) is:

IFS=F:\OS2\JFS.IFS /LW:5,20,4 /AUTOCHECK:GHIM

FYI, this may disable access to the drive in question from the older system
if the volume is dirty or its non-bootable JFS _thinks_ it's dirty.

Also... for rc1, I had to remove PSD=ACPI.PSD to avoid random hangs during
bootup. OTOH, with rc2, it actually works! (sorta) For the first time
ever under OS/2, shutdown turns off the machine. Sadly, 'suspend' does
absolutely nothing.


Thank you for your thoughtful suggestions.

I am not entirely convinced that letting mcp2 check the drive is responsible because as I had stated in my original post, I had backed up several times as I reached milestones I wanted to be able to return to in case of trouble. On some of these occasions, I did more than back up the partition, such as fixing config,sys when a typo made the partition unbootable. In short, the volume was check disked and modified by the mcp2 installation at least eight or ten times before it suddenly refused to boot. I think this shows there is more to it than autocheck fouling up the partition.

Nevertheless, based on your statement, I just did the following:

1. Exteacr the JFS version of OS2BOOT from one of the backups of the JFS partition to h:\ecs.

2. Shut down and boot from the install disk.

3. Go to the maintenance console and use the disk->volume management tool to chnage the drive letter of the HPFS version of eCS2.0RC2 that I have been running the last couple of days from i to n.

4. Resume the advanced install and create a new volume lettered i and long format it JFS.

5. Cancel the install and return to management mode.

6. From a command line, XCOPY n: i: /h/o/t/s/e/r/v
COPY h:\ecs\OS2BOOT i:\

I did this rather than restore one of the JFS backups because I didn't want to lose the changes that have been made since I converted to HPFS,

7. Shutdown and reboot.

This booted on the third try. On the first two tries it reached the eCS logo and sat there for several minutes until I gave up. Unlike the previous occasions, however, the system was not frozen; Ctrl-Alt-Delete worked.

So far I have not remed out ACPI.

I will mess around with this for a few days and see if I can narrow the problem down. If something is causing "random" booting problems, the probability of boot failure does not seem to be constant. I must have done at least twenty boots of the initial JFS installation (not all of them involving going to mcp2 in between) before the initial failure occurred. Once that happened the first time I was able to get in more successful boots by booting from the maintenance partition mcp2 and running JFSCHK32. (I left out this detail in my original post for the sake of brevity.) After that the next time it happened nothing I could think of restored bootability.

Thanks again for the tip.
.

Relevant Pages

  • Re: New XP Installation on new hard drive - will not read from CD
    ... >>Assuming your system is set to boot from the CD-ROM ... >>To Repair a Windows XP Installation using Recovery ... drive and both CD drives are ...
    (microsoft.public.windowsxp.basics)
  • Re: XP Home and XP Pro on two separate drives
    ... , while the CD and DVD drives are on the other ... slave and boot from my old XP configuration (with the old drive as ... :> In the case of SATA HDs, the default HD boot order is just ... :> During installation of WinXP, ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: moving from FC 5 to FC 8
    ... New computer now has 3 hard drives in the following configuration. ... sdb - new 500 GB drive with Windows Vista ... Used the BIOS to alter the boot sequence to: ... So I'm pretty sure that the Kubuntu installation left the MBR on sdb intact from the Windows installation and upgraded the GRUB installation on sda from the FC 5 installation. ...
    (Fedora)
  • Re: Boot problems with RAID
    ... did boot up OK. ... I wanted to avoid having to un-RAID the drives as the rebuild takes an age ... drives hooked up and reboot to the old XP install but what would have ... See if you can boot the installation ...
    (microsoft.public.windowsxp.general)
  • Re: Boot problems with RAID
    ... The drives would definitely have been different now as I had booted to, and performed some actions on, just one of the 750s. ... Maybe I was daft to leave the drives hooked up and reboot to the old XP install but what would have happened to cause my problem? ... I don't know what to make of the fact that the array looks ok from the system ROM or that the Recovery Console's map command appears to see it correctly, but the error message about disk hardware configuration problems tells us its trying to boot from the wrong disk or from a disk that is not on the system, the boot.ini file points to an invalid location. ... See if you can boot the installation with a boot floppy. ...
    (microsoft.public.windowsxp.general)