The PSION Organiser II Homepage
Forum Home Forum Home Help Help Search Search Members Members Login Login Register Register

Welcome, Guest. Please Login or Register.
Why register?
   The Psion Organiser II Forum
   User Forum
   User Post
   Post reply ( Re: Psi2Backup )
Post reply
Subject:
Full name:
Email:
Message icon:
Add Smileys:
Message:
Disable Smilies:

Check this if you'll be adding code (or don't like smileys).


Before submitting, please enter the verification code in the box below.
   


Topic Summary - Displaying all posts. Click here to show the reduced amount
Posted by: hiddenevil Posted on: Nov 16th, 2018, 6:39pm
32bit - check
Windows xp - check
Original serial comm link nope :-P
 
Thanks for reply, I might have to pm you about using MAKE.
Posted by: jaap Posted on: Nov 16th, 2018, 4:15pm
It is probably not to do with the USB comms link as such. There are two possible problems:
 
1. This program is just a wrapper around the original DOS programs from Psion. Those DOS programs do not run on 64bit machines, so this program won't work on 64bit machines either, regardless of what kind of comms link you are using. The only way I can get those old programs to run is via DOSBox.
 
2.  If you can still run those DOS programs (e.g. are using a 32bit OS), then it still only works of the comms link is on com port 1 or 2. This is because in the mid 1980s PCs usually only had those two ports, and Psion's programs were written then. It is not likely that the usb comms link happens to get assigned to port 1 or 2 automatically, so you will have to arrange for this to happen. I think there is software out there that allows you to reassign com ports, but I don't have experience with that.
 
As I mentioned above, I run MAKE/UNMAKE inside DOSBox, and have its settings so that it maps the laptop's comms link usb port to the COM1: port inside DOSBox.
Posted by: hiddenevil Posted on: Nov 16th, 2018, 2:13pm
Doesn't seem to support the usb comm link
Posted by: Perekk Posted on: May 7th, 2010, 1:15pm
on May 4th, 2010, 9:45pm, Boris wrote:

MAKE & UNMAKE support only COM1 and COM2, and there is absolutely nothing that I can do about. Well, unless someone would disassemble unmake.bin AND explain it to me...

 
Ah ok, I was not aware of this limitation in make and unmake.
 
on May 4th, 2010, 9:45pm, Boris wrote:

However, there is a way: I actually know how to dump pack data, even corrupted one, to PC. This method uses the FILE service which is provided by Psi2Win for most, if not all COM-ports. It is not at all a method suited for the average GUI-dependent user, so it has not been published so far.

 
It sounds interesting! If it don't take you much time, would you publish it ?
 
on May 4th, 2010, 9:45pm, Boris wrote:

psi2web: I have been thinking about this, but how do you plan to access a serial port from a web app? Even doomish ActiveX will refuse, since killbits have been set on MSCOMMS32.OCX

 
I was thinking about a psi2twit function to post something on twitter, or a function to sincronyze org 2 diary with google calendar, or a function to get "slices" of html from certain page.
 
It wouldn't be too difficult to make such library, the biggest problem would be to code the serial line protocol.
 
 
on May 4th, 2010, 9:45pm, Boris wrote:

Source code: I provide everyone with all code s|he desires, but I can't guarantee satisfaction. I have been very negligent in commenting, and I must confess that even me myself sometimes has troubles understanding the code that I have been writing years ago.

 
Don't worry about it, you made a little great app that -works- and the most important thing is that you coded the protocol. I'm sure that your code is not worse than all the code I have to debug everyday.  
Posted by: Boris Posted on: May 4th, 2010, 9:45pm
No workaround, sorry. In fact, Psi2Backup is a workaround itself, it is just a shell to provide the 1986 Psion programs with an environment to fullfill their job in a 2010 world and also serves to translate the wishes of GUI dependent users of 2010 to these programs.  
MAKE & UNMAKE support only COM1 and COM2, and there is absolutely nothing that I can do about. Well, unless someone would disassemble unmake.bin AND explain it to me...
 
