Let's see who gets to it first

Meanwhile, the Minerva version of the QLNET driver for Q68 (ND-Q68) is almost ready for release ...
M.
I will look forward to the release of the Q68 Minerva Network driver.martyn_hill wrote: Meanwhile, the Minerva version of the QLNET driver for Q68 (ND-Q68) is almost ready for release ...
M.
I would not have expected anything elsejanbredenbeek wrote:In fact, I've already done that![]()
Obviously, you uploaded the result alreadyjanbredenbeek wrote:I just need to rebuild it.
Not as the driver stands, but it is a trivial matter to reconfigure the Timing Constants (a less-well known feature of the later TK2 Net driver) after loading/initialising the driver to reduce all the HW time-outs to effectively sup-up the bit-rate... At a guess, I reckon a 3-5 fold increase in raw bit-rate could be achieved between a pair of Q68s - assuming the single-ended, noise prone electronics/cable could accommodate it...Derek_Stewart wrote: Would there be any network increase connecting 2 Q68 via the Network connection.
...and one of the driving factors for why I opted to develop the QLUB using the simpler native Net cabling, rather than trying to network with daisy-chained serial cables!Derek_Stewart wrote: Alot simplier than making a 6 port SerNET cable.
You beat mePeter wrote:Obviously, you uploaded the result alreadyjanbredenbeek wrote:I just need to rebuild it.Works fine, thank you!
Peter
Peter wrote:The best solution for this would be to add Q68 PS/2 mouse support to the PE. Since the mouse initialization is already handled by the Q68 loader, that shouldn't be extremely difficult, but I have no idea if the PE sources are available.
Code to look at can be found in the SMSQ/E sources under: smsq_q68_driver_mouse_asm