As far as I know, the only version of Basilisk II that works with MacsBug is Windows build 142. And even then, it only works under the right set-up, and you'll still get error messages on each time you enter or step. I think it was due to a missing implementation for a MOVE to/from SR instruction.

The command line parser is including all of the options in the file name path.

Try putting the file= at the end instead of at the beginning:

Silent exit on launch means the error message should be in the stderr text file.

Odd; 68040 has an FPU built-in, so there should be no situation where someone has an 040 without FPU. This means either we've got a setting for a fictional configuration, or 68040 with no fpu still attempts FPU, making it a misleading configuration. There were Macs shipped with a 68LC040. My Perfor...

Copying to the Mac OS system desktop requires holding down the option key when dragging. Unlike Windows, Mac OS makes a Desktop Folder for every disk volume, and by default the Finder will move the file within the volume. The option key tells the Finder to necessarily copy instead of move (at least ...

I remember being able to configure the power button to F15 for build 142 years ago, and it worked, being able to enter MacsBug via Alt-F15. (The incomplete 68k CPU emulation broke instruction stepping in MacsBug, but having a debugger is better than not having one.) As far as I know, the problem her...

First of all, I'm glad to see that Paul managed to get the emulated Apple Sound Chip working, that the sound plays as well as it does, without breakup. Testing out the latest version, I see that System 7 sounds played in the Finder are interrupted before completion. Incorrect sound buffer completion...

One final update here. The full library has since become “adequate” in that it now handles TrueType and color fonts, GIF animations and JPEGs, and renders PICT images with support for vector graphics and text. Much of the PICT results are pixel-for-pixel identical to QuickDraw rendering with the lat...

Is the black screen issue back? It was fixed here: http://www.emaculation.com/forum/viewtopic.php?f=6&t=6128&p=44856#p44856 Yes, dougg3 made it clear that the ordering of addressing is critical (RAM before ROM). His submission fixed the black-screen-on-startup issue with Windows builds. Thi...

Possibly it has something to do with how the ROM allocates memory for video RAM; could be a related bug in BII, or just that the original hardware couldn't handle that. The ROMs supported by Basilisk II always expect the allocation to be in hardware (VRAM). (Only the earliest ROMs allocated this me...

The version information of course should viewable via File:Properties:Details. However, the newer builds omit Windows module resources, including a version number. There's always an About dialog in the older Windows-specific x86 builds; if there is no About dialog, it's an SDL build. I've downloaded...

SoftwareFPU is not necessary here. Wolfenstein 3D uses the software-based SANE (Standard Apple Numerics Environment) for floating-point calculations. The problem lies in the fact that SANE utilizes the FPU when it’s available, so the bugs in an FPU can be reflected anywhere floating-point calculatio...

Wolfenstein 3D uses floating-point calculations to build the trig tables (needed for rendering and movement), which if these fail (namely with Mini vMac), the game will render horribly and eventually crash.

Try turning 68K FPU emulation off ("fpu false").

It depends on the build and keyboard you’re using. Left-Windows as Option works with my Dell keyboard, running 8.1. Rarely is there an issue with builds 142 and 143, but the start screen also comes up with the SDL builds. It may be that SDL doesn’t have all of the keys mapped. What keyboard are you ...

I don't think there was ever a "free" version of Stuffit. (Stuffit Lite comes to mind, but that was shareware too.) Yes, Stuffit Lite is shareware, but it carries no expiration date (merely complains); it lacks some of the features of Deluxe, handles only older archives (I have version 3....

The emulator doesn’t really do drag & drop with the native system.  And the only thing it opens (from the command line or dropping a file onto the program icon) is allow the user to select a system ROM to load, not a document (such a web page). Use the Virtual Desktop folder to copy files.  It s...

Testing this MacPaint build, it shows to have some drawing code of its own, but I only see this apply to screen drawing (including Fat Bits, which was incorporated into HyperCard). The program expects the screen to be 1-bit (black & white) with a screen width of exactly 512, much like Pinball Co...

I've been trying to find a good 68040LC rom that I can use without the UAE FPU as I think there is some issues in there, when trying to stress things. Although it may just be time to start pushing to update the UAE core like I wanted to. To a point, the ROMs are universal, such that it won't matter...

Say, did anyone ever manage to get the Photoshop 1.0 code to compile? That was also released a while back, but I seem to recall people had trouble using it. Perhaps whatever changes were made to the MacPaint code are applicable there? Also, does MacPaint mostly just call the QuickDraw routines in t...

Though GFX boards have been implemented for other emulated platforms due to frequency of use (such as consoles, PlayStation, N64), I wouldn’t expect projects to go that far in this area (old Macs). There are ways of getting the hardware calls to work with native boards, but there are way too many bo...

Ram Size Lowering the Minimum Size for the program might not be a good idea, as any given program may need as much (too low and it will crash). (And 15,000 KB is quite a lot for a 68K app.) You should increase the RAM size for the emulator instead—at least 8 MB more than that minimum so the OS has ...

I’ve now finished the base (preliminary) implementation of mgraf.  Check it out. In in a number of areas, mgraf exceeds the capabilities of QuickDraw. Added to the list of features: depth and endian conversion, all QuickDraw transfer modes (cpy|or|xor|bic, not; patterns; the arithmetic modes, faster...

If it doesn't work in vMac, it's unlikely to work in BII/SS. However, you could probably use something like screen refresh rate to limit speed to some degree. The refresh rate limit for B2/SS exists to speed up emulation, not slow it down, updating the screen less so drawing takes fewer CPU cycles....

Here is, perhaps, an easier tip: If HFVExplorer is installed, and the .HFV and/or .DSK file types are recognized by Windows to use HFVExplorer (where you’d be able to open one of the files via double-click, return, apps-Open, etc.), you can simply right click in the desired directory in Explorer to ...

With B142, the last version, 6.6.3. Note that Mini vMac is able to run all versions of MacsBug, however not the mouse/menubar versions (6.6.x) due to MvM-II’s trouble with 32-bit mode; 6.5.x are the last versions that MvM currently support. Update: with build 142, the required OS to get MB running w...