Welcome, Guest. Please login or register.

Author Topic: A2091 + KS1.3 + WB1.3 Floppy = Frustration  (Read 3584 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Thomas

Re: SOLVED! Was: A2091 + KS1.3 + WB1.3 Floppy = Frustration
« Reply #14 from previous page: June 02, 2015, 10:14:24 AM »
Quote from: bozimmerman;790427
My best guess is that, when booting any of the Workbench Floppys (and many games apparently fall into this category), they will always Mount any drives they find, including the hard drive.


Harddrives are mounted by the Kickstart before it even checks for floppy disks. You cannot avoid it unless the harddisk controller has an off-switch.



Quote
 However, my hard drive had the International FS which 1.3 didn't have a driver for, thus generating the "insert volume LIBS" prompt.


This is not the reason, at least not completely. FFS Intl. does work on Kick 1.3 if it is installed correctly on the harddrive.



Quote
To be sure, I partitioned the new hard drive as FFS, and "unchecked" FFS when I Quick-Formatted it.


This is not a good idea. By unchecking FFS you made it OFS. OFS has a very small partition size limit (8 MB or so). If your partition is bigger it will corrupt sooner or later. And it is sloooow. That's why FFS is called Fast File System. You should keep FFS, only uncheck Intl and DirCache.

guest11527

  • Guest
Re: SOLVED! Was: A2091 + KS1.3 + WB1.3 Floppy = Frustration
« Reply #15 on: June 02, 2015, 09:51:01 PM »
Quote from: Thomas;790436
You should keep FFS, only uncheck Intl and DirCache.

As you said, there is really nothing wrong with FFS and kickstart 1.3. It does not require anything fancy. There is neither anything wrong with the international support in FFS, it does not reqiure the locale.library or anything else from 3.1. In fact, it is in most cases recommendable that you use this version of FFS to have international file names supported correctly. DirCache does, however, usually not add much value.  A common problem with FFS is however a different one: It cannot access files beyond the 4GB barrier, at least not without the kludge "NSDPatch" that comes with Os 3.9. And this kludge does not exist in Os 1.3.
 

Offline bozimmermanTopic starter

  • Newbie
  • *
  • Join Date: Feb 2015
  • Posts: 19
    • Show only replies by bozimmerman
Re: SOLVED! Was: A2091 + KS1.3 + WB1.3 Floppy = Frustration
« Reply #16 on: June 03, 2015, 05:40:21 PM »
Quote from: Thomas;790436
You should keep FFS, only uncheck Intl and DirCache.


Do you know of any tool that will change the partition marker from DOS/3 to DOS/1?  When you say "Unchecking International" .. I know I can choose NOT to format a drive Intl by not-checking the box, but is there any way to un-do it?

- Bo
 

Offline zipper

Re: SOLVED! Was: A2091 + KS1.3 + WB1.3 Floppy = Frustration
« Reply #17 on: June 03, 2015, 08:31:55 PM »
ReOrg can convert the file system.
 

Offline bozimmermanTopic starter

  • Newbie
  • *
  • Join Date: Feb 2015
  • Posts: 19
    • Show only replies by bozimmerman
Re: SOLVED! Was: A2091 + KS1.3 + WB1.3 Floppy = Frustration
« Reply #18 on: June 03, 2015, 08:40:29 PM »
Quote from: zipper;790535
ReOrg can convert the file system.


Thanks, though (and I feel awful for saying this NOW), ReOrg worked great on on partition, but ran out of memory on the primary partition (more stuff).

I don't suppose there's another alternative?
 

Offline zipper

Re: SOLVED! Was: A2091 + KS1.3 + WB1.3 Floppy = Frustration
« Reply #19 on: June 03, 2015, 09:13:58 PM »
Seems that ReOrg needs about 2 MB memory for a 200MB HD. have you tried avail flush before launching ReOrg?
 

Offline danbeaver

Re: A2091 + KS1.3 + WB1.3 Floppy = Frustration
« Reply #20 on: June 03, 2015, 09:29:18 PM »
You could have changed to filesystem descriptor too from 03 to 01
 

Offline Oldsmobile_Mike

Re: A2091 + KS1.3 + WB1.3 Floppy = Frustration
« Reply #21 on: June 03, 2015, 10:07:44 PM »
I hope you are not using ReOrg on a partition larger than 4GB!  Otherwise, it's great software and I have fond memories of it from back in the day.  A bit useless in this era of CF cards and many-GB drives, however.
Amiga 500: 2MB Chip|16MB Fast|30MHz 68030+68882|3.9|Indivision ECS|GVP A500HD+|Mechware card reader + 8GB CF|Cocolino|SCSI DVD-RAM
Amiga 2000: 2MB Chip|136MB Fast|50MHz 68060|3.9|Indivision ECS + GVP Spectrum|Mechware card reader + 8GB CF|AD516|X-Surf 100|RapidRoad|Cocolino|SCSI CD-RW
 Amiga videos and other misc. stuff at https://www.youtube.com/CompTechMike/videos