However, there is a way: I actually know how to dump pack data, even corrupted one, to PC. This method uses the FILE service which is provided by Psi2Win for most, if not all COM-ports. It is not at all a method suited for the average GUI-dependent user, so it has not been published so far.
 


psi2web: I have been thinking about this, but how do you plan to access a serial port from a web app? Even doomish ActiveX will refuse, since killbits have been set on MSCOMMS32.OCX
 
Source code: I provide everyone with all code s|he desires, but I can't guarantee satisfaction. I have been very negligent in commenting, and I must confess that even me myself sometimes has troubles understanding the code that I have been writing years ago.
Posted by: Perekk Posted on: May 4th, 2010, 3:42pm
Hi all,  
in the setup tab of psi2backup I can choose only com1 or com2.  
My organizer is connected to com3, because com1 and com2 are not working, is there a workaround ?  
 
BTW are the source of psi2backup (and psi2win) available?  
I would like to contribuite to the code and I have some nice ideas for a "psi2web" application.
Posted by: Boris Posted on: Dec 17th, 2008, 11:08pm
Unfortunately I have forgotten to include some files in the previous release packages (v1.00).  
This update contains the same program, but this time with all extra files. I must admit I have been negligent, sorry for any inconveniences
 
Please use the links in the initial message of this thread to download V1.01.  
 
BTW. If you have used any of the previous installer versions, you don't need to use it again, simply download the zip-file and extract it to the Psi2Backup folder in your 'programs' folder. If you want to use the installer again, you must uninstall the previous version prior to using the new msi file!
Posted by: Boris Posted on: Dec 7th, 2008, 5:01pm
I have just released V1.00 of Psi2Backup. I hope this will finally resolve all 'component missing' problems (for vista, please use the installer version).
 
Please update!
Posted by: Boris Posted on: Oct 21st, 2008, 8:05pm
Please use the installer version.  
 
If it still doesn't work, install Psi2Win.
 
To my best knowledge, this will resolve all dependencies.
Posted by: roger_webb Posted on: Oct 21st, 2008, 7:51pm

- Has Psi2Win already been installed when the error occurred?
 

No that is currently installed on another machine.
Roger
Posted by: Boris Posted on: Oct 21st, 2008, 7:44pm
Hmm.
 
I will have to look into that....
 
