Welcome, Guest. Please login or register.

Author Topic: stay with OS 3.1 or update to 3.5?  (Read 4354 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline mr_a500

  • Hero Member
  • *****
  • Join Date: May 2004
  • Posts: 865
    • Show all replies
Re: stay with OS 3.1 or update to 3.5?
« on: January 30, 2006, 03:49:28 PM »
Well, if you've already got 3.5, you might as well try it. Why don't you make 2 bootable partitions - one with 3.5, one with 3.1. Then you can compare and decide for yourself (that's what I did - and decided I like 3.1). Since you have PPC, maybe 3.5 will be better for you.

Quote
I will just have to partition my new SCSI drive into smaller sections so I can use it with 3.1 as from what I remember 3.1 dosent see larger then about 800mb drives.


No, 3.1 can use the first 4Gb with 2Gb max. per partition. If you decide you like 3.1 better, you can always use a utility to extract the 3.5 scsi.device and use it with 3.1 to be able to access partitions beyond 4Gb.

Offline mr_a500

  • Hero Member
  • *****
  • Join Date: May 2004
  • Posts: 865
    • Show all replies
Re: stay with OS 3.1 or update to 3.5?
« Reply #1 on: January 30, 2006, 07:02:28 PM »
Quote
...use HTToolBox to make one bootable and the other not, then if you want to boot from the other make the other one bootable and the original not!


That's a little tedious. I had both bootable and gave my main one higher boot priority. Then when I wanted to boot from the other, I selected it from the early startup menu.

Quote
Isn't having two seperate partitions with two seperate Workbench revisions a little complicated? I mean if you have another partition with your Wordworth or another with your emulators... what OS partition do they look into for C: Libs: MUI: etc.?


It can get complicated, but you just have to make sure the needed files are in both partitions (SnoopDOS can be vital!). I had MUI on my Work partition, so that wasn't a problem. For paths, I used SYS: instead of the volume name so there wasn't a confusion over where it was looking for libs, etc. and so I could disable one partition without it saying insert volume xxxx:

I really didn't have many problems having 2 boot partitions. Probably my #1 problem was the annoying double boot in 3.9 which sometimes caused it to boot back in to 3.1 - causing me to have to select it twice in the early startup menu.