ÓÕÂÊ: ÇEOÒAM, ÁCCESSING ? (Ò5) ÆÒÏÍ: ÐÒÏÇÏÌ 01/24/90 Ó#: 66527 É'AM INTERESTED IN MAKING MY PROGRAMS COMPATIBLE WITH ÇEOÒAM. ÈOW IS IT ACCESSED, DETECTED ? É'VE HEARD IT USES LOCATIONS $ÄÅ00-$ÄÅÆÆ AND $ÄÆÆÅ-$ÄÆÆÆ. ÁNY IDEAS ON THE REGISTER LAYOUT ,ETC ? -::- ÓÕÂÊ: ÁREN'T YOU (Ò) ÆÒÏÍ: ÃRYCKET 01/25/90 Ó#: 121394 KIND OF OVERLOOKING WHAT GEORAM IS ALL ABOUT? ÁLL YOU HAVE TO DO IS MAKE YOUR PROGRAMS COMPATIBLE WITH A DISK DRIVE, AND THE DISK-TURBO/KERNAL AUTOMATICALLY MAKES THEM COMPATIBLE WITH ÁÎÙ ÒÅÕ. ÔHE BEST PART IS THAT IF YOU STICK WITH THE CONVENTION, EVEN ÎÏÎ-ÒÅÕ USERS CAN RUN YOUR PROGRAM. ÉF YOU WANT TO MAKE YOUR PROGRAMS USE THE ÒÅÕ'S MORE EFFICIENTLY, USE THE ÍOVEÄATA KERNAL ROUTINE WHEREVER IT APPLIES INSIDE YOUR PROGRAM. ÇOING ADDRESS-SPECIFIC INSIDE ÇÅÏÓ WILL QUICKLY MAKE YOUR PROGRAM ÇEORAM ÄÅÐÅÎÄÅÎÔ (NOT NECESSARILY COMPATIBLE) AS WELL AS SYSTEM DEPENDENT. ÏF COURSE, IF YOU'RE REFERRING TO PROGRAMMING ÇEORAM FOR USE OUTSIDE OF ÇÅÏÓ, THEN YOU NEED TO BE ADDRESS ORIENTED, BUT SUCH SOFTWARE WOULDN'T NECESSARILY RUN WITH A 17XX ÒÅÕ. -::- ÓÕÂÊ: ÙOU DON'T NEED TO (Ò) ÆÒÏÍ: ÇÅÏÒÅÐ ÊÉÍ 01/25/90 Ó#: 493358 KNOW BEANS ABOUT HOW THE ÇÅÏÒÁÍ IS ACCESSED INTERNALLY TO PROGRAM WITH IT UNDER ÇÅÏÓ. ÆIRST OF ALL, THE ËERNAL ROUTINES FOR ÒÅÕ USE, ÓTASHÒÁÍ - ÆETCHÒÁÍ - ÓWAPÒÁÍ - ÖERIFYÒÁÍ - ÄOÒÁÍÏP ALL WORK EXACTLY THE SAME WHETHER YOU ARE USING A ÇÅÏÒÁÍ OR A 1750 ÒÅÕ. ÙOU PASS THE SAME PARAMETERS TO THEM AND GET THE SAME ONES BACK. ÓECOND AND MOST IMPORTANT, FOR 99% OF PROGRAMS YOU WON'T EVEN NEED THE ABOVE ROUTINES! ÍOST OF WHAT THE ÒÅÕ IS USED FOR IS FOR EMULATING DISK DRIVES, EITHER SHADOWED OR ÒÁÍ DISKS. ÔHIS IS ALL HANDLED INTERNALLY IN THE DEVICE DRIVERS. ÔO THE PROGRAMMER, YOU TREAT IT JUST LIKE A REGULAR DISK DRIVE, JUST LIKE A TRUE PHYSICAL DRIVE OR A 17XX BASED ÒÅÕ SYSTEM. ÉT'S ALL THE SAME. ÔHE ÏÎÌÙ TIME YOU WILL EVER NEED TO KNOW ABOUT THE DIFFERENCE BETWEEN ÇÅÏÒÁÍ AND 17XX ÒÅÕ'S IS IF YOU ARE TRYING TO USE IT OUTSIDE OF ÇÅÏÓ. (ÏR YOU'RE WRITING DIRECTLY TO THE ÒÅÕ REGISTERS FROM ÇÅÏÓ, WHICH IS A NO-NO IN THE FIRST PLACE.) ÊUST KEEP DOING WHATEVER YOU'RE DOING NOW. ÔHE BEAUTY OF ÇÅÏÓ IS THAT TO THE PROGRAMMER, IT ALL WORKS THE SAME, REGARDLESS OF WHAT THE HARDWARE IS LIKE. -ÊIM :) -::- ÓÕÂÊ: ÏPPS... (Ò) ÆÒÏÍ: ÐÒÏÇÏÌ 01/25/90 Ó#: 514824 É ÍEANT TO SAY ÎÏÎ-ÇÅÏÓ ÐROGRAMS. ÓUCH AS DISK UTILITIES, AND THE SUCH. ÓOME ALREADY SUPPORT 17XX ÒÅÕÓ, É FIGURED THAT É MIGHT TRY TO ADD ÇEOÒAM ÃAPABILITY AS WELL. ×HAT É MEANT, HOW IS ÇEOÒAM ACCESSED THROUGH NORMAL, ÎÏÎ-ÇÅÏÓ Ï/Ó ? -::- ÓÕÂÊ: É DON'T IMAGINE (Ò) ÆÒÏÍ: ÃRYCKET 01/25/90 Ó#: 820224 ÂÓ× IS GOING TO REVEAL ANYTHING ABOUT THIS. ÉT SEEMS TO ME THEY WANT THEIR PRODUCT EXCLUSIVELY COMPATIBLE WITH THEIR SYSTEM. ÉN THE EVENT THAT YOU ARE UNABLE TO TURN UP ANYTHING É RECOMMEND DISASSEMBLING THE ROUTINES MENTIONED BY GEOREP ÊIM IN THE PREVIOUS MESSAGE. ÔHAT OUGHT TO HOLD THE ANSWER. -::- ÓÕÂÊ: ×ELL, ÆÒÏÍ: ÇÅÏÒÅÐ ÊÉÍ 01/26/90 Ó#: 410467 É DON'T THINK ÂÓ× CARES IF PEOPLE USE THE ÇÅÏÒÁÍ OUTSIDE OF ÇÅÏÓ - IF ANYTHING, IT WILL INCREASE DEMAND FOR IT! ÔHE ÇÅÏÒÁÍ USES TWO SEPARATE AREAS OF MEMORY - $ÄÅ00-$ÄÅÆÆ AND $ÄÆÆÅ-$ÄÆÆÆ. ÔHE 256 BYTE AREA AT $ÄÅ00 IS A "WINDOW" INTO THE ÇÅÏÒÁÍ. ×HEN THE ÇÅÏÒÁÍ IS INSTALLED, ÒÁÍ APPEARS AT $ÄÅ00. ÔHE 2 BYTES AT $ÄÆÆÅ-$ÄÆÆÆ ARE USED TO SELECT WHICH 256 BYTE BLOCK OF ÒÁÍ WILL APPEAR IN THE $ÄÅ00 SPOT. É'M STILL NOT SURE HOW THESE 2 BYTES ARE ORGANIZED, SINCE IT DOESN'T SEEM TO BE A ÂANK/ÐAGE CONFIGURATION LIKE THE 17XX IS. ÔHE BEAUTY OF THIS ARRANGEMENT IS THAT THE WINDOW IS 256 BYTES, AND A DISK SECTOR IS ALSO 256 BYTES. ÓO, IF YOU TREAT IT LIKE A DISK DRIVE, ALL YOU HAVE TO DO IS PLUG THE APPROPRIATE VALUES INTO $ÄÆÆÅ-$ÄÆÆÆ, AND YOUR 'SECTOR' WILL APPEAR AT $ÄÅ00! ÙOU COULD MAKE A REALLY FAST DISK COPIER USING THIS, SINCE IT IS FASTER THAN THE ÄÍÁ - THERE'S NO MEMORY TRANSFER IN THE FIRST PLACE! ÊUST LOAD THE DATA RIGHT DIRECTLY INTO $ÄÅ00, THEN MOVE THE WINDOW TO GET THE NEXT SECTOR UP. ÉF É FIND OUT ANY MORE INFORMATION ON HOW THE BYTES AT $ÄÆÆÅ-$ÄÆÆÆ ARE SET UP, É'LL LET YOU KNOW. É'M DYING TO FIND OUT MYSELF! -ÊIM :)