Urs,
I think you would be the first person to try an AH ROM QL. To the best of
my knowledge the earliest ROM version that it has been used with is JM. I
don't have access to an AH machine.
As per my recent note about the last minute bug that crept into the 1.03 ROM
you need:
For SER1, instead o
Jiri,
So that I can work out what the problem might be, please could you tell me
what messages are appearing when you start the connection using the ROM
driver with the bootstrap SD card inserted in the Ser-USB? I need to know
this so that I can see whether the unit is functioning correctly at the
All Ser-USB users,
Why this issue has not been reported before, or why it never came up in
testing is a complete mystery to me, but the MOUNT command in driver v1.03
is broken; it will hang if the Queue Manager is active. This is quite a
major problem if you're using standard QL serial hardware
All,
Here is some news about two new projects, still in the very early stages,
code-named Q-BUS and Ser-USB++
Whereas the Ser-USB is targetted solely at file transfers, and is limited by
the speed of the QL's truly abysmal serial ports, the Ser-USB++ would be a
full fixed disk replacement o
That's a good question, Bryan. A lot would depend upon the address space
used by the ROMDisQ for its I/O operations, and I don't have that
information to hand. Also, the one ROMDisQ that I have in my possession
stopped working about three years ago, so I'm not in a position to do any
testing.
For
fyi, here are the lines that the Q-BUS exposes on its 25 pin D-Sub
connector:
GROUND
+5V (In or Out depending upon the Power Source Select jumper)
/ENABLE : Input, active low, default=1 (interface disabled)
/WRITE : Tri-state output, active low (indicates a write to the currently
selected po
Urs,
You can already access FAT16 and FAT32 using the Ser-USB, but there is
currently no native QDOS driver for that mode. Instead, use the file
transfer capabilities of the supplied uwt (USBWiz terminal) utility.
I have been giving some thought to a QXL.WIN over FAT driver for the Ser-USB
but th
I don't know about QL2K, but both QPC and Q-emuLator run fine under Windows
7 64 bit.
I use them all the time.
Adrian
www.memorylanecomputing.com
> -Original Message-
> From: ql-users-boun...@lists.q-v-d.com [mailto:ql-users-bounces@lists.q-v-
> d.com] On Behalf Of Dilwyn Jones
> Sent:
Interesting.
You could probably use this as it stands (though I haven't checked it out)
...
http://www.coolcomponents.co.uk/catalog/product_info.php?products_id=387
Adrian
www.memorylanecomputing.com
> -Original Message-
> From: ql-users-boun...@lists.q-v-d.com [mailto:ql-users-bounc
> -Original Message-
> Dilwyn Jones
> At just under £50 it seems interesting. Connects straight to a 9-pin D so
> should only need a simple QL to 9-pin D adaptor. Works at pretty well any
> baud rate from 1200 up, so good possibilities there especially with a
> superhermes serial port. Pa
Peter,
I have made a small change to the QLROMEXT logic so that it will disable the
interface if an access to address zero (the location holding the 68xxx reset
vector) is made. This kludge means that if the QL is reset then the
interface is guaranteed to be disabled - this actually solved my Whit
; From: ql-users-boun...@lists.q-v-d.com [mailto:ql-users-bounces@lists.q-v-
> d.com] On Behalf Of Memory Lane Computing Ltd
> Sent: 22 August 2011 12:37
> To: ql-us...@q-v-d.com
> Subject: [Ql-Users] QLSD - More thoughts on latest problems
>
> Peter,
>
> I have m
Many of these problems with older XP-era apps can be traced to permissions.
Try assigning full permissions to the folder in which you install the
program and you _may_ find that all your difficulties go away.
As for the utterly absurd decision to implement a 32 bit program folder
called "Program
This has been in development for a while now as an in-house utility to use
FAT drives (SD Card, USB hard drive, flash drive) mounted on a
Ser-USB/USBWiz from QDOS. It's primary purpose was to provide a facility to
load files into a standard QL that had no other storage devices attached and
insuffic
This is expected to be released next week (with a somewhat enhanced feature
set compared to my original e-mail).
For anyone who is interested, here is the user manual for the new software:
http://www.memorylanecomputing.com/index_htm_files/serusb_fdriver.pdf
Adrian
www.memorylanecomputing.com
Jochen,
No problems here. My congratulations to all involved. A great piece of
work!
As I know from experience, you can never be certain that every disk is going
to be readable by every drive. Even if you verify each disk after burning,
some read problems are almost inevitable. And the very act
fo about the ROM Card can be found here:
http://www.memorylanecomputing.com/serusbrom.htm)
Options to purchase the latter two options via PayPal will soon be added to
the shop page.
If you have any questions about upgrading to 1.04 please get in touch.
Best regards,
Adrian Ives
Memory Lan
Apologies for another shot of blatant marketing, but if anybody wants to
stay in touch with product developments and other news at Memory Lane
Computing, we're now on Twitter:
@memorylanecmptg
http://twitter.com/#!/memorylanecmptg
I'll also be tweeting any changes to the status of our device dri
All,
Sorry to be using another system that may quickly join our other platforms
as an irrelevant footnote of computing history, but ...
Pictures of the latest Q-BUS Prototype are now at our Facebook page:
http://www.facebook.com/memory.lane.computing
The latest Q-BUS version has been modified t
I have been asked by a couple of people what the Q-BUS interface actually
is.
Actually, it was covered in previous postings to the Ql Users list, but a
lot of water has gone under the bridge since then: The QL ROM Card project
came along out of necessity (along with another project) so the Q-BUS w
Rich,
>From memory I believe an ED disk has 36 sectors per track, but it is 300
rpm. Data rate is 1Mbps.
... but I could be wrong. It's been a damn long time.
Adrian
www.memorylanecomputing.com
> -Original Message-
> From: ql-users-boun...@lists.q-v-d.com [mailto:ql-users-bounces@lis
fyi
Further to my reply to those people who asked what the Q-BUS is ...
Current information about the project can now be found here:
http://www.memorylanecomputing.com/qbus.htm
Also, some preliminary documentation is available here:
http://www.memorylanecomputing.com/index_htm_files/qbus_preli
There's a confusion between sector and cluster here.
ED disks really _are_ 36 physical sectors per track. That's in the IBM spec.
They should only format to 5760 physical sectors, but possibly Miracle
formatted tracks beyond 80 to get the extra capacity; 88 tracks would get
6336, which is close to
.@q-v-d.com
> Subject: Re: [Ql-Users] Making an image of an ED Disk Drive
>
> Op Sun, 09 Oct 2011 13:32:24 +0200 schreef Memory Lane Computing Ltd
> :
>
> In the CONQUEROR GOLD manual they say:
> "ED disks are not directly supported as no clear PC standard exits for
Ah, so that means the Gold Card was setting the controller to use 2048 byte
sectors, so my previous comments about clusters are not valid. No wonder the
disks were never compatible with the PC :)
Thanks for that information, Norman. Very helpful and that should solve
Rich's problem at a stroke.
Urs,
Thanks for posting a video of a Ser-USB in action ... but it seems to be
spending an awful lot of time sitting there not responding to a DIR command (3
minutes or so!). From what I can see on the video, it looks like the watchdog
timer finally abandoned the I/O attempt as non-responsive.
... that the ROM Ser-USB driver version 1.04 will automatically start the
Queue Manager if a configuration parameter indicating standard QL hardware
was used with the SER_USB command, thus avoiding this issue altogether.
Adrian
www.memorylanecomputing.com
===
I
For anyone who is interested in the Q-BUS project, and hasn't been following
us on Twitter, there is a significant update on our blog:
http://www.memorylanecomputing.com/blog/?p=95
Adrian
www.memorylanecomputing.com
___
QL-Users Mailing List
http:
Richard,
Thanks for this. Somebody on this list was kind enough to send me a scan of
the manual which solved my immediate problem at the time, but it's also very
useful to have this list available in text form.
I have always liked the MasterSpy and it's still the first editor that I
turn to when
Thorsten,
Thanks for the feedback. I will continue to post updates through the blog
and will tweet real-time progress when anything significant happens.
With the hardware for the new prototype finished, attention is now being
turned to a new iteration of the Ser-USB driver that will work over th
All,
The alpha version of the "USBWiz over Q-BUS" driver successfully mounted an
SD card this morning. The first time that a serial port wasn't needed to
talk to a USBWiz module!
Blog update with screen shots:
http://www.memorylanecomputing.com/blog/?p=103
Adrian
www.memorylanecomputing.com
For those who are interested, the preliminary Q-BUS information document has
been updated to include information about the new on-board EEPROM.
http://j.mp/tPuKrY
Adrian
www.memorylanecomputing.com
___
QL-Users Mailing List
http://www.q-v-d.demon.c
> -Original Message-
> From: ql-users-boun...@lists.q-v-d.com [mailto:ql-users-bounces@lists.q-v-
> d.com] On Behalf Of Derek Stewart
> Sent: 03 January 2012 20:23
> To: ql-us...@q-v-d.com
> Subject: Re: [Ql-Users] eBooks
> > I got a Kindle v4 for Christmas from the wife, I am now busy c
Happy New Year everybody.
Is there anyone out there with experience of using C68 (v4.24f) with the
compile-time switch -datamodel=small?
I have been looking at the code generated with this option (which is
supposed to generate 16 bit displacements against a base register) and all
the offsets ar
rge Gwilt
> Sent: 05 January 2012 15:24
> To: ql-us...@q-v-d.com
> Subject: Re: [Ql-Users] C68 "datamodel=small" Question
>
>
> On 3 Jan 2012, at 19:30, Memory Lane Computing Ltd wrote:
>
> >
> > Is there anyone out there with experience of using C68 (v4.24
Dilwyn, George,
Interesting, but it seems not to be a very widely available beta. Actually,
I'm surprised I missed the stuff on C68:1999 when I looked at his site
earlier.
Anyway, not to worry, I've rewritten the affected code to use absolute
addressing now. It was the easiest solution.
Thanks
All,
Does anyone know if there is any documentation listing the changes that took
place between JS and the MGx series of QDOS ROMs (besides the localised
messages and keyboard maps). I am especially interested in finding out about
MGE (Spain).
This relates to an issue arising from beta testing of
All,
I have published some news about the beta testing of the new Ser-USB 2.0
Driver on our blog. Q-BUS is also mentioned.
http://www.memorylanecomputing.com/blog/?p=115
If anyone is interested in participating in the beta test for Ser-USB 2.0
please get in touch. Please let me know which versio
fyi The information requested below is no longer required.
Thanks,
Adrian
www.memorylanecomputing.com
> -Original Message-
> From: ql-users-boun...@lists.q-v-d.com [mailto:ql-users-bounces@lists.q-v-
> d.com] On Behalf Of Memory Lane Computing Ltd
> Sent: 10 January 2012 21
All,
Is there anyone out there who would like to help with the beta testing of
the Ser-USB 2.0 drivers?
There are two drivers:
"Destiny" for QL emulators only. (Supports JM, JS, MG, Minerva, SMSQ).
"Legacy" for legacy black box QLs with standard SER ports, Hermes or
superHermes, running QL ROM
Urs,
Thanks a lot for posting this. Although I've read a lot of it before it's
very nice to have all of the articles brought together as scans, and it's
still fascinating reading.
I originally asked about MG because I wanted to know if anything had been
changed in the area of the IOSS but, in fa
Addendum: The issue below relates only to the ROM version of the driver.
> -Original Message-
> From: ql-users-boun...@lists.q-v-d.com [mailto:ql-users-bounces@lists.q-v-
> d.com] On Behalf Of Memory Lane Computing Ltd
> Sent: 17 January 2012 16:04
> To: QL Users List
>
42 matches
Mail list logo
