Re: trying to identify a rom...

Interesting. My identifier showed a mixture of PET BASIC 2 and BASIC 4 jsr calls and a few c64 calls.BTW, found/fixed a couple small bugs so make sure you get V1.02a release.
Steve

      From: didier derny <didier@aida.org>
 To: cbm-hackers@musoftware.de 
 Sent: Thursday, May 18, 2017 4:34 PM
 Subject: Re: trying to identify a rom...
   
 I think I finally got it  4k by plugin the rom on a SYM1 it is in sym1 paper tape format, I have to convert it 
  
  
 On 18/05/2017 22:03, Steve Gray wrote:
  
  If you send me the 2K of code I can run it through the "platform identifier" of my disassembler. It should confirm what cbm machine/ it's for. 
  Steve 
        From: didier derny <didier@aida.org>
 To: cbm-hackers@musoftware.de 
 Sent: Thursday, May 18, 2017 3:08 PM
 Subject: Re: trying to identify a rom...
  
 there are no other marking on the top
 
 on the bottom there is a number: 41203  made with some ink
 
 I know roughly what is in this eprom but I'm not sure about the machine 
 nor the rom type
 
 its a basic extension  but never seen this version 2.0 is probably the 
 version of the basic with which it was used
 
 
 On 17/05/2017 22:21, Francesco Messineo wrote:
 > On Wed, May 17, 2017 at 10:16 PM, didier derny <didier@aida.org> wrote:
 >> I'm trying to identifiy an eprom type to try to read it
 >>
 >> the rom is made by mos technology
 >>
 >> 24 pin
 >>
 >> datecode: 3680  (the 4000/8000 were not  sold at this time ?)
 >>
 >> label:  Edex 2.0
 >>
 >>
 >> my wild guess is to say it was for the commodore 3000  not found the
 >> schematics I guess it's equivalent to 2001N
 >>
 >> on the schematics  I found rom  6332  any datasheet any where ?
 >>
 >> what differences between a 2332 and a 6332  ?
 >
 > I've never heard about 6332. 2332 is the classic 4k ROM, pin
 > compatible with 2532 EPROM type (NOT 2732).
 > Is there anything else under the label? There must be a part number too.
 >
 > Regards
 > Frank IZ8DWF
 >
 >        Message was sent through the cbm-hackers mailing list
 
 
       Message was sent through the cbm-hackers mailing list
   
 
      
 
 

   

       Message was sent through the cbm-hackers mailing list