Two things I need to know:  
- Has Psi2Win already been installed when the error occurred?
- Did you use the msi (reply#6) or the zip (reply#5)?
Posted by: roger_webb Posted on: Oct 20th, 2008, 5:08pm
I tried to use Psi2Backup V0.0.1 Under Vista
I get "Component @TABCTL32.OCX' or one of its dependencies not correctly regisered: a file is missing or invalid.   Any ideas?
 
Roger
Posted by: logicaid Posted on: Aug 15th, 2005, 7:23am
on Oct 27th, 2004, 6:06pm, Boris wrote:
Hi Mark!
 
I would like to make (UN)MAKE work with Psi2Win .....
snip.....
 
BTW: do you have a disassembler for HD6303 code?

 
Did you find/get a diss-asm? DASMx should be good but I haven't tried it.
Posted by: Boris Posted on: Jul 19th, 2005, 1:04pm
on Jul 19th, 2005, 12:46pm, unclevernon wrote:

 I opend up the pack and saw a standard EPROM inside. The only option left then I guess is to solder the EPROM from the PCB and read the data (if any) directly from the chip with an EPROM programmer. Or does anybody else have an idea how to get access?

I don't see the point. You can read any plain text data (if any) by using FIND on the Org2. The rest is probably programs, which you cant use on the Org2 anyway, because they are 100% incompatible.  
 
If you need to copy the pack (for what reason ever), yes, you'll have to do it the hard way by cloning the eprom.
Posted by: unclevernon Posted on: Jul 19th, 2005, 12:46pm
on Jul 19th, 2005, 12:26pm, Boris wrote:
Organiser 1 (one) packs are organised completely different from Organiser II (two) packs.
I opend up the pack and saw a standard EPROM inside. The only option left then I guess is to solder the EPROM from the PCB and read the data (if any) directly from the chip with an EPROM programmer. Or does anybody else have an idea how to get access?
Posted by: Boris Posted on: Jul 19th, 2005, 12:26pm
Organiser 1 (one) packs are organised completely different than Organiser II (two) packs.
The Organiser II sees them as write protected foreign media. Therefore they cannot be backed up as whole, sorry!
 
But there is limited backward compatibility: Org2 can read (not write) all plain text data as a single file.
 
So data (not the programs!) can be copied to the Organiser II using the COPY utility according to the technical manual.
Since I don't have a Psion1 pack, I can't test this, but most likely the following procedure will copy all data from the pack to a file on A:.
 
  • insert the Org1 pack in the upper slot B
  • select COPY ( LZ: Xfiles>Copy )
  • type B:MAIN ( LZ: select B, type (!) MAIN )
  • press <EXE>
  • type A:ORG1DATA ( LZ: select A, type...)
  • press <EXE>
     
    The resulting file ORG1DATA can be transferred to PC easily by COMMS>TRANSMIT>FILE
     
    BTW: Using FIND should also reveal the data.
     
     

    to unclevernon:
     
    Thanks for the disassembly, guess I'm not much more clever than before, probably should have written "unless someone disassembles and explains...." (8-)
  • Posted by: unclevernon Posted on: Jul 19th, 2005, 9:00am
    Hi to all,
    I am trying to make backups of two packs, found in an old Psion II 'Mark 1' model (as I guess from the description in the model oracle).  One pack is a 16K datapack, with an EPROM glass window in the back, the other is a 'FINANCE' pack. The packs might contain data, but I am not sure. I tried a Psion II XP to make the backup. When I make the backup, for both packs the PSION reports :
     
    FatalErrNo: 240
    UNKNOWN PACK
     
    What could be the cause of this? Would packs from a Mark1 not be readable with an XP model? Any hints will be greatly appreciated.
     
    Best regards,
     
    UV
    Posted by: unclevernon Posted on: Jul 19th, 2005, 7:28am
    on Oct 21st, 2004, 12:18am, Boris wrote:
    Unless someone disassembles (un)make.bin

     
    Here is the result of an attempt to disassemble make.bin. I am not familiar with 6303 assembly so I just went ahead and assumed that everything that is not an ASCII string is code.  Hope this is of help. If it makes sense, I will also try to do the unmake if someone is interested.
    Best regards,
    UV
    Posted by: Boris Posted on: Jan 26th, 2005, 9:47pm
    The current version contains the original MAKE & UNMAKE V3.20. These were released in 1992.  
    This is the latest version known, and probably the only one that fully supports flashpacks.
     
    There are no newer versions. However I have noticed that V3.00 has a 1997 filedate, but this must be incorrect, since the development ceased in 1992.
     
    Well, I have forgot an important point:
    UNMAKE v3.20 will *not* transfer copy protected packs. Other packs should work fine.  
     
    If you are in need of v3.00 (ignores protection): download the latest version of Psi2Backup (initial post) and unzip only UNMAKE.* (3 files) to the Psi2Backup program folder. It allows to switch between v3.00 (patched to ignore  copy protection) and 3.20 (full support for flashpacks).
    Posted by: martinstahl Posted on: Jan 26th, 2005, 3:25pm
    Hello Boris,
     
    I am not shure, but it seems, that the unmake.exe (1.6.1992 with 41kb) is now an earlier version than in your PsiBackup 0.90 (it is from 28.11.1997 with 37kb).
     
    With the older version of unmake.exe it is not possible to make a backup.
     
    When I copy the unmake.exe from 1997 into the PsiBackup directory, then the backup function seems to work.
     
    But when I try to restore the file to a new flash datapak there appears an error message: "xyz.opk is not a valid OPK file".
     
    Is there also a newer version of make.exe?
     
    Thanks a lot!
     
    Martin
    Posted by: Boris Posted on: Oct 27th, 2004, 6:06pm
    Hi Mark!
     
    I would like to make (UN)MAKE work with Psi2Win (the 32bit CL.EXE replacement).  
    The idea is that the original (un)make.bin is booted on the organiser and Psi2Win does supply the same responses as (un)make would do.
    Therefore I would need to know the codes that are used in the communication of make.bin with make.exe.
    I have been spying on the data being sent in a make session, but havn't been able to figure everything out.  
    Probably unmake is easier for the start....
     
    BTW: do you have a disassembler for HD6303 code?
    Posted by: Mark Rivers-Moore Posted on: Oct 26th, 2004, 12:05pm
    I'm a friend of Tom's and I disassembled unmake.bin in 1990 to bypass the protection for the product Tom is still copying today. I should perhaps point out that I wrote the code for the datapack in question!
     
    How much would you like unmake.bin demystified? Since Tom emailed me to mention this thread, I've disassembled most of it again (only 909 bytes). I have enough info so far to hack it to read different packs, but a bit more work would enable me to provide an assembler files to compile.
     
    I have the full technical manuals for the Psion Organiser II, plus the addendums for the LZ/LZ64, COMMS LINK and RS232 port control.
     
    Cheers
    Mark
    Posted by: Boris Posted on: Oct 21st, 2004, 12:18am
     
    It would be nice to be able to put the master into drive B: and the other one into drive C:

    If only it was possible
     
    In other words: the (UN)MAKE progs launched by Psi2Backup were made in 1987 (!)
     
    Unless someone disassembles (un)make.bin, you will have to follow the instructions (un)make.exe issues.
     
     
    BTW: I donate an LZ64+CL to anyone who demystifies both Psions make.bin and unmake.bin. These are the files that are executed on the organiser during the backup/restore.
    Posted by: Tom Scharf Posted on: Oct 20th, 2004, 11:23pm

    I tried Boris's Psi2Backup utility and it works brilliantly! I also installed Psi2Win which may have supplied some missing Vbasic files or whatever.
    Anyway, it does what it says on the tin! It successfully copied the copy protected master 32K datapak onto my hard-disk, and then copied it back onto a 64K datapak. There was a warning that I was copying a 32K datapak into a 64K one but I ignored that, and rightly so. The new datapak works perfectly.
    When the DOS boxes come up, read and follow the instructions in them carefully with regard to when to plug the paks in. You don't want the org2 to size the blank pak before you program it.
    My only trivial comment is that both datapaks need to be plugged into drive C: (the bottom one). It would be nice to be able to put the master into drive B: and the other one into drive C:
     
    Cheers: Tom
    Posted by: Boris Posted on: Oct 20th, 2004, 9:42pm
    Psi2Backup
     
    an easy way to backup and shift valuable packs
     
  • backup any pack
  • restore or append to any pack
  • supports all pack types
  • optionally compresses data (removes deleted records/files)
     


    Psi2Backup allows to backup complete packs to the PC. It supports all pack types (Program, Data, Flash, RAM), even if these are marked as copy protected.
     
    The resulting pack image files (*.OPK) can be restored to another pack, even if the pack size and/or type is different. The contents can even be appended to an existing pack.
     
    Psi2Backup optionally removes deleted data from the pack image, either when backing up or while restoring. This feature allows to compress packs easily.
     


    Download the latest version (2008-12-17)
     
    - Psi2Backup_v1_01.zip (48 kb)
    or
    - Psi2Backup_v1_01.msi (1.49 MB)
     
    The second download is a complete installer package, use it if you're on Vista or addicted to start menu entries, and also if you get something like 'component missing' (or similar) when starting up Psi2Backup.
     
    If you have installed any of the previous versions, do not use the installer again, simply download the zip-file and extract it to the Psi2Backup folder in your 'programs' folder.  
     
    Otherwise, since the installer is a free, and therefore rather limited Micro$oft product, you must uninstall the previous version prior to using the new msi file!  
    (- subject to change -)
     

    The posts below are in historical order. All mentioned bugs have been fixed.

  • The Psion Organiser II Forum » Powered by YaBB 1 Gold - SP 1.1!
    YaBB 2000-2002,
    Xnull. All Rights Reserved.
    top