Print

[bmwcyclist]

Here is my setup:

LISA 2/10.
Physical floppy not working, will work on soon, don't plan to use if I don't have to.
Physical Widget not working not sounding good, don't plan to use if I don't have to.

FloppyEMU ver C. I have used these for a while on my Apple ]['s
ESProfile v1.0 with Diag

XLerator 16mhz with SCSI (installed)
PFG from Vintage Micros (not yet installed)

Issue:
When I boot to MacWorks Plus II it get to the "?" floppy and it does not recognise the FloppyEMU so I am stuck and unable to load Mac OS (6/7)
Note: floppy images mount just fine from the FloppyEMU when I boot to MacWorks XL 3.0 from my ESProfile.
Is this because I don't have the PFG installed?

Is there a way to boot all the way into MacOS 7.x with the ESProfile?

Anything else I should be aware of?

Thanks!

[jamesdenton]

You will need the PFG installed to proceed with booting MW+II. From what I recall, the behavior is what you are experiencing.

[bmwcyclist]

Thank you!

Once that is installed, does that keep me from running other operating systems?

[jamesdenton]

Thank you!

Once that is installed, does that keep me from running other operating systems?

Nope! Completely transparent and will work with Lisa Office System, Xenix, etc

[bmwcyclist]

Good news, installing the PFG got rid of the "?" icon and I am using MacWorks IIPlus.

However, now none of the previously working LOS images will boot, they just go into an infinite loop of restarting.

[AlexTheCat123]

Do you have your 16MHz XLerator installed while you're trying to boot into LOS? If so, you have to remove it and put the stock 5MHz CPU back in. The 16MHz XLerator messes with the fragile timings that LOS needs in order to read the serial number out of the video state machine ROM, causing it to fail to boot.

[bmwcyclist]

I took the XLerator out and still the same behavior...

[AlexTheCat123]

Strange. Maybe pop the PFG out next and revert things to the exact same configuration that things were in when LOS was working? The PFG shouldn't affect LOS at all (other than changing the SCC clock from 4MHz to 3.672MHz), but clearly something strange is going on here.