• 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

OS/2 Warp3 Installation Partition Issue

Started by Charl, 2010.03.30, 16:49:34

Previous topic - Next topic

RobertM

If you've installed Boot Manager, make sure that you make the primary partition smaller than the 8032. I generally pick 8000 and let it size it on the correct block boundary.


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


Charl

Fahrvenugen: Wow, thank you for that detailed information!

Quote13. After advanced installer Part 1 finished (the text screen installer), it would not boot (just loop booted)

Is this after the installer copies the files to the HDD?
(Because my installation crashes around 70% copying files to the HDD)

Edit: Also, I feel guilty for asking, do you think it's possible for you to create floppy images for me and upload to a public server?

Fahrvenugen

Hi,

So if I'm understanding correctly, it goes into the blue text-based install screen (part 1 of the install), gets to around 70%, and gives you the "can not find the specified file" error.

Okay, if I recall it is somewhere around the 70% point where it starts reading files off the floppy drive (the boot disk and disk 1).  Also if I recall correctly (I vaguely remember getting this error several years ago) there are some files that *must* be on those disks when it reaches that point of the install, even though OS/2 doesn't use them (don't ask me to recall which file in particular it is looking for).  What I think I did to get around it is...

-Have a copy of the *original boot disk* and the *original disk 1* on floppy
-Also have the modified boot disk and disk 1
-Use the modified boot disk and disk 1 to start the install process
-Once the install process reaches the point of starting to copy stuff from the CD, swap the modified Disk 1 from the floppy  with the original Disk 1
-When it asks for the install disk and disk 1, use the originals
-Once it completes part 1, then reboot from the modified boot disks and perform steps 14 - 20 from the above

If course the other thing to consider - if it is reading from the CD at the point the error comes up, you might have a bad CD (or a CD that is missing some file)


Charl

Fahrvenugen, you are amazing for remembering :)

It went past the 70% mark and completed the first part of the setup.

Unfortunately for me, I'm unable to work on this for now. (I've got more pressing concerns)

I'll work on it again next week.

Thanks again all!

Charl

Ok! Sooo I made time for this because I was very optimistic  :)

When I try and boot off the HDD after part 1 of the installation, the PC just doesn't boot.
It just sits at the place you expect the OS/2 Warp 3 screen.

So I boot off the floppies and do the changes you recommend. (I copied the ADD files as well and changed the config.sys as well)

No luck! Still just sits like it wants to boot, but doesn't.

Any insight? (I'm going to take a look at the issue again tomorrow)

Fahrvenugen

Hi again,

It *might* need an sysinstx command

To do this, boot from your boot floppies (the updated ones)

When you get to the install screen asking for easy install / advanced install, hit F3 to go to a command prompt.

Switch to your C: drive, enter:

c:

Pop your Disk 0 (the boot disk) into Drive A

Then type:

a:sysinstx c:

It should give you some message about transferred system files.

Also, check your config.sys file on the C drive (use tedit) and you can try REMing out some of the unneeded .FLT device drivers.  I know the ones for SONY can cause trouble. 

You can do the same with a lot of the .ADD's.  Out of these, you for sure need danis506.add and ibm1flpy.add.  The rest you can probably rem out.

If that doesn't work, I'll have to go through the process again on my test machine and see if I missed anything.

Admittedly, getting Warp 3 to install on modern hardware isn't for the faint of heart!



Charl

QuoteAdmittedly, getting Warp 3 to install on modern hardware isn't for the faint of heart!

That's no lie!

I'm going to give it a go this morning and will give feedback as soon as I can.

Charl

#22
Ok! Sooo...

I REMed out:

BASEDEV=SONYCDS1.FLT
BASEDEV=SONY535.ADD
BASEDEV=SONY31A.ADD

I also tried the a:sysinstx c: and I get the following error message:

The type of file system for the disk is HPFS.
The system files have been transferred.

I'm sorry to burden you with the OS/2 issues  :(

Edit: lol, I thought that was an error message... Maybe I should read, or maybe I'm just expecting the OS not to work. Must be my negativity  ;D
hehe, anyways, it's still standing still at the point where it's suppose to boot.

I've tried a clean install without the boot loader partition as well (Same issue)

RobertM

Try FDISK and set the partition as... Startable (I think... it's either that or Bootable).

BUT, if BootManager is still installed, set THAT partition as Bootable, and then go into your Boot Manager options and select the boot partition there.

Remember to save all changes before exiting and then reboot.


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


Charl

Hey RobertM,

FDISK reports that the partition status is 'Startable'
Also that Access is 'C: Primary' with FS Type 'HPFS'

Partition size is 8001MB

ivan

Hi Charl,

Sorry it has taken longer than anticipated to get back to you - unfortunatly work must come first even though I'm supposed to be retired.

First up, Fahrvenugen set out most of what you have to do in extremely good detail.  The one thing we did to stop the problem of the installer not finding files on disk 1 was to use a stub with the name of each file we removed.

Concerning the not booting problem you have.  Did you read the readme in the idedasd package especially the section on large hard disks?  If not do so and you may find the answer to your problem.  I have never installed OS/2 on a partition larger then 2 GB - warp 3 is more than happy on a 1 GB partition - in fact the two working boxes we have here with warp 3 connect on them have the boot partition set at 600 MB on 80 GB drives.

Fahrvenugen

Charl,

Try a smaller partition for your boot partition.  I've never tried installing Warp 3 on anything bigger then a 1 GB partition, but I do know there are partition size limitations beyond which it just won't boot.

Ive found that for Warp 3, a 500 MB boot partition is one of the best sizes.  Room for the entire OS (which even with fixpaks and all the networking stuff installed is still a max of about 100 MB), room for a few core apps, and then if it happens to lose power or that machine gets rebooted without a proper shutdown, the Drive C only takes a few minutes to go through the chkdsk, and if you're lucky the data partition might not have a dirty flag and not go through chkdsk.

And trust me - that's an important thing to consider.  I've had situations where my 60 GB (data) partition took over 20 minutes to chkdsk after an improper shutdown and the dirty flag remained on!


Charl

Thanks all for the input!

I'll give it a go this morning :)