Re: [Ql-Users] Copying files from QL to PC

2009-06-06 Thread aupf82
Here is what I did;  I wrote it so that hopefully even someone in my 
situation (i.e. pretty clueless on QL tech aspects) would be able to get 
results.  I am not a regular QL user; but I am very fond of my QL, and 
occasionally fire it up to remember how things were.  It was the first 
*real* computer I ever owned.

Just as a reminder,  I have a QL that I haven't used since the late eighties 
when I was a teenager.  It is a plain QL with no fancy bits and pieces that 
have come along since, like floppy drives, toolkit II's (whatever that is), 
gold cards, etc.  I also have about thirty microdrives with old files I'd 
created as well as some commercial games with considerable sentimental value 
to me.  A lot of these cartridges are on their last legs, and I wanted to 
get the files off and onto a PC where they will be safe, and I can run them 
on an emulator;  I can't say that I miss that QL keyboard! And I wanted to 
do this using just a serial cable; what followed was hours and hours of 
frustration (well, if I'm honest, I actually I quite enjoyed it, as all 
those QL memories came flooding back...).

I will not cover the usage of QemuLator as it already includes excellent 
documentation.

There are three steps.

1. Connecting the hardware
2. Getting sofware onto the QL that will allow us to copy files back to the 
PC (i.e. QemuLator) without losing header information.
3. Copying the actual files from the QL to the PC.

1.  Hardware setup

This is what I used:

- My original QL, microdrive cartridges, etc
- Windows XP laptop with QemuLator v.2.5 installed
- Serial cable to link the two together (like the one here: 
www.thesinclairshop.com/PDF/sinclairserialadaptor.pdf)

I did not have to change anything with com port settings on the PC, or 
change any of the defaults on QemuLator.  My laptop has one physical COM 
port which is the usual DB9 male connection and is seen as COM1 by XP.

I connected one end of the cable to the PC's COM port, and the other to the 
SER1 port on the QL.

Connectivity can be tested by typing at the QL

copy ser1 to scr_

the QL's flashing cursor will disappear as the command runs and waits for 
data on the SER1 port.

On the QL, type the following
open #4,ser1
print #4,Test

You should see the word Test appear in QemuLator

still on the QL, type

close #4

In QemuLator, press ctrl-space, the cursor should reappear.  A not 
complete message also appears (this message will appear later when we 
transfer files and press ctrl-space, but can be ignored as the files DO 
transfer correctly).

2.  Getting the program to use for copying over to the QL

The first thing we need to do is copy the MdvToWin program (which is 
supplied with QemuLator) from the PC to the QL and fix it so that it works. 
This program can then be used to transfer files from the QL back to 
QemuLator, correctly preserving them.

So first, we set up an mdv1_ on QemuLator which holds the MdvToWin_exe file.
On the QL, place a writeable microdrive cartridge with free space in mdv1_

To copy from the QL to QemuLator I did not have any problems with defaults 
( I believe the default rate is 9600 bps); however, I could not copy TO the 
QL if I didn't bring this down to 1200, so on both the QL and QemuLator, 
type

BAUD 1200

(there is no confirmation message from this command)

On QemuLator, type

copy mdv1_MdvToWin_exe to ser1

(the cursor stops flashing)

on the QL, type

copy ser1 to mdv1_MdvToWin_exe

the microdrive will whirr into life as the file is transferred.  You will 
know when the file transfer has completed, because a cursor will start 
flashing on QemuLator, and then the QL microdrive will stop; at this point 
hit ctrl-enter on the QL.

We now have the MdvToWin_exe on mdv1_ on the QL, but it won't run, because 
it's header has been lost (thanks Dilwyn for your explanations on this), so 
it needs to be recovered

the first thing we need to to know is the length of the mdvtowin_exe file in 
bytes.  We can get this by right-clicking on the file in Windows and 
bringing up its properties.  For the version I used, it was 1058 bytes.

Taking this number, on the QemuLator, we type

print alchp(1058)

which (for me at least) displays a result 169220

we then take these two numbers and on the QL we type

lbytes mdv1_MdvToWin_exe,169220
sexec mdv1_mdvtowin,169220,1058,10240

