• 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

rc5 install

Started by Phil, 2008.11.03, 21:16:33

Previous topic - Next topic

Phil

Hi to the list:

    Can anyone tell me what is loading in the background when the OS2rectangle (upper left corner of screen) leaves,
Then I beleive, The next screen should be ecom splash screen, then graphical install.  My interest is what files are being loaded and in what order  I am interested in accessing the config .sys file and remming out, perhaps drivers one at a time to see if I can get past this hurdle in installing eComstation.  Any advice or suggestions will be greatly appreciated.

Regards Phil

ivan

At the boot blob (OS2rectangle) type Alt + F2.  This should show everything loading.

An alternative is to place a file named ALTF2ON.$$$ in the root dir of the boot drive - this has the same result.

Phil

Ivan:

    Thanks for the response.  Tried your suggestions, shows nothing loading.  I thought if I knew what was loading at that point in time, I might be able to rem out one by one and see if I could over come this problem.

Regards Phil

rdonnelly

Read Biostips.txt at the root of the installation CD. It helped me with alot of my boot up problems.
Just waiting for eCS to have all the features................

RobertM

Phil,

In the initial stages when you see the "boot-blob" (and more specifically, the stage at which you seem to be stuck), it would be the loader and the kernel... followed by the two initializing other services, such as (IIRC) temporary file system "drivers" and doing some work with the BIOS... at which point (again if memory serves), the two begin the OS load and pass off disk access to the storage and file system drivers that the system uses.

Thus, I'd follow rdonelly's suggestion and check the biostips.txt file for some tips that may help. From what you are describing, it doesnt sound like you are getting much further than the loader and/or kernel initialization. That usually is indicative of the two not being able to properly finish some sort of BIOS query that they then use when initializing the necessary memory and chipset support to bypass those BIOS functions (again, IIRC - been a while since I have delved deeply into such).

The only other causes I have seen are the two not being able to operate the storage devie (hard drive - usually), or something on the disk not being correct/there and the two hanging before they can load anything to generate a message.

Robert


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


RobertM

Phil,

On the first point (OS2LDR/OS2KRNL initialization), check your BIOS's memory settings. The following should apply during installation:
(1) Disable all caches

(2) Ensure any memory access parameters are NOT set to OS/2 (anything but OS/2 usually works - most only have "OS/2" and "non-OS/2" as options. If yours has more, let me know what they are).

(3) If the machine is overclocked, (memory and/or CPU), return it to it's normal speed(s).

(4) Unplug any unneccessary add-ins (ie: stuff in the PCI slots you dont need) - unlikely to be the cause though; those would usually exhibit problems later in the install if there was a conflict.




AFTER successful installation, #2 still (and always) applies. #3 may still apply - try overclocking at your own risk, if you intended to. OS/2, even as resource un-intensive as it is, does make more use of certain things, such as the CPU (Ring 2 of the CPU for instance).

Let us know if any of that helps.

-Robert

PS: As a bit of a historical note, #2 (that option in the BIOS) applies to OS/2 v1.x systems only - and does not work with OS/2 v2 or above. Thus, nowadays, it is rarely used. In actuality, I would surmise, it is never used in this day and age (at least not on new hardware) as I doubt that a copy of OS/2 1.x would install on today's newer hardware. Yet, I still see that option in many BIOS's on brand new boards. Kinda funny when you think about it. (Though who knows what copies of OS/2 1.x are out there on support contracts that have been modified to work on newer hardware that is replacing an ancient, dead box? Never know?)


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


The Blue Warper

#6
Hi, Phil!

You can try pressing ALT+F4 when you see the boot blob.  It's the same as ALT+F2, except that ALT+F4 will show the name of the next driver to be loaded, pausing at each one and asking for confirmation.  This way you have a very thorough control on what you want to be loaded.  This should work with non-base drivers, as base drivers are needed by the system in order to correctly initialize itself at boot time.

You said, in reply to a previous post: "Tried your suggestions, shows nothing loading."
So, if you can't get past the boot-blob, this method shouldn't be of great help to you, as the device drivers are loaded in a later stage.  But you should be able to see the drivers being loaded nonetheless (by pressing either ALT+F2 or ALT+F4).
This key combination (ALT+F2 or ALT-F4) should be pressed as soon as you see the rectangle.  Try to press and release it multiple times rather than keeping it pressed once.

If all the above doesn't help, and you still can't get past the boot blob, then you might also want to try booting with an alternative loader, such as the newly rewritten loader by Team OS/4.  You can find it here:
http://hobbes2.nmsu.edu/download/pub/os2/system/patches/warp_4/os2ldr_20080917.zip

Good luck!

Pete

Hi Phil

Sounds like you cannot get the Install CD to boot to the Installer?

Have you played around with the preboot settings "boot with menu for own settings" or similar?

Might be an idea to let us know what hardware is involved; maybe someone has already managed to install to a similar/same system.

Regards

Pete

Andi

Maybe it helps if you describe what you did so far. Did the Boot-CD start? Have you installed RC5 (first phase) and now it hangs on reboot? Or have you copied this installation from another system?

rdonnelly

I made too many primary partitions and had to reformat to be able to use the rest of the non partitioned space. I got rid of eCS1.2, did a fresh install of RC5. After phase1 completed, I shut down the PC because I had an appointment to keep. When I returned a couple of hours later, and booted up a nice cool computer, the rest of the phases went very smoothly with out any system hangs. If your PC has alot of dust in it, get some compressed air and blow it out. That is one of the recommendations to installing this OS, is clean out the dust. And maybe, letting it cool down between phases may help as well.
Just waiting for eCS to have all the features................

Phil

To all for their great suggestions and advice, is much appreciated. I have spent the past several
days working on the suggestions but no progress. Reread the bios tips and found the bios options on this computer are painfully lacking.
not sure how I would handle using a different loader, but will look into that.
    What I have done so far trying to install, Boot from cd creates memory drive and unpacks installation disks
and transfers to mem drive (in this case Z drive) and setsup emulation, seems successful so far arrives at
boot blob, appears to be looking for something, cannot find and aborts.  reverts bact to first menu on CD.
Hope this clarifies the issues I am having
Regards
Phil

Computer hardware:

HP Pavillion dv9623cl Laptop
AMD Turion 64x2 TL58  1.9ghz
2  111 gb hard drives
2 gb ram
1 cd/dvd drive

Device Manager reports
IDE ATA/ATAPI Controllers
2 ea ch 0 ATA controllers
2 ea ch 1 ATA controllers
2ea standard duel ch pciide controllers

1 DVD RW CD ROM
Pioneer DVR K17 ATA device