![]() Place that value at offset 0x17 of your file just after step 3 in the 'from scratch' instructions and then continue and you'll be golden. The fix requires knowing the proper length of whatever SCSI driver you're using in 512-byte blocks (if it's lido, it's 18, or 0x12) in hex. It's at offset 0x17 at the start of the VHD (in block 0 of the partition map) and defaults to the driver partition size (32 or 0x20) in blocks, which is wrong and will cause the Mac ROM to try to read more driver than is actually there (and subsequently lock up/crash spectacularly). The first problem is that hfdisk has no way of knowing the length of the SCSI driver you're later going to add (following the 'from scratch' directions linked above). On a related note, has anyone successfully mounted two VHDs at once (one at SCSI-6 and the other at SCSI-2)? (The whole point of the exercise is that I've painted myself into a corner with a 20MB VHD and need to grow it - that's easily done with Mini vMac, and repackaging that into a VHD *should* have been a slam dunk.but not so much.) I've even done side-by-side binary compares and I just can't see what I'm doing differently/wrong. I then broke down how yours is structured (and pulled the SCSI drivers out) from examining boot.vhd and Supplement.vhd (which interestingly use _different_ drivers, and neither matches lido - why is that?), and despite painstakingly reproducing your setup *exactly* (including the 16K of empty space at the end and the resequencing of the partition table), it *still* isn't recognized in MacPlus. I can test direct video as well, I have the are you creating your VHDs?īut anything larger than 20MB would not be recognized. I am not near my MiSTer this weekend, I can check again on Monday. As I wrote before and you can see in my photo, the correct aspect ratio is very close to 3:2 and should not fill the full screen height. The scaler should not be active, thus the scaling options for integer v/h should not have any effect. I don't think it matters though because the other cores aren't affected. Mister.7z (3.09 KiB) Downloaded 140 timesĮDIT: forgot to add that I'm using Direct Video. Perhaps making a thread about it in Amiga section would be a good idea, or I could try and ask on EAB (Amiga's biggest forum). I did kinda follow this guide when I was making my hdf, but I'm not sure I was entirely succesful, seeing as I didn't really install anything but WB on it. I don't think it matters though because the other cores aren't the file system stuff is above my pay grade. Got all the other CRT-friendly cores working.ĮDIT: forgot to add that I'm using Direct Video. Would you mind taking a look at my attached mister.ini? I'd love to get this sorted, it's my last CRT frontier. ![]() But even with the latter at 100 there are still substantial black bars on both sides. I can actually get a proper scaling using Wider HV-integer and then stretching image horizontally on my monitor. Without any tweaks the image is narrow, with OSD's Full Screen it fills the screen but scaling is flawed (can see it on text in games, otehrwise it can look deceptively good). I have applied this to a fresh mister.ini, with mixed results. As no scaler is used, video_mode should not be relevant.
0 Comments
Leave a Reply. |