The mdvtowin file is the new file which WILL execute correctly, and is saved 
to mdv1_ by the above command.  I don't know what the 10240 is, but (for me 
at least), it all works.

On the QL, type

exec_w mdv1_mdvtowin

and you should get a program running with a title of MDV - Q-emulator for 
Windows 95

We can now use this executable to transfer files from the QL to the PC 
(QemuLator)


3. Now to copy a file from a QL microdrive to QemuLator.

Restart the QL and the QemuLator.  This is to set the baud rate back to 
9600, and get everything to a standard state.

As an example I have a file on mdv1_ on the QL called index_dbf, which I 
want to 

Re: [Ql-Users] Copying files from QL to PC

2009-06-06 Thread Dilwyn Jones

Thank you John. This will be a very useful document for others trying to
achieve what you did, hopefully without the trial and error and frustration
you experienced.

I agree wholeheartedly with what you say about QemuLator. My main system is
a QPC2 emulator which I use for day to day QL work, although I also have a
QemuLator on this PC for when I want to run software which won't run on
QPC2, or when I need to quickly test something on an original Sinclair ROM
version.

The Toolkit II you mentioned is a rom of extensions for the QL. It adds a
lot of useful new and revised keywords to the QL basic and improves the
network of a Sinclair QL. Once you've used a system with Toolkit 2, it's
awkward going back to a 'bare' QL system without it. It was included in many
floppy disk interface systems over the years. These days you can even
install it as a back eprom image in QemuLator. If you haven't got Toolkit II
on your system, you can get a copy for emulators from my website.

--
Dilwyn Jones

- Original Message - 
From: aup...@dsl.pipex.com

To: ql-us...@q-v-d.com
Sent: Saturday, June 06, 2009 8:39 AM
Subject: Re: [Ql-Users] Copying files from QL to PC




Here is what I did;  I wrote it so that hopefully even someone in my
situation (i.e. pretty clueless on QL tech aspects) would be able to get
results.  I am not a regular QL user; but I am very fond of my QL, and
occasionally fire it up to remember how things were.  It was the first
*real* computer I ever owned.

Just as a reminder,  I have a QL that I haven't used since the late
eighties
when I was a teenager.  It is a plain QL with no fancy bits and pieces
that
have come along since, like floppy drives, toolkit II's (whatever that
is),
gold cards, etc.  I also have about thirty microdrives with old files I'd
created as well as some commercial games with considerable sentimental
value



___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] RECOL

2009-06-06 Thread Dilwyn Jones

Dilwyn Jones wrote:

RECOL #0,0,1,2,3,4,5,6,0 turns white to blue instead of black
RECOL #0,0,1,2,3,4,5,6,2 turns white to magenta instead of red
RECOL #0,0,1,2,3,4,5,6,4 turns white to cyan instead of green
RECOL #0,0,1,2,3,4,5,6,6 turns white to white instead of yellow

and so on. Anybody got any ideas what's going on?


Congratulations, you've found a bug that has been in SMSQ/E since
probably the introduction of GD2 ;-), i.e. quite a while. The test
that checks if the machine is in mode 4 or mode 8 doesn't work, it's
basically pure chance what it chooses. Using the mode 4 recolour
code in mode 8 then results in the effects you've experienced.
Phew, I thought I'd been doing something wrong! Well, perhaps I was, in 
using MODE 8 to start with!


Actually, I was updating an old program of mine for knitting patterns, which 
loads mode 8 pictures and converts them into knitting patterns by counting 
the number of pixels of each colour and mapping those onto wool colours. The 
RECOL statement was used to show what the picture would look like in other 
wool colours.


Is this RECOL bug something which might get updated in time, or is MODE 8 
redundant as far as you are concerned?

--
Dilwyn Jones 



___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] Copying files from QL to PC

2009-06-06 Thread Go Boy Go(lt)

Hello 'pipex' John

I'm not currently seeking to emulate your process; but never say never!

Thank you for setting out everything so clearly. It is all now in my tech.
archive.

Good to read that, yet again, the old QL is spreading serendipity.  I think
I can safely say that we all join Dilwyn in praise of TKII.

