Search found 628 matches
- Thu Mar 07, 2024 11:38 pm
- Forum: Compatibles Corner
- Topic: Minerva4Q68
- Replies: 22
- Views: 1904
Re: Minerva4Q68
After the upgrade from v1.00 to v1.05 I got random crashes when loading Minerva from the FAT partition, which led to the discovery of the bug in the FAT driver. It seems to be connected to the 40MHz SDHC clock option (which I had disabled in the SMSQ/E configuration). SMSQ/E versions before 3.37 ap...
- Wed Mar 06, 2024 11:55 am
- Forum: Compatibles Corner
- Topic: Minerva4Q68
- Replies: 22
- Views: 1904
Re: Minerva4Q68
I have loaded Q68 v1.02 FPGA code onto a Batch 4 Q68, and copied a Q68_ROM.SYS, with integrated Toolkit 2, to a freshly formatted SD Card with a FAT32 partition. The Q68 boots up to Minerva and links Toolkit 2, faster than my monitor startup. The system seems to work in 512x256, 1024x768, also load...
- Wed Mar 06, 2024 11:42 am
- Forum: Compatibles Corner
- Topic: Minerva4Q68
- Replies: 22
- Views: 1904
Re: Minerva4Q68
It was too late last night, but I have just mailed Wolfgang.Derek_Stewart wrote: ↑Wed Mar 06, 2024 9:42 am Have you reported this to Wolfgang to get the problem fixed?
- Tue Mar 05, 2024 11:32 pm
- Forum: Compatibles Corner
- Topic: Minerva4Q68
- Replies: 22
- Views: 1904
Re: Minerva4Q68
In addition, there is little documentation available about the internals of the built-in drivers, other than the (scarcely commented) source code. Given this fact, you do an amazing job! :D Thanks! Now a bit of bad news: I just discovered that SMSQ/E's Q68 FAT driver contains a bug that corrupts fi...
- Fri Mar 01, 2024 10:12 pm
- Forum: Help for New Users
- Topic: Serial QPC to QL
- Replies: 17
- Views: 678
Re: Serial QPC to QL
Hi Jbizzel, It's best to install the RAM disk driver and copy to ram1_ first, then to storage media. The QL cannot handle serial and storage I/O at the same time, and serial buffering is limited to just 81 bytes. The con_ driver is also quite slow. For reliable transfers you can use SERnet or QTPI t...
- Fri Mar 01, 2024 9:55 pm
- Forum: Compatibles Corner
- Topic: Minerva4Q68
- Replies: 22
- Views: 1904
Re: Minerva4Q68
I have 2 Q68 with same build and Q68 ROM Loader v1.05, both seem to load Minerva from Q68_ROM.SYS or from SMSQ/E. A bit strange. I have updated the FPGA to v1.05 and running Minerva with no problems. One question what does Minerva do different to SMSQ/E? SMSQ/E has all drivers built-in, whereas Min...
- Fri Mar 01, 2024 5:27 pm
- Forum: Compatibles Corner
- Topic: Minerva4Q68
- Replies: 22
- Views: 1904
Re: Minerva4Q68
I have received Dilwyn's Q68 which seems to boot up with no cursor. So a little more investigation required. Mark Swift has done a lot of research on this, see https://github.com/janbredenbeek/Minerva4Q68/issues/1 He was able to type a few lines on his Q68 before freezing. From the video it looks l...
- Thu Feb 22, 2024 9:08 pm
- Forum: Software & Programming
- Topic: Joystick/Sound in Supervisor mode?
- Replies: 66
- Views: 2193
Re: Joystick/Sound in Supervisor mode?
Interesting, you managed to jump to a system variable (SV.RAND) which contains a random number... And by chance it happened to have a value $Axxx which is always illegal to the 68000 (but often used by emulators).
- Thu Feb 22, 2024 7:34 pm
- Forum: Software & Programming
- Topic: Joystick/Sound in Supervisor mode?
- Replies: 66
- Views: 2193
Re: Joystick/Sound in Supervisor mode?
Thanks Tofro, so "OFFSET 0" puts the code at the start of the 4kb? It still won't assemble code after an OFFSET though (the offset section is at the end of my source file) You need to add a SECTION directive after the block defined after OFFSET 0. E.g.: OFFSET 0 label1 DS.L 1 label2 DS.L ...
- Thu Feb 22, 2024 4:07 pm
- Forum: Software & Programming
- Topic: Joystick/Sound in Supervisor mode?
- Replies: 66
- Views: 2193
Re: Joystick/Sound in Supervisor mode?
Just a short explanation on why you shouldn't be fiddling with PC_INTR ($18021) directly: If you write directly to that address (a hardware register), you're confusing the system that normally maintains a copy on what was last written there. Next, you seem to be writing $ff there, which re-arms all...