General Category > LisaList2
Max ESProfile Image (volume) Size?
bmwcyclist:
The external ESPROFILE has the large profile.image file. The LED is green so it seems to like it.
I know the external works well cause I boot off it all the time.
However, the Mac works installer seems to only see my internal ESPROFILE.
I didn't mean this to turn into a troubleshooting thread, but your help would be appreciated because it would be nice to be able to make profile images quick and easy.
ried:
On macOS 26.0 (Tahoe) you can use Terminal and dd to create a blank image in whatever size you'd like. For example, open Terminal and change to your directory of choice (i.e. "cd Desktop") and then...
--- Code: ---dd if=/dev/zero of=HD200.img bs=1M count=200
--- End code ---
That should generate a blank file called HD200.img that's ~200MB in size.
bmwcyclist:
--- Quote from: ried on September 26, 2025, 02:59:52 pm ---On macOS 26.0 (Tahoe) you can use Terminal and dd to create a blank image in whatever size you'd like. For example, open Terminal and change to your directory of choice (i.e. "cd Desktop") and then...
--- Code: ---dd if=/dev/zero of=HD200.img bs=1M count=200
--- End code ---
That should generate a blank file called HD200.img that's ~200MB in size.
--- End quote ---
I don't have a modern Macintosh.
I have several utilities to make.IMG files if that's all that's needed, but I was under the impression that a profile.image file is not the same format.
sigma7:
--- Quote from: bmwcyclist on September 26, 2025, 03:19:56 pm ---I don't have a modern Macintosh.
--- End quote ---
Do you have anything running OSX? If so, what version?
If not, what OS are you using/have available to put stuff on the SD card?
--- Quote ---I have several utilities to make.IMG files if that's all that's needed, but I was under the impression that a profile.image file is not the same format.
--- End quote ---
That's correct, the emulated ProFile image files (as used by eg. the ESProFile) are not the same as .img files created from floppies, MacOS hard disks, CDs etc.
--- Quote ---Looks like BLU does not want to touch it.
--- End quote ---
Please provide more info: Does BLU recognize there is a parallel port card (If not, it is likely a hardware problem)? If so, does it recognize there is a hard disk attached to it (If not, it is likely a hardware problem)? If so, what happens when you try to access it?
Note that BLU isn't capable of "initializing" disks, meaning the process of configuring the disk for use by an operating system, creating a root directory, boot blocks, and so on. The "format" function implemented in BLU is a lower level operation that configures the magnetic media into sectors.
However, BLU may still be a useful tool in cases such as this to help identify why the operating system installer cannot initialize the drive.
--- Quote ---I'm not sure that BLU knows how to deal with big disks like that.
--- End quote ---
I believe BLU will be comfortable up to the limit of 16M blocks (about 8GB).
--- Quote ---limitations when it comes to size under MW
--- End quote ---
From the screen pic it looks like you are using MW+II, but for completeness: MacWorks XL (preceding MacWorks Plus and MacWorks Plus II) is limited to MFS, which according to wikipedia, was limited to 20MB volumes.
edit: attempted to decrease the number of typos
bmwcyclist:
Thank you for the replies! Here are the answers to your questions.
1. I manage my image primarily using a Windows operating system.
I can copy the files and rename them, but of course I cannot mount them.
When I work with my BLUESCSI images, I just mount them to basilisk.
2. Thank you for confirming. I figured with a different Block size as well as the fact I think all of the MAC utilities are looking for a SCSI device and not a parallel device. This would be an issue.
3. Sorry, I was not more detailed.. the parallel port card works great. Blu could see "something" (I didn't take a screenshot sorry) but would not low level format. It gave me an error along the lines of this is not a 5 or10 meg profile..
I didn't go to the BLU utility at first because from the above description I thought it would show up as simply volume that needed formatting. That didn't happen and none of my utilities could see a non-SCSI drive. It seemed worth giving it a shot.
4. So I'm still left wondering why my Mac works 2+ is not seeing the ESPROFILE with a "raw" file name profile.image. The ESPROFILE led is green and it is a good working unit.
How the heck do people make their formatted blank .image files if they don't download an already made one.?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version