Happy emulatin'

John in Wales

___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


[Ql-Users] Commercial game copy protection mechanisms

2009-06-06 Thread aupf82

Hi,

I wonder if I might impose once again and request some more help?

After recently transferring some files from microdrive to QemuLator, I am 
having problems getting a commercial game
working.

The game is called Wanderer and was produced by a company called Pyramide.

On the real QL, a quick check is run on the original cartridge when the game is 
loaded (from a copy), and if it is
not there the QL reboots.  In QemuLator, all eight mdv lights light up and it 
also reboots, when it does the check
for the real mdv.

I used the included (in QemuLator) mdvtowin_exe program to transfer the file 
from the original, and I believe this
program is supposed to remove some forms of copy protection.  I don't know 
whether this game is failing to run on
QemuLator because it just won't work on QemuLator or because the 
copy-protection is kicking in.

Is there any documentation out there that explains how this copy protection 
might work and how it might be
circumvented; or does anyone know if I can get hold of this game in some other 
way?

I was playing around with the disassembler on QemuLator, and am prepared to 
spend time working on this - do you
think removing the protection is an achievable aim (I have some programming 
knowledge, and a basic grasp of assembly
language, but very little knowledge of the QL and its hardware), or will I just 
be wasting my time?

The original mdv is failing to read correctly more and more often and I don't 
think it will last much longer;  so
any help would be much appreciated.

Thanks for any suggestions,

John

P.S. Is there a quick way that I can tell which ROM version is in my QL?
-- 


-
Visit Pipex Business: The homepage for UK Small Businesses

Go to http://www.pipex.co.uk/business-services

___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] Commercial game copy protection mechanisms

2009-06-06 Thread Tony Firshman

aup...@dsl.pipex.com wrote, On 6/06/09 14:19:



P.S. Is there a quick way that I can tell which ROM version is in my QL?
  

print ver$

Tony

--
QBBS (QL fido BBS 2:257/67) +44(0)1442-828255
  t...@firshman.co.uk http://firshman.co.uk 
Voice: +44(0)1442-828254 Fax: +44(0)1442-828255 Skype: tonyfirshman

   TF Services, 29 Longfield Road, TRING, Herts, HP23 4DG

___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] Commercial game copy protection mechanisms

2009-06-06 Thread Ralf Reköndt
Try to look for QLone from Ultrasoft or Locksmithe from ZitaSoft (Steve 
Jones).


Locksmithe is a bit better if the copy protection goes a step beyond the MDV 
magic number.


The most worst protection mechanism is in software from Talent. No chance 
without detailled knowledge in machine code.


BTW: Pyramide has released a Toolkit Nucleon, which also contains a 
mechanism (for the user, not as a protection for the software itself) to 
protect MDV (and it works...surprise..surprise...also on disks) at machine 
code level. Maybe they have also used it for their games.


Wanderer 3D is written in machine code (AFAIK), so it might be a bit 
difficult to get it freed. I remember such freed versions going round in 
the 80s. Anyway, Wanderer 3D writes directly in the screens area for speed 
reasons on the QL and maybe do some other dirty things like disabling the 
interrupts etc. So it might be better, to use it on a QL.


Ralf



Hi,

I wonder if I might impose once again and request some more help?

After recently transferring some files from microdrive to QemuLator, I am 
having problems getting a commercial game

working.

The game is called Wanderer and was produced by a company called Pyramide. 


___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] Commercial game copy protection mechanisms

2009-06-06 Thread Ralf Reköndt

;-)) Quite right.

From: Tony Firshman

Surely it is Locksmythe?

___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] Commercial game copy protection mechanisms

2009-06-06 Thread Dilwyn Jones
I seem to remember from years ago that the protection systems using the 
FORMAT random number (the cartridge fingerprint) can be re-created on a 
new microdrive cartridge with a POKE_W to the relevant system variable 
(probably the 'random number seed' ) just before a FORMAT command. As I 
haven't got technical info to hand at the moment, I can't remember the 
details, though I think it might be sv_rand (in QDOS terminology) at offset 
$2E in the system variables. No doubt if my memory is as bad as usual 
someone will correct me!

