QXL Notes – Sequel

Author(s): Al Feng
Publication: ZXir QLive Alive!
Pub Details: ZXir QLive Alive! v5 n2 (Volume 5, Issue 2)
Date: Summer 1995
Pages: 13-14

Well, I finally got my working copy of SMSQ 2.47 [the QXL’s operating system (OS) which mimics the QL’s QDOS] — very satisfactory, but not perfect.

First, the excessive keyboard rollover which really made the QXL difficult to use has been corrected. The NUMLOCK can be left ‘on’ (good news if you prefer using the keypad for numeric input).

A spurious character generation still occurs when TaskMAX (DRDOS) is used to TASK SWITCH between DOS and SMSQ. Again, this is corrected by pressing the ESCape_KEY and/or ESCape + ConTRoL_E key combination. Since I know how to correct the problem on-the-fly, I can live with it. When it becomes too much of a nuisance, I may opt to upgrade to OS/2 WARP.

A minor disappointment is the fact that SBASIC barely accommodates the TURBO compiler. Relatively short and simple programs can be compiled (v3.24); but, long and complex programs return ERRORs which do not occur when compiled on a “regular” QL. I suspect that the LIBERATOR may also have a problem running under SBASIC.

Needless to say, I’ll probably be using a ‘regular’ QL in tandem with the QXL for some time to come until all the irregularities are resolved (if ever).

I keep hoping that another version of the SMSQ OS will be released which better fills a VGA screen rather than what I am getting. Now, this may simply be a matter of my not knowing how to configure the single SMSQ module for different video displays. I don’t recall seeing any documentation on this (i.e., how to use the ‘config’ program which is now included); but, that does not mean that it isn’t there … somewhere.

Since my VGA card seems to be able to interpret CGA programs so that they fill the screen as if using a high-res CGA monitor, I naively presume that it would be possible to re-write the SMSQ video so that the QL’s standard display will also fill a standard VGA monitor.

Now, hoping for Christmas-in-July, I would like to think that the firmware development that has gone into the soon-to-be-released (probably released by the time this gets into print) MIRACLE MASTERPIECE ENHANCED GRAPHICS CARD will be used on the next SMSQ release. After all, if the MASTERPIECE CARD generates a similarly scaled display on a VGA monitor as the current SMSQ video driver manages, then that would surely be a major disappointment. Having more colors in MODE 4 (80-column) is really a trivial enhancement if the display size remains diminutive.

NETworking the QXL

Since my preferred version of TURBO is 2.00, I was originally perplexed when I could not get the NETwork PORTs to function.

It turns out that there is some incompatibility between the SMSQ code and older versions of the TURBO TOOLKIT. I have found that older TURBO TOOLKITs also cause some problems with the MAKE_DIR command; but, MAKE_DIR can be made viable by re-invoking TK2_EXT.

Before the (SUPER)GOLD CARD and the QXL, the only type of NETworking that could be realistically considered was SERVER-CLIENT. This is because a QL is really crippled when FSERVE is invoked to make that particular QL a FILESERVER.

I have found that the QXL and (SUPER)GOLD CARD have sufficient clock speeds that each can be declared as FILESERVERs for the other, thus making a PEER-TO-PEER NETwork a viable reality.

Consequently, my QXL’s BOOT program includes the following statements:

NET 1
FSERVE
NFS_USE, NDK, N2_flp1, N2_flp2_, N2_ram1_, N2_ram2_, N2_ram3_, N2_ram4_, N3_ram1_, N3_mdv1_

And, the BOOT for my GOLD CARDed QL includes the following statements:

NET 2
FSERVE
NFS_USE WIN, N1_win1, N1_win2_, N1_win3_, N1_win4_, N1_win5_, N1_ram1_, N1_ram2_, N3_ram1_

You should note two things:

First, if you do not have a hard disk (interface), you can declare up to eight “win()_” devices for the client. The fact that you can have up to eight devices might not be obvious, but it was there in the original, minuscule TOOLKIT2 manual.

Second, if “win()_” is already a device (as on the QXL), then you cannot declare “NFS_USE WIN” since this would conflict with an existing system device name or QDOS keyword.

Since the QXL uses “win()_” devices, my preferred choice is to use “ndk()_” for my NETworked devices (after fdk/hdk). “NDK” is an abbreviation for N(etwork)D(is)K.

While you can use any device_label, I quickly found that it is best to use a three-letter abbreviation. If you use a three-letter designation, you can LOAD/SAVE/etc. from within PSION programs (and, most others) along the NETwork. If you choose a non-three-letter designation, the program will probably not recognize it.

DEV_USE has been found to be limited in function. Using DEV_USE to re-label your non-three-letter designation would cripple the NETwork, in part, because functions such as WCOPY will currently return an ‘in use’ error message. While DEV_USE does allow for LOAD/SAVE, using it to re-label, decreases the overall number of devices you can use.

DEV_USE

You may have read elsewhere that DEV_USE is a kluge for older programs that cannot directly access sub_DIRectories. Inevitably, you will want to reconfigure your programs to access a “dev()_” instead of “flp2_” for data files.

My QXL’s boot includes these lines:

30 DEV_USE 1,WIN2_doc_
31 DEV_USE 2,WIN2_dbf_
32 DEV_USE 3,WIN2_aba_

Prosaic — very unoriginal

As you can see, I have duplicated the suffix as the sub_DIRectory prefix.

Once you reconfigure your programs, you don’t have to remember these DEV_USE calls unless you want to access them from the command line prompt.

You can cascade DEV_USE designations; but, I currently don’t see the point of it since I have specific sub_DIRectories for specific programs.

FINALLY

Because I often make “_lis” files, I have found it more convenient to have my copy of Quill configured so that it still looks to “flp1_” for the printer_dat file. Of course, this demands that I remember (!?) to have an old start_up disk in the drive (I have forgotten on a couple of occasions, already!).

HAPPY TRAILS,
AND COMPUTING, TO YOU …

People