Re: [Ql-Users] Turbo switch-bouton history

[Dave Park]

My apologies. I misunderstood.

Dave

On Fri, May 5, 2017 at 2:45 PM, Peter Graf  wrote:

> No. Alain wants to use the turbo switch, not the reset button.
>
> Am 05.05.2017 um 19:37 schrieb Dave Park:
> > As the reset button is momentary, it will also take a bistable flipflop
> > like a 7474...
> >
> > When I get back, I'll do you a little circuit. :)
> >
> > Dave
> >
> > On Fri, May 5, 2017 at 7:58 AM,  wrote:
> >
> >> On 5 May 2017 at 14:47, Alain HAOUI wrote:
> >>
>  You'd have to bend one pin of each EPROM, so they don't connect to the
> >>> socket. Then connect both bent pins by wire with turbo switch and a
> >> pullup.
> >>> (The onboard ROM selector jumpered to "Normal Operation".)
> >>>
> >>> This sounds promising. Not afraid. Pins number please. Thanks
> >>
> >> Depends on size. Why not look into EPROM datasheet yourself? Simply
> >> the highest addressline you've got.
> >>
> >> Peter
> >>
> >> ___
> >> QL-Users Mailing List
> ___
> QL-Users Mailing List
>



-- 
Dave Park
Sandy Labs
d...@sinclairql.com
___
QL-Users Mailing List

Re: [Ql-Users] Turbo switch-bouton history

[Peter Graf]

No. Alain wants to use the turbo switch, not the reset button.

Am 05.05.2017 um 19:37 schrieb Dave Park:
> As the reset button is momentary, it will also take a bistable flipflop
> like a 7474...
> 
> When I get back, I'll do you a little circuit. :)
> 
> Dave
> 
> On Fri, May 5, 2017 at 7:58 AM,  wrote:
> 
>> On 5 May 2017 at 14:47, Alain HAOUI wrote:
>>
 You'd have to bend one pin of each EPROM, so they don't connect to the
>>> socket. Then connect both bent pins by wire with turbo switch and a
>> pullup.
>>> (The onboard ROM selector jumpered to "Normal Operation".)
>>>
>>> This sounds promising. Not afraid. Pins number please. Thanks
>>
>> Depends on size. Why not look into EPROM datasheet yourself? Simply
>> the highest addressline you've got.
>>
>> Peter
>>
>> ___
>> QL-Users Mailing List
___
QL-Users Mailing List

Re: [Ql-Users] Turbo switch-bouton history

[Dave Park]

As the reset button is momentary, it will also take a bistable flipflop
like a 7474...

When I get back, I'll do you a little circuit. :)

Dave

On Fri, May 5, 2017 at 7:58 AM,  wrote:

> On 5 May 2017 at 14:47, Alain HAOUI wrote:
>
> > > You'd have to bend one pin of each EPROM, so they don't connect to the
> > socket. Then connect both bent pins by wire with turbo switch and a
> pullup.
> > (The onboard ROM selector jumpered to "Normal Operation".)
> >
> > This sounds promising. Not afraid. Pins number please. Thanks
>
> Depends on size. Why not look into EPROM datasheet yourself? Simply
> the highest addressline you've got.
>
> Peter
>
> ___
> QL-Users Mailing List
>



-- 
Dave Park
Sandy Labs
d...@sinclairql.com
___
QL-Users Mailing List

Re: [Ql-Users] Turbo switch-bouton history

[pgraf]

On 5 May 2017 at 14:47, Alain HAOUI wrote:

> > You'd have to bend one pin of each EPROM, so they don't connect to the
> socket. Then connect both bent pins by wire with turbo switch and a pullup.
> (The onboard ROM selector jumpered to "Normal Operation".)
> 
> This sounds promising. Not afraid. Pins number please. Thanks

Depends on size. Why not look into EPROM datasheet yourself? Simply 
the highest addressline you've got.

Peter

___
QL-Users Mailing List

Re: [Ql-Users] Turbo switch-bouton history

[Alain HAOUI]

Thanks Peter for your comments.

> Could it be your QubATA code? I remember that Qubide was always a bit
critical on powerup.

This happens without QubATA or any extra code or configured items.
Qubide was always a bit critical on powerup, QubATA is not ;-)

> How about the monitor? Or did you find one of the rare Flatscreens that
can display 1024x512 well?

I still have a CRT multisync monitor (probably the last one working) but I
used also a video upscaler VGA to HDMI on faltscreens.

Anyway, I don't really use the high resolution (1024x512) which is not
enough compliant with my eyes quality requirement.
However the 16 bits colours mode is excellent.

> You'd have to bend one pin of each EPROM, so they don't connect to the
socket. Then connect both bent pins by wire with turbo switch and a pullup.
(The onboard ROM selector jumpered to "Normal Operation".)

This sounds promising. Not afraid. Pins number please. Thanks

PS : Bouton = Button = Taste = Botòn = some kind of electrical equipment
when pushed or turned, switches from a stable state (Computer OFF) to an
unstable state (Computer ON) - :-)

Regards,
Alain

___
QL-Users Mailing List

___
QL-Users Mailing List

Re: [Ql-Users] Turbo switch-bouton history

[pgraf]

On 5 May 2017 at 9:41, Alain HAOUI wrote:

