home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Go64!
/
Go64_1999-06_1999_CSW_Side_A.d64
/
1581cp50.zip
/
1581COPY.TXT
< prev
next >
Wrap
Text File
|
1999-05-13
|
20KB
|
395 lines
1581cp50.zip 1581-cOPY, VERSION 0.50 1999-05-13
(c) cOPYRIGHT 1998, 1999 wOLFGANG mOSER,
PUBLISHED UNDER THE gnu PUBLIC LICENSE
1. iNTRODUCTION
2. tROUBLESHOOTING
3. pARAMETER DESCRIPTION
4. sOME DETAILS ABOUT THE SECTOR LAYOUT OF mfm ENCODED cOMMODORE DISKS
5. tHE cREDITS
6. aDDITIONAL AND DISTRIBUTION INFO
7. cONTACT
1. iNTRODUCTION
tHIS IS VERSION 0.50 OF THE cbm 1581 FLOPPY DISK COPY UTIL FOR dos. iT
SHOULD BE ABLE TO IM- OR EXPORT A cbm 1581 DISK WITHIN 39 SECONDS ON A
pc BASED 3.5" FLOPPY DRIVE AND DISK CONTROLLER.
iF YOU DON'T HAVE SOME 3.5" dd DISKS ANYMORE, BUT WANT TO TEST THIS
TOOL YOU CAN DO THE FOLLOWING: gET A NORMAL 1,44 mb 3,5" hd DISK AND
CLOSE THE SECOND DETECTION WHOLE (IT'S ON THE OTHER SIDE OF THE WRITE
PROTECTION SWITCH) ON THE FLOPPY DISK BY PUTTING SOME ADHESIVE TAPE
OVER IT. tAKE NOTICE, THAT WRITING WON'T WORK WITH THIS METHOD ON
DRIVES THAT CONTAIN A dd MECHANIC ONLY (720 kb).
bUT SOME cbm 1581 DISK DRIVES AND MOST OF THE pc FLOPPY DRIVES CONTAIN
hd MECHANICS (1,44 mb), THAT ARE ABLE TO WRITE "TAPED" hd DISKS. i
DON'T KNOW, WHAT HAPPENS, IF YOU REPLACE YOUR cbm 1581 DRIVE MECHANIC
BY A pc BASED hd DRIVE MECHANIC (1,44 mb DISK DRIVE), BECAUSE i NEVER
TESTED IT, i DO OWN ONLY SOME cbm 1541 DISK DRIVES MYSELF. dON'T ASK,
HOW i WAS ABLE TO WRITE THIS UTILITY WITHOUT HAVING A cbm 1581,
OTHERWISE YOU MAY THINK, THAT i'M VERY CRAZY OR SIMPLY MINDLESS!
iNCLUDED WITHIN THIS PACKAGE IS A USER MENU CONFIGURATION FILE FOR
tHE sTAR cOMMANDER. iT SUPPLIES THE cOMMANDER WITH SOME VERY SIMPLE
METHODS FOR IMPORTING AND EXPORTING DISK IMAGES FROM AND TO DRIVE a:
(PRESS f2, WHEN BROWSING THE STANDARD FILE SYSTEM). iMPORTING DISKS
WITHOUT OVERWRITE TAKES ONLY THE FIRST PART OF THE FILENAME (WITHOUT
EXTENSION) AND GENERATES A NEW FILENAME WITH THE APPROPRIATE EXTENSION
(d81 OR d2m). bE SURE TO SELECT A FILE WITH THE CORRECT EXTENSION, IF
YOU WANT TO USE IMPORTING WITH OVERWRITE. iF YOU WANT TO IMPORT INTO
A COMPLETELY NEW GENERATED FILE, YOU HAVE TO CREATE A NEW EMPTY IMAGE
FIRST (sHIFT-f1) FOLLOWED BY RENAMING IT TO THE CORRECT EXTENSION. iT
DOESN'T MATTER, IF THE FILE HAS THE WRONG FILE SIZE, 1581-cOPY
CORRECTS THIS, IF OVERWRITE IMPORTING IS SELECTED.
tHERE'S A MODIFIED FLOPPY DISK PARAMETER TABLE FOR lINUX INCLUDED INTO
THIS PACKAGE. tHIS WAY YOU SHOULD BE ABLE TO DO IMAGE FILE TRANSFERS
UNDER lINUX, TOO. fIRST THE gap SIZES FOR THE cbm1581 PARAMETER HAVE
BEEN ADJUSTED TO A BETTER WORKING VALUE, SECONDLY A PARAMETER FOR cmd
fd2000 SUPPORT HAS BEEN ADDED. tRY IT OUT, IF YOU ARE lINUX'ED.
2. tROUBLESHOOTING
yOU MAY ENCOUNTER SOME PROBLEMS, IF YOUR FLOPPY DISC CONTROLLER IS OF
SOME UNUSUAL TYPE OR IF YOU RUN THIS TOOL UNDER MULTITASKING
ENVIRONMENTS. tHERE ARE TWO PARAMETERS NOW, SO THAT YOU CAN CONTROL,
HOW THE TRACKS OF THE FLOPPY ARE ACCESSED. pLEASE TRY OUT THE
FOLLOWING SEQUENCE, IF YOUR DRIVE DOESN'T REACH THE IM-/EXPORT SPEED
OF LESS THAN 40 SECONDS PER DISC:
1. eNABLE THE MULTIPLE SECTOR FEATURE AND SPECIFY AN INTERLEAVE OF
TWO (/p /i:2). aTTENTION, ON SOME RARE SYSTEMS, THE MULTIPLE
SECTOR FEATURE MAY CRASH THE SYSTEM (HANGUP). iF THE TRANSFER
GETS A BETTER PERFORMACE NOW, YOU MAY TRY TO CHOOSE THE DEFAULT
INTERLEAVE OF 1 (ONLY SELECTING /p).
2. iF THE MULTIPLE SECTOR FEATURE DOESN'T WORK ON YOUR SYSTEM OR
DOESN'T HELP, YOU SHOULD SPECIFY AN INTERLEAVE OF 2 ONLY (/i:2),
BUT THIS WILL SLOW DOWN THE DISK TRANSFER TIME TO 70 SECONDS.
3. tRY OUT HIGHER INTERLEAVES, BUT BE WARNED, THIS WILL DECREASE
THE TRANSFER PERFORMANCE HEAVILY. nEVERTHELESS, IT MAY BE HIGHER
THAN WITHOUT ANY PARAMETER.
4. iF YOU CAN'T OPTIMIZE THE PERFORMANCE ON YOUR SYSTEM AND WANT TO
TRANSFER ONLY A SINGLE FILE, YOU SHOULD DELETE ALL UNUSED FILES
FROM THE DISK OR THE DISK IMAGE. tHEN TRY OUT THE bam COPY SWITCH
(/b), THIS TRANSFERS ONLY TRACKS WHICH ARE ALLOCATED BY THE FILE.
3. pARAMETER DESCRIPTION
1581copy [/f[:X]][/v][/b][/m][/p][/i:N][/t:NNN] [source] destination
source
- tHIS IS THE SOURCE DISK OR IMAGE FILE. iF YOU READ A DISK, IT
MUST BE A FILENAME. iF YOU WRITE OR FORMAT AND WRITE A DISK,
THIS MUST BE A DISK DRIVE (a: OR b:). wHEN YOU WANT TO FORMAT
DISKS ONLY, THIS PARAMETER MUST NOT BE SPECIFIED.
destination
- tHIS IS THE DESTINATION DISK OR IMAGE FILE. iF YOU READ A
DISK, IT HAS TO BE THE DISK DRIVE (a: OR b:). iF YOU WRITE OR
FORMAT AND WRITE A DISK, IT MUST BE A FILENAME. wHEN YOU WANT
TO FORMAT DISKS ONLY, THIS PARAMETER SELECTS THE DISK DRIVE,
WHICH DOES THE FORMATTING.
/f[:X]
- tHIS SWITCH ENABLES FORMATTING. iF YOU ARE IN THE WRITE MODE,
THE DISK IS FORMATTED BEFORE WRITING ANY CONTENTS TO IT. iF
THE DISK IS NOT IN WRITE MODE, THIS SWITCH SELECTS FORMATTING
ONLY. yOU MUSTN'T SPECIFY THE source PARAMETER THEN. iF
FORMATTING ONLY IS SELECTED, AN EMPTY DEFAULT bam IS WRITTEN
TO THE DISK AND A SYSTEM PARTITION ON cmd fd2000 DISKS, TOO.
wITH THE ADDITIONAL PARAMETER 'X' YOU ARE ABLE TO SPECIFY THE
DESTINATION FORMAT; 2 SELECTS THE cmd fd2000 DISK FORMAT, 1
SELECTS THE cbm 1581 FORMAT. iF THIS PARAMETER IS NOT
SPECIFIED AND YOU AREN'T WRITING AN IMAGE TO THE DISK, ALWAYS
THE cbm 1581 IS SELECTED.
/f:w tHIS SWITCH LET'S 1581-cOPY USE A VERY SPECIAL FLOPPY DISK
CONTROLLER COMMAND, THAT IS AVAILABLE ON INTEL'S 82078
CONTROLLER. tHIS MAKES IT POSSIBLE TO FORMAT AND WRITE A TRACK
AT ONCE. bUT BECAUSE i COULDN'T FIND A COMPUTER OR MAINBOARD
THAT CONTAINS SUCH A CONTROLLER, THIS FEATURE COULDN'T BE
TESTED. tHEREFORE IF YOU SELECT THIS SWITCH AND 1581-cOPY
DETECTS THE CONTROLLER AS "INTEL 82078 COMPATIBLE", VERIFY IS
ENABLED TO MAKE SURE, THAT THIS COMMAND WORKS AS EXPECTED. iF
YOU THINK YOU OWN SUCH A WORKING CONTROLLER PLEASE
(please !!! :-) SEND ME A REPORT WITH THE fdc TYPE AND
VERSION, THE COMMAND LINE SWITCHES AND SOMETHING ELSE YOU DID.
/v - tHIS SWITCH ENABLES THE VERIFY MODE. iT CAN BE USED, IF YOU
WRITE AND/OR FORMAT DISKS. iT DOESN'T COMPARE THE DISK
CONTENTS WRITTEN WITH THE SOURCE BUFFER AGAIN, BUT DOES A crc
CHECK OF THE WRITTEN DATA ONLY.
/b - eNABLES _SIMPLE_ bam COPYING. oNLY TRACKS WITH ALLOCATED
BLOCKS ON IT ARE TRANSFERRED. tAKE NOTICE, THAT bam COPYING IS
CURRENTLY ONLY SUPPORTED ON cbm 1581 DISKS. i DIDN'T DO THIS
FOR cmd fd2000 DISKS, BECAUSE OF THEIR MUCH MORE COMPLEX
PARTITIONING SYSTEM. iF SOMEONE INSTALLS DIFFERENT PARTITIONS,
i WOULD HAVE TO CHECK ALL THE bamS OF ALL THESE PARTITIONS.
/m - eNABLES MASS IMPORTING OR FORMATTING WITH LEAST USER
INTERACTION. yOU CAN READ OR ONLY FORMAT MULTIPLE DISKS, IF
YOU ENABLE THIS SWITCH. aFTER A DISK HAS BEEN PROCESSED,
1581-cOPY PROCEEDS AUTOMATICALLY AFTER A DISK CHANGE HAS BEEN
DETECTED. iF READING IS SELECTED, NEW FILENAMES ARE GENERATED
AUTOMATICALLY WITH jOE fORSTER'S INDEXING ALGORITHM. mULTIPLE
DISK WRITING IS _NOT_ POSSIBLE.
/p - eNABLES THE "READ/WRITE MULTIPLE SECTORS" fdc FEATURE. oN SOME
CONTROLLERS (E.G. aDAPTEC 2842), THIS CAN HELP FIXING SPEED
PROBLEMS. pAY ATTENTION, THAT THIS SWITCH COULD CAUSE A HANGUP
OF YOUR COMPUTER SYSTEM AND MANY OTHER PROBLEMS.
/i:N
- sPECIFY AN INTERLEAVE FACTOR FOR HIGHER TRANSFER SPEED ON VERY
SLOW fdcS. iF YOUR SYSTEM IS NOT ABLE TO READ SECTORS
CONTINOUSLY FROM THE DISK, YOU SHOULD SPECIFY AN INTERLEAVE
FACTOR OF 2. tHE TRANSFER WILL NEED 70 SECONDS THEN, BUT THIS
MAY BE FASTER THAN WITHOUT SPECIFYING AN INTERLEAVE. vALUES
FROM 0 TO 9 ARE POSSIBLE, 1 IS THE DEFAULT. iF YOU SPECIFY THE
/p PARAMETER TOO, THE SELECTED INTERLEAVE IS ONLY USED, IF
VERIFY IS ENABLED OR A MULTIPLE SECTOR TRANSFER FAILS, SO THAT
THE NORMAL TRANSFER IS USED.
/t:NNN
- sPECIFIES THE NUMBER OF RETRIES TO DO, IF AN ERROR OCCURS. tHE
DEFAULT ARE 3 RETRIES ON EVERY ACCESS.
sOME PARAMETER EXAMPLES:
1581copy a: 1581img.d81 /t:999 - READ AN ERRORNOUS 1581 DISK
1581copy a: /f:2 /m - FORMAT MULTIPLE fd2000 DISKS
1581copy testdisk.d81 b: /b - bam COPY AN IMAGE TO a:
1581copy newdisk.d2m a: /f /v - FORMAT, WRITE AND VERIFY
1581copy /f a: - FORMAT A d81 IN DRIVE a:
1581copy a: newdisk /m /p - READ MULTIPLE DISK FROM a:
4. sOME DETAILS ABOUT THE SECTOR LAYOUT OF mfm ENCODED cOMMODORE DISKS
eACH SECTOR OF A mfm ENCODED DISK CONTAINS A SECTOR HEADER LIKE THE
gcr ENCODED DISKS, TOO. eACH SECTOR HEADER CONTAINS A CYLINDER NUMBER
AND A DISK SIDE DESCRIPTOR BYTE THAT NORMALLY CORRESPONDS TO THE
MECHANICALLY SELECTED TRACK AND HEAD NUMBER. tHE THIRD BYTE HOLDS THE
SECTOR NUMBER AND THE FORTH BYTE DESCIBES HOW MANY BYTES ARE STORED
WITHIN THIS SECTOR.
bUT THERE IS A LITTLE DIFFERENCE BETWEEN ibm-pc FORMATTED DISKS AND
cbm RELATED FORMATTED DISKS. oN ibm-pc DISK LAYOUTS SECTORS OF THE
LOGICAL SIDE 0 ARE STORED TO THE PHYSICAL SIDE 0 (ACCESSED BY HEAD 0),
SECTORS OF THE LOGICAL SIDE 1 ARE STORED TO THE PHYSICAL SIDE 1.
oN cbm RELATED DISK FORMATS (E.G. cbm 1581, fd2000 NATIVE) THE BOTH
SIDES ARE SWAPPED. sECTORS OF THE LOGICAL DISK SIDE 0 ARE STORED ONTO
THE PHYSICAL DISK SIDE 1 (HEAD 1), SECTORS OF THE LOGICAL SIDE 1 ARE
STORED ONTO THE PHYSICAL DISK SIDE 0 (HEAD 0). tHIS IMPLIES, THAT THE
SECTOR HEADER DISK SIDE DESCRIPTOR BYTES ARE "WRONG", TOO. a PHYSICAL
DISK SIDE 0 CONTAINS ONLY SECTOR HEADERS, WHERE ALL THE DISK SIDE
DESCRIPTORS CONTAIN THE VALUE 1.
tHE cbm 1581 DISK SECTOR LAYOUT:
nUMBER OF CYLINDERS: 80, PHYSICALLY NUMBERED FROM 0 TO 79,
LOGICALLY NUMBERED FROM 1 TO 80
nUMBER OF SIDES PER CYLINDER: 2, PHYSICALLY STORED ON SIDE 1 AND 0
(ALSO DESCRIBED AS TRACKS) LOGICALLY NUMBERED 0 AND 1
nUMBER OF SECTORS PER TRACK: 10, PHYSICALLY AND LOGICALLY NUMBERED
FROM 1 TO 10
nUMBER OF BYTES PER SECTOR: 512
tHE cmd fd 2000 DISK SECTOR LAYOUT:
nUMBER OF CYLINDERS: 81, PHYSICALLY NUMBERED FROM 0 TO 80,
LOGICALLY NUMBERED FROM 1 TO 81
nUMBER OF SIDES PER CYLINDER: 2, PHYSICALLY STORED ON SIDE 1 AND 0
(ALSO DESCRIBED AS TRACKS) LOGICALLY NUMBERED 0 AND 1
nUMBER OF SECTORS PER TRACK: 10, PHYSICALLY AND LOGICALLY NUMBERED
FROM 1 TO 10
nUMBER OF BYTES PER SECTOR: 1024
nOTE: tHE LOGICAL NUMBERING OF THE CYLINDERS MAY NOT BE CORRECT.
bUT AT LEAST _i_ WILL DO NUMBER THE CYLINDERS FROM 1 TO 81,
BECAUSE THE ANALYSIS OF AN IMAGE i GOT SHOWED ME, THAT THE
LOGICAL SECTOR CHAINING USES THE SAME NUMBERING MECHANISM.
bECAUSE i DON'T KNOW NOTHING ABOUT cmd PARTITIONS, THAT MAY
BE WRONG.
wHENEVER THE DISK SECTOR SIZE CONTAINS MORE THAN 256 BYTES, cbm DRIVES
DIVIDE SUCH BIG PHYSICAL SECTORS INTO SEVERAL LOGICAL SECTORS, THAT
ALL CONTAIN 256 BYTES. tHEREFORE THE PHYSICAL SECTOR SIZE MUST BE A
MULTIPLE OF 256.
cURRENTLY i DON'T KNOW ANY UTILITY, THAT CAN HANDLE OTHER DISK IMAGES
THAN cbm 1581 ONES (d81). wHEN i ADD DISK IMAGE TRANSFER SUPPORT FOR
OTHER cbm RELATED mfm DISK FORMATS, IT MAY BE OF NO USE FOR YOU,
BECAUSE YOU CAN'T HANDLE THE FILE CONTENTS OF THESE IMAGES. iT'S UP
TO YOU TO FIND OUT, HOW THE FILE CONTENTS OF THESE IMAGES CAN BE
HANDLED, BECAUSE i DON'T WANT AND NEVER WILL IMPLEMENT FILE BASED
SUPPORT INTO 1581-cOPY. iT MAY BE THE JOB OF pETER sCHEPERS (64 cOPY),
bERNHARD sCHWALL (tRANS64) AND jOE fORSTER/sta (tHE sTAR cOMMANDER) TO
INTEGRATE FILE ACCESS SUPPORT INTO THEIR UTILITIES. yOU CAN SUPPORT
THEM BY SENDING REPORTS OF ANY INFORMATION YOU KNOW OR FIND OUT ABOUT
UNKNOWN cbm DISK FORMATS. yOU CAN SEND ME SUCH REPORTS, TOO, i'LL
FORWARD THEM, BUT PLEASE WRITE IN ENGLISH, i DON'T WANT AND AM
ABSOLUTELY UNABLE TO BE A TRANSLATION MACHINE FOR YOU. aND YOU SHOULD
WAIT UNTIL THE DESIRED DISK FORMAT IS SUPPORTED BY 1581-cOPY, BECAUSE
IT MAY BE OF NO USE, WHEN WE KNOW HOW TO HANDLE FILES OF A DISK IMAGE,
THAT CANNOT BE TRANSFERRED TO AND FROM REAL DISKS.
5. tHE cREDITS, GREETS GO TO (AM i WRITING AN INTRO OR DEMO??? :)
tHIS LIST IS CREATED IN MORE OR LESS CRONOLOGICAL ORDER TO DESCRIBE
THE HISTORY OF 1581-cOPY.
wOMO AKA wOLFGANG mOSER <WOMO@MINDLESS.COM>
iF HE WOULDN'T HAVE BORN 1969-07-27-22:03, i WOULD NEITHER KNOW
WHAT OR WHO i AM, NOR WHY i LIKE SUCH SOPHISTICATED THINGS LIKE
PROGRAMMING CALCULATORS.
nICOLAS wELTE <WELTE@CHEMIE.UNI-KONSTANZ.DE>
a MAN LIKE ME, VERY HARDWARE INTERESTED. aFTER i JOINED tHE sTAR
cOMMANDER BETA TESTING CREW, WE HAD HUNDREDS OF EMAIL DISCUSSIONS
ABOUT ALL THESE HARDWARE BASED DESIGN QUESTIONS. oUR GREATEST WORK
WAS THE DESIGN OF THE xe1541 CABLE, i THINK. dON'T THINK, THAT
ONLY 4 DIODES CAN IMPOSSIBLY CAUSE ANY TROUBLE.
jOE fORSTER/sta AKA kOV CS bAL ZS <STA@LUDENS.ELTE.HU>
iF i WOULDN'T HAVE HAD SO MANY DISCUSSIONS WITH jOE ABOUT SO MANY
DIFFERENT c64 RELATED THINGS, THIS PROJECT WOULD HAVE NEVER BEEN
STARTED. iT WAS THE tHE sTAR cOMMANDER, THAT HAS LET ME START
THINKING ABOUT SUCH A SMART TECHNOLOGY, LIKE DIRECT cbm 1581 DISK
ACCESS.
mARKO mKEL <MSMAKELA@CC.HUT.FI>
i THINK HE IS ONE OF THE REAL GURUS OF THE cbm SCENE, THANKS FOR
SIMPLY BEEING THERE.
jENS-mICHAEL gROSS <GROSSIBR@BURAN.FB10.TU-BERLIN.DE>
hE WROTE read81, THE FIRST ibm-pc/dos TRANSFER UTILITY, THAT WAS
AND IS ABLE TO READ cbm 1581 FORMATTED DISKS. hE SHOWED ME, THAT
IT MUST BE POSSIBLE TO DO THE SAME MYSELF. tHE DIFFERENCE IS, THAT
HIS UTIL IS SHAREWARE AND HE DOESN'T DISTRIBUTE THE SOURCES OF IT.
sO THERE WAS NO POSSIBILITY TO INTEGRATE HIS ROUTINES INTO tHE
sTAR cOMMANDER. hIS UTIL IS ABLE TO DO DIRECT FILE ACCESSES ON cbm
1581 DISKS. tO PROTECT HIS WORK AND TO PREVENT ME FROM
IMPLEMENTING TOO MUCH UNINTERESTING STUFF, i DECIDED, THAT
1581-cOPY SHOULD BE A DISK IMAGE TRANSFER UTILITY ONLY WITHOUT ANY
FILE HANDLING SUPPORT.
zENITH dATA sYSTEM
tHEIR tECHNICAL rEFERENCE mANUAL TEACHED ME IN ACCESSING AND
PROGRAMMING DIFFERENT HARDWARE COMPONENTS OF THE ibm-pcS (LIKE
THE lpt PORTS, THE irq AND THE dma CONTROLLER).
dAN fANDRICH <DAN@FCH.WIMSEY.BC.CA>
hE WROTE A cbm 1581 DISK DRIVER AND FILESYSTEM ACCESS UTILITY FOR
lINUX AND SOME WONDERFUL DOCUMENTATION, THAT COULD EXPLAIN ME,
WHY IT IS SO DIFFICULT (IS IT REALLY?) TO ACCESS cbm 1581 DISKS
WITH ibm-pc BASED OPERATING SYSTEMS (THE DISK SIDE SWAP).
cHRISTOPH h. hOCHSTTTER <CHRISTOH@MICROSOFT.COM>
hIS dos UTILITY fdformat WAS MY FIRST STEP INTO LEARNING HOW TO
DO DIRECT FLOPPY DISK CONTROLLER PROGRAMMING.
cIRIACO gARC{CBM-K}A DE cELIS <CIRI@GUI.UVA.ES>
tHE "SON" OF cHRISTOF hOCHSTTTER, HE WROTE THE TOOLS 2m, 2mgui
AND 765debug. wITHOUT THE SOURCES OF 765debug, i WOULDN'T HAVE
BEEN ABLE TO IMPLEMENT THE LOW LEVEL fdc ROUTINES. iF YOU COMPARE
THE SOURCES, YOU WILL SEE, THAT i DERIVED THE WHOLE LOW LEVEL fdc
ACCESSING ROUTINES FROM THE SOURCES OF 765debug. wELL, IN THE
MEANTIME i DID SO MANY RESTRUCTURES, THAT YOU WON'T SEE ANYTHING
ANYMORE :-)
rALF bROWN <RALF+@CS.CMU.EDU>
hIS INTERRUPT LIST AT HTTP://WWW.POBOX.COM/{$7e}RALF/FILES.HTML IS THE
GREATEST RESOURCE FOR ibm-pc BASED LOW LEVEL PROGRAMMING PEOPLE,
THAT HELPED ME VERY MUCH IN IMPROVING DIFFERENT ROUTINES AND
ESPECIALLY IN LEARNING HOW TO PROGRAM THE dma CONTROLLER.
sOREX/wow AKA gEERT vERSCHUEREN <sOREX@SKYNET.BE>
oNE OF MY FIRST TESTERS. hE OWNS A VERY SOPHISTICATED TEST
PLATFORM, A 386dx RUNNING wINDOWS 95.
pONTUS bERG <bACCHUS@fAIRlIGHT.oRG>
tHE MAINTAINER OF THE BEST SORTED AND COMMENTED cbm RELATED TOOLS
PAGE. tHANKS FOR PUBLISHING 1581-cOPY ON YOUR PAGE.
aNDREAS bOOSE <BOOSE@lINUX.rz.fh-hANNOVER.de>
hE SUPPORTED ME WITH INFORMATIONS FROM THE ibm pc/at TECHNICAL
REFERENCE MANUAL AND JUST INFORMED ME, THAT HE PLANS TO INTEGRATE
DIRECT cbm DISK ACCESS SUPPORT INTO A FUTURE VERSION OF vice FOR
dos, THIS IS REALLY A GREAT IDEA, ISN'T IT.
nEAR lETTER qUANTITY AKA jOCHEN aDLER <daDLER@T-ONLINE.DE>
tHIS IS THE AUTHOR OF SEVERAL FLOPPY SPEEDER IMPROVEMENTS, LIKE
sUPRAdos, sUPERjIFFYdos AND sUPERjIFFYdos FOR THE 1541. hE
PROVIDED ME WITH SEVERAL INFORMATIONS ABOUT THE cbm 1581 AND
ESPCIALLY SOME ANALYSES ABOUT THE EXACT TRACK FORMAT. wITHOUT HIM,
i WOULDN'T HAVE BEEN ABLE TO SOLVE THE PROBLEM WITH THE DIFFERENT
(WRONG) gap SIZES OF THE EARLIER VERSIONS.
jOHANNES sCHULZE-oECHTERING <ST0159@AIXRS1.HRZ.UNI-ESSEN.DE>
mARK sEELYE <MSEELYE@YAHOO.COM>
tHESE BOTH PEOPLE WERE PUSHING ME FOR INTEGRATING cmd fd2000
SUPPORT INTO 1581-cOPY. tHE ROUGH fd2000 SUPPORT OF 1581-cOPY IS
MAINLY THEIR MERIT. mARK DID SOME SPECIAL TESTS, SO THAT i WAS
ABLE TO IDENTIFY THE LOW LEVEL DISK LAYOUT FOR THE FIRST TIME.
jOHANNES DID SEND ME SOME NATIVE cbm 1581 FORMATTED DISKS, SO
THAT i COULD TEST THE NEW ADJUSTED gap SIZES.
cREDO/scs*trc AKA rAY nEMES <CREDO@BIGFOOT.COM>
pER oLOFSSON/mAGERvALP <CL3POLOF@CLING.GU.SE>
fRANK rEICHEL <fRANK.rEICHEL@FORCHHEIM.BAYNET.DE>
tHESE PEOPLE ARE ALSO IN THE 1581-cOPY TEST CREW AND HELPED ME
DEBUGGING 1581-cOPY BY WRITING TEST REPORTS FROM TIME TO TIME.
6. aDDITIONAL AND DISTRIBUTION INFO
pLEASE READ THE HISTORY FOR FURTHER VERSION INFORMATIONS AND MUCH OF
THE IMPLEMENTATION BACKGROUND. aND YOU SHOULD CHECK THE SOURCES OF
COURSE, PERHAPS YOU WANT TO DERIVE YOUR OWN PROJECT FROM MY WORK.
iF YOU ARE AN OWNER OR MAINTAINER OF A cbm RELATED SITE PLEASE DO
PLACE THE UTIL ONTO YOUR SITE, IF YOU FIND IT USEFUL.
tHIS, OLDER OR NEWER VERSIONS OF 1581-cOPY MAY BE FOUND ON THE
FOLLOWING SITES:
- tHE PRIMARY DISTRIBUTION SITE (wOMO'S DEVELOPER PAGE)
HTTP://WWW.GM.FH-KOELN.DE/{$7e}WOMO/SOURCEN/SOURCES.HTML
- tHE sTAR cOMMANDER SITE OF jOE fORSTER/sta
HTTP://STA.C64.ORG/SCEXTPRG.HTML
- tHE "tOOLS" PAGE OF bACCHUS/flt
HTTP://WWW.FAIRLIGHT.TO/TOOLS/PC.HTML
- mARKO mKELS ftp SITE
FTP://FTP.FUNET.FI/PUB/CBM/TRANSFER/1541-TO-pc
7. cONTACT
pLEASE SEND ME BUG REPORTS, SO THAT i CAN FIX AS MOST BUGS AS
POSSIBLE. pERHAPS i SHOULD DEFINE THIS SOFTWARE AS aNTI-sHAREWARE,
WHERE i PAY _YOU_ FOR EVERY _NEW_ BUG YOU FIND AND REPORT TO ME :-)
wOMO <WOMO@MINDLESS.COM>
WWW.GM.FH-KOELN.DE/{$7e}WOMO