Changing the size of an existing disk in Basilisk II (on mac)

This page is a wiki. Please login or create an account to begin editing.

13 posts / 0 new

2013, March 11 - 6:34pm

Offline

Joined: 2013 Feb 26

Changing the size of an existing disk in Basilisk II (on mac)

I followed the setup guide for Basilisk II and everything works great. I just got a game that I want to try but when I mount it from the shared folder it says it "cannot be mounted from the disk it is currently on". No biggy, move it to the boot disk, I've done this before and it works. Only problem is that this file is larger than my 500mb boot disk.

So here's my question. Can I alter the size of that disk without deleting it and recreating the entire thing?

P.S. apologies if this has been asked/answered. I couldn't find a thread.

Thanks in advance

Comments

2013, March 11 - 7:29pm

IIGS_User

Offline

Joined: 2009 Apr 8

I don't know if that's possible, but you could add another virtual drive to Bas using its GUI application.
Maybe needs to be initialized/formatted within Bas for the very first time.

2013, March 11 - 9:21pm

(Reply to #2) #3

absolutelee

Offline

Joined: 2013 Feb 26

@IIGS_User: I guess that leads to another question. When it says "cannot be mounted from the disk it is currently on" I take that to mean it needs to be on the boot disk. Wouldn't adding another drive present the same problem as trying to open it from the unix drive (named according to the basilisk II setup guide on this site). That's why I wanted to get it on the boot disk. I had the same problem when trying to play The Dark Queen of Krynn, and that worked when I moved it to the boot drive. That's like a 5MB game though so I didn't have this capacity issue.

Also, I left out some details. I'm trying to mount this with 'Disk Copy', which is what I've used to mount every other disk I've gotten here. I have tried mounting with a copy of disk copy on the storage disk and with a separate copy of the program on my boot disk.

@24bit: I'm sorry but I'm not understanding how this helps make the file fit on my boot disk.

Thank you both for your responses

2013, March 11 - 9:58pm

(Reply to #4) #4

MikeTomTom

Offline

Joined: 2009 Dec 7

"cannot be mounted from the disk it is currently on"

The "unix" drive should only be used to transfer files between the emulated hard drive and the host computer. It is very dangerous to work with files in the "unix" drive other than as a "go-between" as classic Mac files can be made unusable if run from within this drive.

You can easily create further classic Mac "hard disk" image files much larger than 500 MB and mount them in the same emulated session.

You can also, mount large image files in the emulator by adding them to the list of drives before starting an emulated session. This way large image files will mount on the emulated desktop as a hard drive disk and you can access the contents that way, negating the need to create a drive for it.

If your B-II session is windowed and not full-screen you can also drag an image file from your host computer into the B-II window and it will mount as a disk drive this way, too.

In order for image files to mount, they need to be in a suitable format, i.e. Uncompressed disk image. Either drag or add to the list of hard drives and see if it mounts OK.

HTH

2013, March 11 - 10:38pm

24bit

Offline

Joined: 2010 Nov 19

Resizing a existing image is not possible, I suppose, but its easy to create disk images of almost any desired size as big uncompressed dmg in OSX for use with emulators.
Basilisk_II will ask whether a new (big) image should be initialized, when mounted for the first time.
Copy the stuff from your small disk to it, open system folder once to have it blessed to make it bootable.
A 2GB dmg should be able to hold all kinds of files for the Classic Mac OS.
Always copy your files to the emulated hard disk, not to the desktop of the emulated Mac.

2013, March 12 - 3:43pm

absolutelee

Offline

Joined: 2013 Feb 26

Thank you so much MikeTomTom. I misunderstood how the whole program was working. It all makes sense now

2013, July 28 - 10:39pm

kd0tpc

Offline

Joined: 2013 Jul 23

Since you say that you are using the Mac OS version of Basilisk II; Have you tried one of the many DiskCopy aids that provides the ability to resize a DiskCopy image? You may have to boot in Mac OS 8.1 or earlier in order to do so.

Also where did you find the Mac version of Basilisk II? My old copy is corrupt (used an archiver that requires resource forks, and forgot to binhex before backing up on an ISO9660 CD). Has some one finaly updated the Mac Version?? I have not seen it in a long long time.

@MikeTomTom:
On the Macintosh version of Basilisk II it does not say Unix, it says MacHost (or in some earlier versions just Host).

2013, July 28 - 11:55pm

(Reply to #7) #8

MikeTomTom

Offline

Joined: 2009 Dec 7

@kd0tpc: Your copy of Basilisk II must be very old (the shared drive is now called "Unix"). You can find more recent builds of Basilisk II via the E-Maculation pages.

It was the OP who bought up the term "unix" not me, however, you can find the reference that he was alluding to on this E-Maculation page in the chapter with the heading beginning; "The shared folder". Also further down in same page under the heading "The shared folder / "Unix" disk".

2013, July 29 - 4:55pm

(Reply to #8) #9

kd0tpc

Offline

Joined: 2013 Jul 23

@MikeTomTom:
I thank you for the info on the renaming of the Shared Folder/Virtual Drive.

I can only find versions of Basilisk II for Windows, Darwin OS X (Some say 'Mac OS X'), and Linux on the E-Maculation page. If you could point me to the download for the more recent Mac OS/Macintosh System Software versions I would appreciate it much. I would love to get a copy of the most recent version that is not Corbonized (I run Macintosh System Software 7.5.5, and Mac OS 8.1 on my PowerPC Macintosh), as there are a good number of old 68k apps that just refuse to run on the PowerPC systems (I assume that this is the reason for the Macintosh port to start with).

Thank you much.

2013, July 29 - 11:55pm

(Reply to #9) #10

MikeTomTom

Offline

Joined: 2009 Dec 7

@kd0tpc: Well, you've got me stumped there. I'm not aware of there ever being a Basilisk II port to a PPC classic Mac OS 9.x or earlier Macintosh. The only ports I'm aware of were to Linux, Windows, Mac OS X and BeOS - I guess there were others, as the source is free to compile.

The only 68k Mac emulator I know of that is actively supported to run on pre-OS X Macintosh PPC (and even 68x0) hardware is Mini vMac, which can be made to emulate most 68000 Macs and also a 68020 Mac II (alpha builds). See the Mini vMac Options page for hints on variations and builds.

2013, July 30 - 12:16am

#11

kd0tpc

Offline

Joined: 2013 Jul 23

Ok thank you for that.

Also the Forum tittle is a bit misleading as it specifies "Basilisk II on Mac", so what version of basilisk II is @absolutelee using if not the Mac OS version? Especially noting that your list leaves the Mac out.

2013, July 30 - 2:08pm

(Reply to #11) #12

MikeTomTom

Offline

Joined: 2009 Dec 7

@kd0tpc:

Also the Forum tittle is a bit misleading

Then you must be confused by what is a hardware issue. Somehow you are associating the word "mac" in the subject title with a classic "Mac OS", which it simply is not and never was.
Anyway, you are digressing. This topic was answered in post #5 and resolved in post #6

2013, July 30 - 7:05pm

#13

bertyboy

Offline

Joined: 2009 Jun 14

Back to the original post - the use of Terminal's hdiutil resize may help here.

I used Disk Utility to create all my disk images for Basilisk and mini vMac. so I would expect that I can resize them later. I've used the resize extensively to enlarge and shrink other (secure) disk images, but not for use with Basilisk.

Give it a try.