--
Dilwyn Jones

- Original Message - 
From: Ralf Reköndt ralf.rekoe...@t-online.de

To: ql-us...@q-v-d.com
Sent: Saturday, June 06, 2009 3:25 PM
Subject: Re: [Ql-Users] Commercial game copy protection mechanisms




Try to look for QLone from Ultrasoft or Locksmithe from ZitaSoft 
(Steve Jones).


Locksmithe is a bit better if the copy protection goes a step beyond the 
MDV magic number.


The most worst protection mechanism is in software from Talent. No 
chance without detailled knowledge in machine code.


BTW: Pyramide has released a Toolkit Nucleon, which also contains a 
mechanism (for the user, not as a protection for the software itself) to 
protect MDV (and it works...surprise..surprise...also on disks) at machine 
code level. Maybe they have also used it for their games.


Wanderer 3D is written in machine code (AFAIK), so it might be a bit 
difficult to get it freed. I remember such freed versions going round 
in the 80s. Anyway, Wanderer 3D writes directly in the screens area for 
speed reasons on the QL and maybe do some other dirty things like 
disabling the interrupts etc. So it might be better, to use it on a QL.


Ralf



Hi,

I wonder if I might impose once again and request some more help?

After recently transferring some files from microdrive to QemuLator, I am 
having problems getting a commercial game

working.

The game is called Wanderer and was produced by a company called 
Pyramide.


___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm




___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] Commercial game copy protection mechanisms

2009-06-06 Thread Ralf Reköndt
Yes, but there are few commercial programs, which use this later than 
1984-85 (apart from the Sinclair Software Production Kit utility, written 
by Tony Tebby).


A lot came later with own protection versions, including using marked bad 
sectors on MDV, a few with sectors filled on the Sinclair Spectrum. Or 
ask Jochen about his Card Games on Disk, which were delivered as a 
One-side-QL-Disk but formatted on side 2 on Spectrum and read special 
sectors. Clever boy, he.


Also, some used marked bad sectors, which weren't really bad but included 
special values.


One of the worst one was QL.Pawn, which used a very heavy way of 
protection, also installed an own Operating System at Start-up. As far as I 
know, this one was only freed by an italian guy. Always notable by an 
additional file called 0815. Very ironically.


Also Tankbusters was greatly protected. But MC...always searchable. Good 
QL.Monitor(s)...;-)).


Ralf

- Original Message - 
From: Dilwyn Jones


I seem to remember from years ago that the protection systems using the
FORMAT random number (the cartridge fingerprint) can be re-created on a
new microdrive cartridge with a POKE_W to the relevant system variable
(probably the 'random number seed' ) just before a FORMAT command. As I
haven't got technical info to hand at the moment, I can't remember the
details, though I think it might be sv_rand (in QDOS terminology) at offset
$2E in the system variables. No doubt if my memory is as bad as usual
someone will correct me!
--
Dilwyn Jones

- Original Message - 
From: Ralf Reköndt ralf.rekoe...@t-online.de

To: ql-us...@q-v-d.com
Sent: Saturday, June 06, 2009 3:25 PM
Subject: Re: [Ql-Users] Commercial game copy protection mechanisms




Try to look for QLone from Ultrasoft or Locksmithe from ZitaSoft 
(Steve Jones).


Locksmithe is a bit better if the copy protection goes a step beyond the 
MDV magic number.


The most worst protection mechanism is in software from Talent. No 
chance without detailled knowledge in machine code.


BTW: Pyramide has released a Toolkit Nucleon, which also contains a 
mechanism (for the user, not as a protection for the software itself) to 
protect MDV (and it works...surprise..surprise...also on disks) at machine 
code level. Maybe they have also used it for their games.


Wanderer 3D is written in machine code (AFAIK), so it might be a bit 
difficult to get it freed. I remember such freed versions going round 
in the 80s. Anyway, Wanderer 3D writes directly in the screens area for 
speed reasons on the QL and maybe do some other dirty things like 
disabling the interrupts etc. So it might be better, to use it on a QL.


Ralf



Hi,

I wonder if I might impose once again and request some more help?

