The Sinclair QL Forum

There are quite a few 7805 replacement voltage regulators in the market, Traco is one of them. In case it's a drop-in replacement for a 7805, and matches the current rating, it should generally be usable. I use one of those https://www.digikey.com/product-detail/en/OKI-78SR-5/1.5-W36H-C/811-2692-ND/...

Those are not the least bit flying. Must have been a pretty boring tour

I'm pretty sure that what happens when you add new SuperBASIC keywords, is that the new ones are always added to end of the list in the name table. If a name already exists in the table, the new one does not get slotted in in the old ones place. Correct. BP.INIT doesn't walk the name table replacin...

What's done in the QubIDE driver is the following: The QubIDE driver installs a device named BOOT (that doesn't actually provide any files, but rather returns "not found" on any action). This is just to get the next step called at the proper time in the boot process. The BOOT device driver...

Jan,

You're absolutely right, forgot that. Long time since I tried to write my last Basic extension.

Doesn't make it any easier, though. I'd still go for programming my own COPY...

Tobias

OK. Understood. I guess the culprit is here: - When this command is executed it makes available new commands. That clearly indicates the NET_START command calls BP.INIT to link in "more procedures". This call extends the S*Basic nametable with the basic commands you hand in. QLiberator is ...

Giorgio, I refer to the "linking the command into BASIC" (the BP.INIT system call). My understanding of Martin's question was "Can you have an LRESPR (or LBYTES + CALL) of a basic extension in a compiled program and expect that extensions be known to all other basics afterwards?"...

Martin, [*]The QLiberator manual "Using Basic extensions" explicitely states "it [initialising Basic extensions] doesn't work because QLiberator jobs have a non-expandable name table"[/list] With QLiberator for an extension to be recognized it must have been loaded so that it ca...

Martin, [*]The QLiberator manual "Using Basic extensions" explicitely states "it [initialising Basic extensions] doesn't work because QLiberator jobs have a non-expandable name table"[/list] With QLiberator for an extension to be recognized it must have been loaded so that it ca...

That could probably work - At least on a QL with TK2, COPY is a machine code extension. Such extension's addresses are collectable from the name table. I would assume the same in SBASIC on SMSQ/E. I am not sure what's the situation with plain QDOS. You should, in theory, be able to pull that start a...