Synchronization Error

Synchronization Error

Post by Mark David Kakats » Wed, 02 May 1990 22:18:00



Hello. I've had a CPM 2.2 boot disk for a while, but just recently managed to
get a hold of the MOVCPM program for it. When I ran it to make a 56K version
(using "CPM 56 *"), I got a sync error. This means that the serial numbers in
the MOVCPM program and in the CPM on the disk don't match. The only way out of
this is to change the serial numbers to match. Is there any way of doing this
without having to go through the problem of disassembly, changing code,
reassembling, etc...? I have a disk editor, but I don't know where the serial
number is stored on a CPM 2.2. disk. Also, is there any way I can use something
like DDT to change the number in the MOVCPM program?

Thanks for any help!


--
+-----------------------------------------------------------------------------+

| smashed from drinking only only one stein| uwmcsd1!uwmcsd4!paravia          |
| of beer. Hence; Albert Einstein.         |                                  |

 
 
 

Synchronization Error

Post by Robert Lee Bail » Wed, 02 May 1990 03:32:00



Quote:>Hello. I've had a CPM 2.2 boot disk for a while, but just recently managed to
>get a hold of the MOVCPM program for it. When I ran it to make a 56K version
>(using "CPM 56 *"), I got a sync error. This means that the serial numbers in
>the MOVCPM program and in the CPM on the disk don't match. The only way out of
>this is to change the serial numbers to match. Is there any way of doing this
>without having to go through the problem of disassembly, changing code,
>reassembling, etc...? I have a disk editor, but I don't know where the serial
>number is stored on a CPM 2.2. disk. Also, is there any way I can use something
>like DDT to change the number in the MOVCPM program?

Its been a while, but, as best I recall, the serial number is located in
the first 6 bytes at the start of BDOS.  To patch it you will need to
know the starting address of BDOS.  There are several programs that will
find the address for you: PROBE, SYSTEM, SURVEY, or STATUS.  When you
find the BDOS entry, it should start on a boundry like xx00H.  The
actual BDOS entry point is xx06H.  I believe that the bytes between
xx00H & xx06H contain the serial number of your CP/M.  I am not sure
where the serial number is located in MOVCPM.  Maybe some other kind
soul can tell you where it is in MOVCPM.

Hope this helps.

                Bob Bailey

 
 
 

1. high performance i/o and synchronization

I'm playing around with farming out multiple requests to a disk array
under OS/2.  I'd be interested in learning of any other folks' experiences
in this area.  The 32-bit API seems to have lost some of the useful
functions from the 16-bit API (such as DosFileIO).  I'm not impressed
that it appears I have to spawn multiple threads, get each of them
to open the file (to solve the file position race condition), and
then get each of them to block doing an operation.

The code I have written keeps the I/O threads around as worker
threads.  But to synchronize I'm using OS/2's semaphores... and from
my experimentation, they are way too slow (even on a 66Mhz Pentium).
I think my code ends up spending a good percentage of its time thunking
to the 16-bit kernel and back again.  When you have to do 5 or 6 system
calls and two context switches just to read/write a section of a file,
things go way too slow.

Dean

2. Looking for very basic (and cheap) spreadsheet

3. Time Synchronization between OS/2 Clients and UNIX Server

4. What is the difference between regular process and "at" process

5. SENDMAIL Synchronization

6. Connecting to Net Drives when using VPN

7. Utilities - Directory Synchronization

8. FOR ALL ACORN NUTS. CHECK THIS OUT

9. java sound synchronization problem?

10. OS-9000 Synchronization Primitives

11. Address Book Synchronization/2

12. Palm and Psion 5 synchronization with os/2

13. Describe and Mobile File Synchronization (MFS) problems