> I have managed to burn the latest SMSQ/E version 3.31 on a big ROM with some
> extra modules. This also worked as expected; A new "Quantum Leap".

Congratulations, you are ahead of the Q40 designer ;) I have not yet 
tried the latest SMSQ/E version from ROM.

> Then I was discussing for a while with Peter and Derek to learn how to
> split/combine all parts and construct the big ROM image with 2 OSes. Very
> interesting but we discovered later that ROM selector doesn't permit more
> than 128KBytes as continuous space addressing, so it can't be used to have 2
> bigs OSes whatever the size of used ROM; Return to reality.

That was just a primitive implementation pulling a single address 
line high or low. So it supported only a fixed size for the 
selection. At design time, 256 ROM seemed more appropriate than 1024 
KB.

> I have also noticed that different SMSQ/E versions may have different
> behaviors on starting. On my system per example, the v3.31 need to be
> restarted with the Reset button after switching On the Power to get SMSQ/E
> correctly started from ROM, while it starts normally when LRESPRed from
> disk. It looks like a timing issue related to Ready State for some devices.

I guess there was no work on the SMSQ/E lowlevel Q40 code for 
external devices since the last version from Tony Tebby. That one 
definitly boots without extra reset.

Could it be your QubATA code? I remember that Qubide was always a 
bit critical on powerup.

> Finally, I returned to the last working configuration with a 512KBytes ROM
> with a recent tuned SMSQ/E version, plus some extra modules and enough free
> space left for the next (10 ?) years needs; Great.

How about the monitor? Or did you find one of the rare Flatscreens 
that can display 1024x512 well?

> By the way, the Turbo switch button is again free on my case. Any idea ?

If not afraid of tinkering, you could use a different address line 
for the switch, allowing two larger OS in ROM. 

You'd have to bend one pin of each EPROM, so they don't connect to 
the socket. Then connect both bent pins by wire with turbo switch 
and a pullup. (The onboard ROM selector jumpered to "Normal 
Operation".)

Peter

PS: I like the word "bouton" in the subject :) sounds french... does 
it mean the same?

___
QL-Users Mailing List

[Ql-Users] Turbo switch-bouton history

[Alain HAOUI]

 

On my old good Q40 platform, I used a very early unusable SMSQ/E ROMed
version. It served only to load a more suitable SMSQ/E version from hard
disk on boot.

 

As I was recently playing with all kind of ATA/ATAPI devices, I needed to
have a working OS starting from ROM without necessary having a working
master device. Then, I decided to burn a new ROM with a good SMSQ/E version;
A real challenge for a novice tinkerer like me.

 

After having prepared all necessary burning material, I discovered that
recent SMSQ/E versions are greater than 256KBytes and can't fit in a
standard ROM on Q40 using 2x27C0124 ships; Grrr Horror.

 

With some help from "a gentleman registrar" and "community", I could have a
good enough working version within the limit of 256KB. I have managed to
burn a new ROM with SMSQ/E version 3.11 and this worked fine; Good start.

 

I was happy with this result until I needed to add a new module to the ROMed
SMSQ/E OS. I wished to add my new QubATA driver as a module and start it
automatically with SMSQ/E. As this module takes about 16KB.; Again, it can't
fit in ROM..

 

Knowing Q40 may support greater ROMs (up to 1 MBytes), I purchased some
27C2048 ships (256KBytes capacity, each) permitting to have a global ROM of
512KB. It wasn't easy to find these ships at reasonable price on the market.
Derek has also managed to find some 27C4096 ships (512KB each) in the back
of a drawer permitting to have a global ROM of 1MBytes; Plenty of ROM space.

 

I have managed to burn the latest SMSQ/E version 3.31 on a big ROM with some
extra modules. This also worked as expected; A new "Quantum Leap".

 

I was happy with this new result.until I have got another idea. While
reading the Q40 manual I noticed the ROM selector which permit to split ROM
with 2 parts for 2 different OSes.

 

I then wanted to have 2 SMSQ/E systems, one for a standard stable use and
the other for test and experimenting use. I was also proud to find some
utility for the Turbo-switch button lurking in my case for years which I can
use to select wanted OS. As I used a dual CF card readers and 2 ISA cards
I/O, I could be able to change easily between different system
configurations without the need to open the case; A dreamful.

 

Then I was discussing for a while with Peter and Derek to learn how to
split/combine all parts and construct the big ROM image with 2 OSes. Very
interesting but we discovered later that ROM selector doesn't permit more
than 128KBytes as continuous space addressing, so it can't be used to have 2
bigs OSes whatever the size of used ROM; Return to reality.

 

I have also noticed that different SMSQ/E versions may have different
behaviors on starting. On my system per example, the v3.31 need to be
restarted with the Reset button after switching On the Power to get SMSQ/E
correctly started from ROM, while it starts normally when LRESPRed from
disk. It looks like a timing issue related to Ready State for some devices.
Some versions don't load at all when launched from Classic QDOS even from
disk; Old history.

 

Finally, I returned to the last working configuration with a 512KBytes ROM
with a recent tuned SMSQ/E version, plus some extra modules and enough free
space left for the next (10 ?) years needs; Great.

 

By the way, the Turbo switch button is again free on my case. Any idea ?

 

Sorry for this long history that I hope someway useful.

 

Alain

___
QL-Users Mailing List