• Please review our updated Terms and Rules here

PET 4032 - can't run d64 images from PETdisk MAX v2

You did not say what command you used. Did you mount the image using this command:

load "$: petrobots-shareware v1.1.d64", 8

NOTE: do NOT use space after the colon. I had to show it with a space to avoid an unwanted smiley.

Then list the directory to view the files.
 
Hmm, not sure what I'm doing wrong here.

I loaded the wedge first. Is this required?

I don't get any lowercase characters. Is this normal?

wedge.jpeg

I've renamed the file to just petrobots.d64. I tried `load "$: PETROBOTS.D64", 8` but no luck.
 
That command should not need the wedge. There is another command that uses the wedge. I’ll have to look it up.
You are using the normal/graphic character set that is usually used for games.
 
I picked up a petdisk for my 8032 and was also not able to load d64 images, though if I extract the d64's into directories then I can load stuff just fine.
 
I picked up a petdisk for my 8032 and was also not able to load d64 images, though if I extract the d64's into directories then I can load stuff just fine.
Click to expand...

How do you do this?
 
It looks like from the video that you:

load "$:xxx.d64",8

Which effectively mounts the .d64 file and then you can list and load/run the programs/files within the d64 file.

This is a function of the PETdisk MAX V2.

The wedge also has some shortcuts...

Dave
 
Instructions are here.
https://github.com/bitfixer/petdisk-max

Are you able to get a directory of the root of the SD card?

One possibility is a corrupt or non standard .d64 file,
but one likely possibility is a problem with the 6520 that drives the IEEE port.

Also note, I've done some testing for Bitfixer and have found that it doesn't always behave properly when another IEEE drive is connected and powered on.
There's something with the timing when there's another device on the bus but it should work fine if the other drive is off.
 
Last edited:

From the max GitHub page. Note that there are no spaces in the command line.​

D64​


The PETdisk MAX currently supports D64 files for both reading and writing. To mount a D64 file stored on either an SD card or network drive, use the following command: LOAD"$:filename.d64",devicenumber

This will mount the D64 file as the disk for the specified device number. It will also load the directory of the disk image which can be viewed with LIST.

To unmount the D64 file and return to the original device, use LOAD"$:..",devicenumber
 
I don't think it's a matter of not understanding how to use the petdisk. I was in communication with bitfixer with mine through email and I was not told "I'm doing it wrong", I attempted to load the d64 exactly as you describe and exactly as the documentation describes (the same):
LOAD"$:filename.d64",devicenumber

Every d64 I tried it would come over corrupt. If I used DirMaster to pull those files out and put them into a subdirectory on the SD card then it would load on the pet just fine.
I never got an answer from bitfixer on this subject, the last I heard on it was "Thanks, it's possible I had some regression in d64 support. Will check it out.".

My guess is that people reporting that petdisk is working with d64's just fine are using an older firmware and maybe a bug got into a newer version of the firmware which somehow broke d64 support but I don't know that's just a guess on my part.

Don't get me wrong I'm still happy with it, sure beats trying to load stuff off of a datasette, but d64 support would be nice.
 
You can use the wedge commands to mount the d64 file.

@cd: petrobots.d64 (as above... no space between : and p, and then enter) will mount the d64 as a virtual disk. From there you can load the program file.

eg -

dload"*

See how that goes.
 
OK.

PET 3016 with Tynemouth board and v 4 ROMS. Tynemouth board set to use the motherboard ROMS (ie disable the Tynemouth ROMs) and enable the 32K RAM on the Tynemouth board.

No other devices physically connected except for the PET DISK MAX 2

PET DISK MAX 2 has the latest firmware available from here:

github.com

petdisk-max/firmware at main · bitfixer/petdisk-max

Firmware and schematics for the PETdisk MAX storage device for Commodore PET - bitfixer/petdisk-max
github.com github.com

PET DISK MAX 2 set to device id 8

The only file apart from the configuration file on the SD card is the file downloaded from the web site above. I renamed the file to PETROBOTS.D64

LOAD"$: PETROBOTS.D64",8 works (see attached photos) [note no space used]

I then get a directory listing.

Pressing Shift+Run didn't work, but manually loading PETROBOTS worked fine.

Screenshots attached.

Colin.
 

Attachments

  • PXL_20230607_151732724.jpg
    PXL_20230607_151732724.jpg
    2.3 MB · Views: 14
  • PXL_20230607_151812418.jpg
    PXL_20230607_151812418.jpg
    2.1 MB · Views: 15
  • PXL_20230607_151830190.jpg
    PXL_20230607_151830190.jpg
    2.2 MB · Views: 15
  • PXL_20230607_151853829.jpg
    PXL_20230607_151853829.jpg
    1.9 MB · Views: 15
  • PXL_20230607_151903600.jpg
    PXL_20230607_151903600.jpg
    2.1 MB · Views: 15
I tried loading the wedge and then loading the d64 file:

IMG-0479.jpg

I tried loading the d64 directly without the wedge:

IMG-0480.jpg

It just hangs. I emailed bitfixer and got this response so I am hopeful:
Hi, Thanks for your email. Yes, they definitely should work. The
command looks okay, although there should not be a space in there, not
sure if that was in your original command or not. Basically
LOAD"$:pETROBOTS.D64",8
should work.
After you run this, a LIST should show all the files in that D64 image.
If that's not working, I would try double checking that your sd card
is a single partition, formatted as FAT32. It probably is already, or
wouldnt' have gotten that far.
Happy to help further if things are not working - I'm away from my PET
test setup for a few days though so will be able to help more next
week.
Sorry it's not fully working right now, but we'll figure out what's
wrong with it. Monday or tuesday next week I'll have more ability to
check things. Thanks
Click to expand...
 
I would test the IEEE488 port on your PET in the intervening time just to make sure everything is working correctly.

I know you say that you have used it with something else (?) - but I would still use the diagnostic program nonetheless...

Dave
 
You must log in or register to reply here.
Back
Top