After recently transferring some files from microdrive to QemuLator, I am 
having problems getting a commercial game

working.

The game is called Wanderer and was produced by a company called 
Pyramide.


___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm




___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm 


___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] Commercial game copy protection mechanisms

2009-06-06 Thread Rich Mellor
I possibly have the widest selection of programs with the 
copy-protection removed.


However, I have never seen a cracked version of QL Pawn.  The initial 
cartridge was always easy to crack - oddly however, it loaded most of 
the game/operating system from specific sectors on the second cartridge 
(if you DIR it, it appears to be blank) - however, the original 
cartridge included a useful CLONE program to make as many copies as you 
needed of that second cartridge!!


It just means that you could never get it to run from disk!

Rich

Ralf Reköndt wrote:
Yes, but there are few commercial programs, which use this later 
than 1984-85 (apart from the Sinclair Software Production Kit 
utility, written by Tony Tebby).


A lot came later with own protection versions, including using marked 
bad sectors on MDV, a few with sectors filled on the Sinclair 
Spectrum. Or ask Jochen about his Card Games on Disk, which were 
delivered as a One-side-QL-Disk but formatted on side 2 on Spectrum 
and read special sectors. Clever boy, he.


Also, some used marked bad sectors, which weren't really bad but 
included special values.


One of the worst one was QL.Pawn, which used a very heavy way of 
protection, also installed an own Operating System at Start-up. As far 
as I know, this one was only freed by an italian guy. Always notable 
by an additional file called 0815. Very ironically.


Also Tankbusters was greatly protected. But MC...always searchable. 
Good QL.Monitor(s)...;-)).


Ralf

- Original Message - From: Dilwyn Jones

I seem to remember from years ago that the protection systems using the
FORMAT random number (the cartridge fingerprint) can be re-created on a
new microdrive cartridge with a POKE_W to the relevant system variable
(probably the 'random number seed' ) just before a FORMAT command. As I
haven't got technical info to hand at the moment, I can't remember the
details, though I think it might be sv_rand (in QDOS terminology) at 
offset

$2E in the system variables. No doubt if my memory is as bad as usual
someone will correct me!



--
Rich Mellor
RWAP Services
URL:http://www.rwapsoftware.co.uk
URL:http://www.rwapservices.co.uk


___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] Commercial game copy protection mechanisms

2009-06-06 Thread Ralf Reköndt
Yes, I know. Maybe this 2nd cartridgr was either formated by Magnetic 
Scrolls own OS or by this special 68k card from GST. Who knows...?


They know, why they included esp. THAT CLONE...;-)

Ralf

- Original Message - 
From: Rich Mellor


However, I have never seen a cracked version of QL Pawn.  The initial
cartridge was always easy to crack - oddly however, it loaded most of
the game/operating system from specific sectors on the second cartridge
(if you DIR it, it appears to be blank) - however, the original
cartridge included a useful CLONE program to make as many copies as you
needed of that second cartridge!! 


___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] Copying files from QL to PC

2009-06-06 Thread Daniele Terdina

The manual explanation is pretty clear (even mentions 'directory-type 
devices'), but IMO the examples are confusing. One example advises to use 
COPY_N to copy to SER without headers, while using COPY seems to have the same 
end effect. Another example uses COPY for NET and doesn't mention headers being 
lost (not 100% sure, but I don't think NET preserves them).

 

Daniele
 
 Date: Fri, 5 Jun 2009 00:50:16 +0200
 From: ql-us...@mail.kilgus.net
 To: ql-us...@q-v-d.com
 Subject: Re: [Ql-Users] Copying files from QL to PC
 
 Daniele Terdina wrote:
  [The QL User Manual implies that COPY also copies the headers, as
  there is a COPY_N command to copy without headers, but it doesn't
  seem to work that way]
 
 Well, COPY does copy the header if it can, i.e. if the target device
 supports headers. If not, it behaves exactly like COPY_N. Headers
 never become part of the data stream.
 
 Marcel
 
 ___
 QL-Users Mailing List
 http://www.q-v-d.demon.co.uk/smsqe.htm

_
Windows Live™: Keep your life in sync. 
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_BR_life_in_synch_062009
___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] Commercial game copy protection mechanisms

2009-06-06 Thread Daniele Terdina


 The game is called Wanderer and was produced by a company called Pyramide.


Hello John,

 

I think Wanderer should work with Q-emuLator if you used the mdvtowin_exe 
utility to transfer the copy protection as you did.

 

Make sure you set the RAM to 128 KB. If it still doesn't work, please send me 
the Wanderer files you transferred to your PC and I can take a look at what may 
be wrong.

 

Thank you,

 

Daniele

 

 

_
Windows Live™ SkyDrive™: Get 25 GB of free online storage.
http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009
___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] Commercial game copy protection mechanisms

