Jump to content

F.G. Kaal

  • Content Count

  • Joined

  • Last visited

Community Reputation

375 Excellent

About F.G. Kaal

  • Rank
    Chopper Commander
  • Birthday 11/19/1961

Profile Information

  • Gender

Recent Profile Visitors

4,239 profile views
  1. I am using a new compiler ... I had to do that to make speech work. What Windows version are you using?
  2. What windows says that? As far I can tell it does work on my Samsung laptop with 64 bit Windows 10 and Asus with 32bit WIndows 10.
  3. Studing the TI disccontroller DSR is on my to-do list. I just wan't to know how it is done. Using a rechargable battery is also a good idea ... never thought about it. 🙂
  4. Because the data buffers and program stack are also in the RAM. And it is much easier to load a new DSR in RAM instead of distributing (E)PROMS. And I am also al lazy programmer ... I never tried to continiously read/write DSR dat from/to VDP RAM. This DSR (and the IDE DSR and the TIBUS DSR) does it only once and that is much easier to do.
  5. Where to store all that data !? I suppose I must (finally) use the SAMS functionality if I update Dm2k for this 🙂
  6. The description of IDE DSR V04 in IDEDSRMAN.TXT shows: V04 12/04/2006 Added: When opening directory with INPUT,FIXED 146 instead of just INPUT, FIXED [38] now possible to read file/directory creation timestamp and last change timestamp, sequence is: name, type (0-6), recordlength, size, creation timestamp second, minute, hour, month, day, year, change timestamp second, minute, hour, month, day, year. For a directory is change timestamp all zero. In order for timestamping to work the clock must be set with: CALL IDESC(hour,min,sec,dow,month,day,year) The square brackets arround [38] suggests that 38 is optional so I suppose that this functionality is since 12/04/2006 and I also suppose the functionality is the same is the HFDC (because that was my big example how things work). And the short version of reading a directory is default because then the functionality is still the same as with the good old TI diskcontroller and even when using the reading directory example in TI basic in the diskcontroller manual still functions fine when using IDEx. instead of DSKx. as device name. This being said then this: "It is also a good practice not to define the record length, because when the record length is not defined, the peripherals DSR will (and should) fill this in. On some peripherals the record length is 38 bytes but when the peripheral is capable of time stamping the record length is 146." must be a mistake in my documentation.
  7. The >84 subprogram is fully compatible with the >24 subprogram. In the time when I was busy developing the IDE DSR (2003-2005) on the real (Geneve) thing it was difficult to debug the DSR code when also using the >2X subprograms for the IDE DSR, because first my HFDC card was found by DSRLNK and next my SCSI card was found and finally my IDE card was found. That was the moment I changed the >2X subprograms to >8X subprograms to speed things up (if I remember correctly that was because the CRU address of my IDE address was >1800 that time). When the first version of the IDE DSR was finished I left it this way. I saw I allready answered this a few months ago
  8. Can you tell us which capacitor from C3 to C14 it was? Or are all capacitors around the Xilinx CPLD suspicious !? Fred
  9. A member of the dutch TIGG contacted the OLV Hospital which is close to Berry's home. Berry was also hospitalized there a few months ago (but then his mobile phone was still switched on and we could contact him). Because of the (new) privacy rules here in Europe we are not entitled to ask for any information about people laying in the hospital because we are not belonging to the family of Berry. After explanation about the why who and what and some persuation we got the answer that Berry was not there. Berry's situation and where abouts is still unknown 😞 Also haven't received any reaction from Berry's sister. Fred
  10. If you place the clock chip back on the card then you must be able to measure some voltage on the power pins of the SRAM (between 2.0 and 2.5V or so). If the IDE card is placed in the PEB and the PEB is switched on then you must be able to measure a higher voltage on the SRAM (3V or so). If it doesn't then there is no correct 5V reaching the clock chip. If the clock chip has no 5V then it keeps the SRAM in a disabled state.
  11. A missing capacitor or a capacitor to much over the VCC and GND of a TTL chip doesn't matter to much.
  12. You don't need C23 because the SRAM is powered by the battery of the clock chip. Drawings (no ASCII art) of the circuitry are available on my website. And also what Chris said ... if battery is dead then no SRAM. https://www.ti99-geek.nl/Projects/idecard/idecard.html https://www.ti99-geek.nl/Projects/idecard/Files/ide_sch1.gif https://www.ti99-geek.nl/Projects/idecard/Files/ide_sch2.gif https://www.ti99-geek.nl/Projects/idecard/Files/ide_sch3.gif
  13. THe IDETEST program and manual is in the same ZIP download as the IDE DSR!
  14. Ther LED at the back of the IDE card: 3) Switch the IDE-card back led on. This is done by continiously reading address >404E (IDE status register). If this test fails check the orientation of the LED at the back, U8, U9 and all the other gates used. Again you are allready in the total SRAM test. What is the result of the simple read write test of the IDE test program: 4) Simple read/write and read only test Writes a 16 bit pattern at address >4000 and >5000 and tries to read it back. When this fails, there is something wrong with the SRAM selection or SRAM is always read/only. Check circuitry for CRU bit 0 & 5 on IC16, and IC8, IC10, IC15, IC23 and all the gates used. Next sets CRU bit 5 so that SRAMS becomes read only and tries to write to >4000 and >5000. (I suppose that IC16 etc means U16 etc here). It can be the SRAM or any other chip in the circuitry to select it. Fred
  15. Roger, An updated version if EA5 is available here https://www.ti99-geek.nl/Modules/edas5/edas5.html#edas_5 But there was another problem; the save program returns to GPL (B @>0070) but EA5 is not a GPL program. So I also updated SAVE and SAVE2 to version 2 and these programs return with B *R11 to the calling program. Both the original Editor/Assembler module and EA5 can handle this. What were those people thinking back in 1981 savesave2save.a99save2.a99
  • Create New...