|
|
Post by bjonte on Dec 14, 2018 9:00:54 GMT
|
|
|
|
Post by robertb on Dec 14, 2018 16:21:34 GMT
Ooo, yes, I discovered that at a recent FCUG meeting. I was about to download the C64 version and run it on the SD2IEC but found the C128 version. I thought, "Hey, the C128 version must be better."  So, that was the one that was downloaded and played during the meeting. Writing from Salem, Oregon, Robert Bernardo Fresno Commodore User Group - www.dickestel.com/fcug.htmSouthern California Commodore & Amiga Network - www.portcommodore.com/sccan |
|
|
|
Post by jmpff3d on Dec 15, 2018 6:12:41 GMT
Speedfixed ! As seen here .. csdb.dk/release/?id=172575 Yes, you heard me.. I had to C128-speedfix this one as well ! .. Speedfixes are not just an Infocom thing ! ** SPEEDFIXES: Disabled VIC-IIe chip (7% improvement) - The game is an obligatory VDC game. There is no need for VIC-IIe to maintain an active functional screen display with badlines fetching. Lowered system baud rate from 300 to 150. CP/M shows its terminal legacy strongly here. In the C128 architecture, the Z80 NMI pin is disabled. Without NMI, the system relies heavily on IRQs to handle certain assignments such as the 'serial port', 'keyboard', etc. As the baud rate setting increases, the amount of time that the Z80 has available for general tasks obviously decreases. A rule of thumb with respect to IRQ load is that the number of IRQs per second is three times the system baud rate. |
|
|
|
Post by jmpff3d on Dec 15, 2018 12:47:42 GMT
Looking over the disk image, there may be enough space to include the C64 version's intro artwork and have the C128 display it. I assume that's Mermaid's handiwork, and it looks nice. I almost went for it, thanks to a suggestion by Strobe, but then I realized I didn't want to deal with the CP/M filesystem. =)
I don't think this would be too difficult though. ASSUMING rendering the graphics are easy, it would only be a minor pain in the rear to make this happen, but simple in practice. You'd first have to import the graphics with a tool like RDCBM.COM, save it to CP/M disk, and then figure out where the thing sits inside the image at the C128 side. If the graphics are easy to render, you might be able to do it entirely from autobootblock codespace.
Display the graphics straight from diskblocks, add a little pause when rendering is complete, and then jump to CP/M loading at the end of the bootcode. This should work as long the user doesn't move, re-copy, or otherwise disturb the file on the CP/M image/disk.
|
|
|
|
Post by bjonte on Dec 16, 2018 10:40:23 GMT
Nice idea, but there may be more work since the colors aren’t the same (provided you want to display on the VDC screen).
Does the CP/M format have the same track and sector layout, just a different interpretation of the contents?
|
|
|
|
Post by jmpff3d on Dec 16, 2018 15:27:07 GMT
Nice idea, but there may be more work since the colors aren’t the same (provided you want to display on the VDC screen). Does the CP/M format have the same track and sector layout, just a different interpretation of the contents? CP/M 128 GCR formats can be laid down on straightfoward .d64 / .d71 / .d81 ... what do you think? =) ****  The above image, presumably created by Mermaid (Vanja Utne), suggests "VIC-II friendly" .. .. I think ! I invite any pro graphician to convert that into nice-looking artwork on VDC ! Mayhaps the Spectrum graphics below are "easier to VDC" .. or mayhaps not !  |
|
So, that was the one that was downloaded and played during the meeting.