2009-06-06 Thread Daniele Terdina

 The original mdv is failing to read correctly more and more often and I don't 
 think it will last much longer; so
 any help would be much appreciated.


I have a program for MDV backup. In some cases it can also recover unreliable 
cartridges (it tries to read the data harder than COPY).

If interested, please contact me privately.

 

Daniele

_
Insert movie times and more without leaving Hotmail®. 
http://windowslive.com/Tutorial/Hotmail/QuickAdd?ocid=TXT_TAGLM_WL_HM_Tutorial_QuickAdd_062009
___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] Commercial game copy protection mechanisms

2009-06-06 Thread Ralf Reköndt

Expresso Coppee?


- Original Message - 
From: Daniele Terdina


I have a program for MDV backup. In some cases it can also recover 
unreliable cartridges (it tries to read the data harder than COPY). 


___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] Commercial game copy protection mechanisms

2009-06-06 Thread Daniele Terdina

No, it's a (probably similar) sector copy utilty that I wrote to backup my 
original Psion Chess microdrive.

 

Daniele
 
 From: ralf.rekoe...@t-online.de
 To: ql-us...@q-v-d.com
 Date: Sat, 6 Jun 2009 20:44:42 +0200
 Subject: Re: [Ql-Users] Commercial game copy protection mechanisms
 
 Expresso Coppee?
 
 
 - Original Message - 
 From: Daniele Terdina
 
 I have a program for MDV backup. In some cases it can also recover 
 unreliable cartridges (it tries to read the data harder than COPY). 
 
 ___
 QL-Users Mailing List
 http://www.q-v-d.demon.co.uk/smsqe.htm

_
Lauren found her dream laptop. Find the PC that’s right for you.
http://www.microsoft.com/windows/choosepc/?ocid=ftp_val_wl_290
___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] Commercial game copy protection mechanisms

2009-06-06 Thread Rich Mellor

Ralf,

If you have a disk copy of QL Pawn, I would be really interested - I 
have an original microdrive version, but alas it is no longer readable!


Rich

Ralf Reköndt wrote:
Hmm...just search your MDVs to 0815...;-)). As far as I remindI 
have a disk version! But do not know, if it run on others than native QL.


Ralf

- Original Message - From: Rich Mellor

However, I have never seen a cracked version of QL Pawn.  The initial
cartridge was always easy to crack - oddly however, it loaded most of
the game/operating system from specific sectors on the second cartridge
(if you DIR it, it appears to be blank) - however, the original
cartridge included a useful CLONE program to make as many copies as you
needed of that second cartridge!!

It just means that you could never get it to run from disk!

___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm





--
Rich Mellor
RWAP Services
URL:http://www.rwapsoftware.co.uk
URL:http://www.rwapservices.co.uk


___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm


Re: [Ql-Users] Commercial game copy protection mechanisms

2009-06-06 Thread Marcel Kilgus
aup...@dsl.pipex.com wrote:
 I was playing around with the disassembler on QemuLator, and am
 prepared to spend time working on this - do you think removing the
 protection is an achievable aim (I have some programming knowledge,
 and a basic grasp of assembly language, but very little knowledge of
 the QL and its hardware), or will I just be wasting my time?

It is definitely achievable if somebody has the time and motivation,
especially as I expect the QemuLator debugger to basically behave like
an ICE and not being affected by any anti-debugging tricks.

It is highly unlikely that the program includes its own MDV access
code, so the entries to the MDV vectors might be a good starting
point.

Marcel

___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm