Jump to content

aftyde

Members
  • Content Count

    339
  • Joined

  • Last visited

Posts posted by aftyde


  1. 4 minutes ago, arcadeshopper said:

    Actually, did not upgrade.  I re-imaged the SD card using the 2.3 download and then expanded the root fs...

     

    Did you upgrade from stretch or buster?

    Sent from my LM-V600 using Tapatalk
     

     


  2. Just did the upgrade.  Oddly, eth0 no longer works.  Managed to get connected via wifi, ssh'd in - eth0 shows with the correct mac address.  However dhclient eth0 returns after some time with no address.  If I manually set the IP using ifconfig and appropriate netmask and router settings - it can't ping anything and instantly knocks down the wifi connection.

     

    Would like eth0 to work again...  ;)   Interestingly, if I turn predictable names on, reboot, then off, reboot - the eth0 interface will come up... but it's a headache to do that on every boot.

     

    Thoughts?  Thank you, Arthur...


  3. That is a cute monitor...  I've had my finger hovering over the bid button on that Triple Tech card.  Which I absolutely do not need.  Right now;

     

    In the console

    • F18
    • MiniMem

    In the PEB

    • Firehose
    • 32K Memory
    • P-Gram+
    • WHT SCSI card w Syquest 200MB cart drive in external box WDS1.
    • SID Player card
    • RS-232 card w HDX mod installed - modem, HDX1.
    • TIPI card with Raspberrry PI mounted.
    • Myarc DDCC w 80 track mod - DSDD/2880 sectors.  DSK1 and 2 are Lotharek SD card floppy emulators, DSK3. (DSSD) shares the external box with the 1/2 height Syquest.

     

    Full house ... and I use it every day...  Thanks to @jedimatt42 I now have more or less unlimited high speed database storage.

     

    As a kid, if I had such a system - there would be a LOT more TI software in the world today.

     

    Cheers, Arthur...

    • Like 6

  4. Worthy of note - some programs use this memory.  I run a very large TI-BASE (Incebot) database, and if you happen to have a Mini Mem - the DB, which normally starts with 1569K of working space for tables and such will start with 4096K of working memory.  This allows for more open databases and larger program files as the software has a DB language which allows for all forms of entertaining data manipulation, string manipulation, compute operations and so forth.  So this is a cart I keep in the TI at all times.  Without it, there is no way to edit my DB procedures.  Have had this machine going for 35 years.

    • Like 3

  5. Tried ethernet to the LAN; .3 MS.  Consistent.  So something might be up with wifi connectivity - since no matter which wifi AP I hit, the variable performance issue mentioned above is a problem.  So, question is...  can I disable wifi and just use this from ethernet with no ill effect?

    • Like 1

  6. Seems like network is the issue.  The pi is seeing ping times of 1.5 ms to 4000ms and it seems bursty.  It'll go fast (2 pings), then several pings at 3 to 4K MS, then another 2 pings at less than 10ms.  Never seen anything like this.  Seems to be this way no matter which wireless net I connect it to.  Presently connected to localhost on the TI console via. telnet to get around the choppy connection speed.

     

    Anyone else seen this?  Should I apt-get update, and then upgrade?  See if I can trade some old bugs for new?  Is there a service I can stop and start for tipi?


  7. Hi Team, Python seems to be consuming 30% of the CPU - the TI is switched off - as is the PEB.  Logged into to the PI to map some drives and it's really sluggish - hard to even edit a file.  Feels like this is new as I don't recall previous ssh sessions on the PI being like this.  Has there been a change, or perhaps a process I can kill?


  8. 7 hours ago, jedimatt42 said:

    I had imagined here: https://github.com/jedimatt42/tipi/blob/8feed0f6cf74adef1670ec9d15d578fa9b483623/services/ti_files/CatalogFile.py#L80

    and here: https://github.com/jedimatt42/tipi/blob/8feed0f6cf74adef1670ec9d15d578fa9b483623/services/ti_files/CatalogFile.py#L95

     

    that the values for mapped drives might want to be different than the values for TIPI. device... 

     

    I think I saw HRD gets away with much larger values. 

     

    I could let you OPEN #1:"PI.CONFIG"::PRINT #1:"SECTOR_COUNT=9900"::CLOSE #1

     

    and that would be persisted, and 9900 or whatever you put there would be the value... What are the limits to this? I believe 16bits are used to refer to sector numbers or block numbers within a file... so 0-64k? a.k.a unsigned int?

     

    That could work...  in the spirit of fooling ancient software, it might make sense to decrement the free blocks by the size of whatever files happen to be in the directory.  Or am I scope creeping...  ;)  Largest floppy I have ever gotten to work is 2880 sectors, DSDD 80 track.  On my 200MB SCSI drive - it reports a total size of 781376, 741024 free and 40352 used.

     

     


  9. Is there any place I can hack a different value into the volume size reported back to the TI?  It's currently fixed at 1440 - but needs to be larger for programs that create bigger than diskette sized files.  The ability for a disk mapping to be 2880 or even 5760 would likely resolve some large file issues I am running into. 

     

    Seems that so long as I run DB sizes that are smaller than 1440 all is OK - but when I merge files that push above that number weird things happen.

     

    Thank you, Arthur...

     

     

    • Like 1

  10. 11 hours ago, jedimatt42 said:

     

    I'd like to figure out your disk mapping issue too... 

     

    1st, the ability for disk mapping to work, requires that the TIPI be the first device that a DSRLNK will discover the DSKn device name on. Typically this means TIPI is at crubase >1000 with a floppy at >1100, or TIPI is at >1100 and you have no floppy controller.

     

    https://github.com/jedimatt42/tipi/wiki/PI.CONFIG <- describes the rules

    https://github.com/jedimatt42/tipi/wiki/TIPICFG <- shows a transcribed screen - copied below

     

    TIPICFG v9   PI-Version: 1.42
    CRUBASE: 1100        IP: 192.168.1.48
    DSR Build: 2018-04-19T21:37:02-07:00
    ----------------------------------------
    
    ----------------------------------------
    Drive Mappings
      1) DSK1=DISKS.INFOCOM.DEADLINE
      2) DSK2=
      3) DSK3=
      4) DSK4=
      J) URI1=
      K) URI2=
      L) URI3=HTTP://www.cwfk.net/4afiles/
    ----------------------------------------
    WiFi Settings
      S) SSID=sillyname
      P)  PSK=*******
    ----------------------------------------
    
    
    ----------------------------------------
    CFG: Q)uit, R)eload
     PI: H)alt, re(B)oot

     

    In the above screen, my mapping of DSK1 is to DISKS.INFOCOM.DEADLINE

     

    DISKS.INFOCOM.DEADLINE is the TI directory: TIPI.DISKS.INFOCOM.DEADLINE.

    The unix path :  /home/tipi/tipi_disk/DISKS/INFOCOM/DEADLINE/

    The windows share path: \\TIPI\TIPI\DISKS\INFOCOM\DEADLINE\

     

    In that directory can live the DEADLINE program image, and support data file. 

    You can then load DSK1.DEADLINE from an EA5 loader, such as CALL TIPI("DSK1.DEADLINE")

     

    If you have the auto-map feature on.. you don't have to have DSK1 pre-mapped... you can CALL TIPI("TIPI.DISKS.INFOCOM.DEADLINE.DEADLINE") 

    It will load the program image and temporarily map the DSK1 drive to the folder it was loaded from.. Having the same result. That temporary mapping will be gone when you return to the TI title screen.

     

    A few posts back, I pointed InsaneMultitasker at the TIPI special file that can live in a directory, and create more complex auto-mappings on program image load. The goal here is you can setup your art software and auto map your clip art folder or save data folders as needed. 

     

    For my own organization, I have a folder TIPI.DISKS. and whenever I upload a .DSK image to the TIPI, I drop it in that folder. I usually only do this for software that relies on volume name or DSKn access. This is just my style, not a requirement.

     

    If your program has volume name matching requirements, like multiplan, then it is important that the leaf most folder name matches the volume name your legacy software expects.. such as TIMP for multiplan. Or INSCEBOT for TI Artist.

     

     

     

    Fixed.  Ran DU2K to get a complete dump of DSR and devices - and discovered the card was set to 1800 - which I should have noticed earlier.  Reset to 1000 and all is working!  :)

    • Like 2

  11. Just a quick comment...  TIPI won't associate to an ESSID that is hidden.  Bug or feature?

     

    I would like to figure out the disk mapping issue.  Can someone post a screenshot of their CALL TIPI screen properly set up?  If I knew what was correct, it would be a good place to start.


  12. In the Happy Happy Joy Joy department...

     

    Though a 8 hour routine of hacking file names and editing binaries with WinHex - to point TI-BASE from "HDX1.TIB." to "TIPI.TIB." and data files to "TIPI.AFTDB" I finally managed to get the software to run from the PI perfectly, and have it access the DB files (also on the PI) perfectly.

     

    Interestingly, this has never before worked anywhere else.  Only diskettes.  All past attempts to place the DB on a hard disk of any type, or HDX resulted in data corruption.  This is sort of a life changing moment for my little TI universe.  It's fast - at least 3x.  My storage limitations are probably a thing of the past.  I used to juggle indexes on and off RAM cards and such - now it all works at high speed (for a TI) in one place.

     

    I could not be happier!  I'm still disappointed that DM2K seems to not like it and there must be bugs in Ti99dir as well (they seem to map filenames in different ways) - and that file name conversions are painful and manual.  I'll test with this for a while, and if good...  I can lose a lot of hardware and maybe put some interesting old stuff up on eBay!

     

    Thank you Matt, Greg, and everyone who has helped me along the way with this!  I'll probably continue to ask dumb questions - but pizza and beer is on me should our paths ever cross!

     

    Cheers, Arthur...

    • Like 2

  13. Hi Jedi, attempting to paint a complete picture of the file naming issues.  I have studied the link you sent.  But I'm still unable to work out a best practices.  I must assume that other people don't have problems copying or reading files and that I am an idiot, missing some crucial bit of into, or have a broken setup - possibly all three...  🤪

     

    Here we see HDX1.TIB (left) copied to TIPI.TIB (right), all looks good.  In ti99dir the file names and designations match.  HDX1.TIB is TI-BASE in a fully running configuration.  I can read all files using View both at source and destination.

     

    step1.thumb.jpg.927046336b38c139b726b550667e05aa.jpg

     

    Here is how the PC see the files...  both on the TIPI and on the SAN containing the HDX1 source directory.  So far, all match up.

     

    313513658_step2pcview.thumb.jpg.61e44bfa444a2f1cf23786250ecd164b.jpg

     

    Looks good so far, then - we go into DM2K to have a look at the directory on TIPI and try to edit SETUP/C (to point TI-BASE at TIPI instead of HDX1).

     

    1250720870_step3dm2kview.thumb.jpg.8fb4d2251686768a0785129a7127d8ee.jpg

     

    WTH???  :)  All screwed up.  So I went ahead and renamed all the files with overscores per suggestion.  TIDIR however now sees all the TI Names as wrong, the /(C or H) is missing - for kicks, I left one TEST(overscore)H which still shows as TEST/H.

     

    442814420_step4afterdotrenametidirseestifileshosed.thumb.jpg.367e41a2978613047bf1a98e1d4c1989.jpg

     

    However, DM2K is loving it...  It sees all the files as properly named now... except for TEST of course, which is as Ti99dir likes...

     

    2094131068_step5nowDM2Kseescorrectfilenameshowevernotxtfileopenable.thumb.jpg.3746360a5e027d4cf7137e767f7f5db2.jpg

     

    However, none of the text files are readable from DM2K - oddly, I can execute TIBASEW - which defaults to DSK1 in the absence of a readable SETUP/C file.

     

    1536352418_step6butnoneareviewable.thumb.jpg.e86f03280e21a236f9b430f91e01e059.jpg

     

    So this is where I am at the moment.  I'll look around at other programs to see if I can view or edit this file - very close to having it work.  If I can make this happen, and then move the DB from diskette.  Life will be better.  I am still completely unable to map DSK4 to any dir on the TIPI.  Again, I must be an idiot or something is broken... because it seems to work for everyone else.  For example...

    97498661_1361943967337452_473367522721136640_n.thumb.jpg.2d9c4a3b9fe5dad5b3502d48572a7d00.jpg

     

    Never results in a working DIR...

    98039054_656653241845162_4583661627403927552_n.thumb.jpg.f042c89c4cd0bd9a12dcf789be9a9d69.jpg

     

    In any event - not sure if this helps in any way.  I guess the question I would have is does this actually work for anyone else?  And if so, what tools have you used to make it work?

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

×
×
  • Create New...