68kMLA Classic Interface

@MrFahrenheit I have a WGS 95 being delivered this Friday. The person who I've bought it off is ex-Apple and the WGS 95 was used inside Apple. It's got some assets stickers on it which is fun. Unfortunately upgraded to a WGS 9150, so I'll probably swap out the board for a 950 board. But no special cache/scsi PDS card 🙁

Lastly, no software at all or any other artefacts from their time at Apple. So I'm a bit jealous of what you have there in your hand!

Here is an alternative method if you don't want to use filesystem sharing methods...

You can use a tar file as a disk image.

On the Linux or Mac side, create an empty disk image

truncate -s 512M image.dmg

In the A/UX side, for SCSI ID 1, something like

tar -cf - /absolute/or/relative/path/to/directory | dd of=/dev/dsk/c1d0s0

Shutdown the emulated system after that is done.

On the disk image, the tar data will end up at offset 0x19800 bytes (why?).

Then, on the Linux or Mac side, something like

dd if=image.dmg bs=1024 seek=102 | tar -xf - -C /absolute/or/relative/path/to/directory

If you want to do it the opposite way, make sure the tar program is generating compliant archives. One way to do this with GNU tar is with the "--portability" command line argument.


Another tidbit is that you can mount A/UX UFS (not SVFS) filesystems on Linux as read-only.

On the Linux or Mac side, create an empty disk image

truncate -s 512M image.dmg

In the A/UX side, for SCSI ID 1, create filesystem and mount it

newfs /dev/dsk/c1d0s0 Other
mkdir /mnt/disk_mount
mount /dev/dsk/c1d0s0 /mnt/disk_mount

Create a file, then unmount it

echo "Hello World" > /mnt/disk_mount/file.txt
umount /mnt/disk_mount

Shutdown the emulated system after that is done.

On the disk image, the filesystem data will end up at offset 0x19800 bytes (why?).

In the Linux side, mount the disk image (unfortunately read only), then print contents, then unmount

mkdir /mnt/disk_mount
mount -t ufs -o offset=104448,ufstype=old image.dmg /mnt/disk_mount
cat /mnt/disk_mount/file.txt
umount /mnt/disk_mount

pax -w -p | dd bs=512 /dev/dsk/c1d0s31

More tidbits...

If you use e.g. /dev/dsk/c1d0s31 (SCSI ID is 1, slice is 31) then the offset will start at 0 instead of 0x19800 bytes. This means you can simply remove "offset" or "seek" options, reducing the complexity.
The tar data appears to be there immediately in the image and seems to work. But I'm not too sure about how caching is done and if it is safe to use the tar data or write new tar data there.

tar has 100 character limit, and can't save symbolic links or device nodes properly. cpio has 128 character limit.
Use the "pax" tool, which doesn't have these limits.

pax -w -p | dd bs=512 /dev/dsk/c1d0s31

You can use this as a primitive "file sharing" method.

pax -w -p /path/to/directory | dd bs=16384 /dev/rdsk/c1d0s31

Some mistakes in the command: file operand was missing and using rdsk is faster.

pax -w -p /path/to/directory | dd bs=16384 /dev/rdsk/c1d0s31

pax -w -p /path/to/directory | dd bs=16384 of=/dev/rdsk/c1d0s31

mount -v /dev/dsk/c4d0s4 /mnt/optsw

Installing and setting up AUX will be something I would like to do to. LC475 does not work on this even with a full 040, but I have a Quadra610 (not used yet) and a Quadra700 which I am currently setting up via bluescsi because the internal SCSI HDD had some serious issues. My Q700 has a nubus 386 OrangePC and a PPC601 card. Currently I have setup 7.1.2 with the possibility to use the PPC card and I am currently setting up the PC-Section. AFAIK I can install AUX after macos7. my first hdd on Bluescsi is 500MB with 125MB System7, 125MB System8 (not installed jet) 256 Slice3 AUX (not installed).

Which AUX should I use and will there be problems if I activate the PPC card in that machine?

Doc

OK, thx, If I remember that correctly AUX boot's System7 so no use of PPC card with System7 anymore when installing AUX?