kl99

This is version 0.4 of Web99: I want to give you a quick update on this project. There is heavy works going on on this for a while now. Further I did a presentation on the TI Treff and on the Chicago TI Faire about Web99. Here is a presentation about Web99 from the Chicago TI Faire 2015: http://www.ustream.tv/recorded/76712901?rmalang=de_DE What was worked on? - nice treeview of what is Inside the Index, all Types (DIS/FIX, PROGRAM,...) get their own icon - TI Basic/Extended Basic Syntax Highlighting - created a custom Lexer for within the Scintilla Library - added a custom Scintilla.Net Library based on that - this will be extended to Syntax Highlighting for all other kinds of Source Code like Assembler, GPL,... - a public independent release of this will come for other Tools to integrate, just need to get some bugs fixed there - fulltext search within TI Basic/XB Source Files - using Subversion for Version Controlling the Source Code of the Project for a while already - created classes for TI Entities like Ti File Binary, Ti File, Disk File Record, Disk and Disk Clone and seperated them from methods which are extracting data for those - found a big bug in the code which let clustered Ti Files to not have a correct/usable binary, fixed it of course. Many more Basic Program have been extracted as a result. - started to write some first Unit Tests to test the Code of Web99 - added a lot of checks in code to not let a corrupt Disk Image crash the Application - small fixes to Basic Source Code formatting, the reference for the look is always how it looks when you LIST the same program in your TI. Both TI99Dir and TIImageTool have some issues there as well. - Basic Source Code Extraction now properly stores and displays characters beyond Ascii Code 127 (using Codepage 850). Thanks to John G. for pointing out the need. - Fixes in calculation of FileSize and ClusterLength (many Files have incorrect values in their File Descriptor Record) which have let to corrupt Binaries. Have fun: Web99 version 0.4 2015-11-09 Web99_2015-11-09_v0.4.zip

That story made my day. Now that we actually met in person, I can imagine your "evil" smile towards him even better. I guess this guy still has nightmares of that moment. Thanks for that Ksarul.

For both versions of the PEB you can switch the Voltage to 220. I did a thread on this when I opened mine to change it, all is documented with photos. No Powerconverter needed.

very nice list, never saw that. I remember Jens-Eike told me he ordered such parts from TI instead of hunting down rare cartridges back in the days.

Here are some Auctions without the name TI-99 in them, so more hard to find: TI Flex Interface: http://www.ebay.com/itm/Texas-Instruments-TI-Flex-Cable-Interface-Card-with-Connector-Cable-/131615611631?hash=item1ea4e6daef http://www.ebay.com/itm/131613567457 Cartridges: http://www.ebay.com/itm/151846158728 http://www.ebay.com/itm/161855365843 http://www.ebay.com/itm/262086523807 http://www.ebay.com/sch/m.html?_odkw=&_ssn=theoneeyedowl&item=171957952767&_osacat=0&_from=R40&_trksid=p2046732.m570.l1313.TR0.TRC0.H0.Xtexas.TRS0&_nkw=texas&_sacat=0 http://www.ebay.com/sch/todhah-0/m.html?item=262068535767&rt=nc&_trksid=p2047675.l2562 http://www.ebay.com/itm/400503057582 http://www.ebay.com/itm/171942297912 http://www.ebay.com/itm/161832482220 http://www.ebay.com/itm/201447801484 http://www.ebay.com/itm/141777553894 http://www.ebay.com/itm/131604262859 http://www.ebay.com/itm/ZeroZap-command-module-Texas-Instruments-1979-Milton-Bradley-company-ultra-rare-/331467022971?hash=item4d2cf9627b http://www.ebay.com/itm/161551623927 http://www.ebay.com/itm/261978435805 http://www.ebay.com/itm/231676727195 http://www.ebay.com/sch/m.html?_odkw=&_ssn=leeannshop2014&item=221885207824&_osacat=0&_from=R40&_trksid=p2046732.m570.l1313.TR0.TRC0.H0.Xtexas.TRS0&_nkw=texas&_sacat=0 http://www.ebay.com/itm/262084422293 http://www.ebay.com/sch/m.html?_odkw=&_ssn=frontier_quality&item=291534367012&_osacat=0&_from=R40&_trksid=p2046732.m570.l1313.TR2.TRC0.A0.H0.Xtexas.TRS0&_nkw=texas&_sacat=0 http://www.ebay.com/itm/161391578858 http://www.ebay.com/itm/351139043642 http://www.ebay.com/itm/221897146293 http://www.ebay.com/itm/301721556965 http://www.ebay.com/sch/m.html?_odkw=&_ssn=wookiesdontburn&item=310852680838&_osacat=0&_from=R40&_trksid=p2046732.m570.l1313.TR12.TRC2.A0.H0.TRS0&_nkw=texas+instruments&_sacat=0 Manuals/Books: http://www.ebay.com/itm/301764597506 http://www.ebay.com/itm/381415962312 http://www.ebay.com/itm/Vintage-70s-Texas-Instruments-Computer-Employee-Books-Annual-Reports-Lot-/121599905562 http://www.ebay.com/itm/171371844009 http://www.ebay.com/itm/321892190932 http://www.ebay.com/itm/252122636043 http://www.ebay.com/itm/221407180435 http://www.ebay.com/itm/161828607123 Broschures/Ads: http://www.ebay.com/itm/261824669476 http://www.ebay.com/itm/291567101628 http://www.ebay.com/itm/130509761325 http://www.ebay.com/itm/262090628575 Disks/Tapes: http://www.ebay.com/itm/371427833237 http://www.ebay.com/sch/m.html?_odkw=texas&_ssn=bridgett372&item=391245869767&_osacat=0&_from=R40&_trksid=p2046732.m570.l1313.TR12.TRC2.A0.H0.Xtexas+instruments.TRS0&_nkw=texas+instruments&_sacat=0 http://www.ebay.com/itm/291567097095

Here are the Infos: http://www.chicagotiug.com/tiki-index.php?page=Faire Looking forward to meet you guys, some again and some for the first time. Klaus

I am coming to Chicago this year!

It would further be interesting to finally have a list of all Euroepan Product Numbers of the European Cartridges. Most look like 1103056-0002 or 1103058-0001 where the last digits stand for the regions/languages.

The Game was 'Made in Austria' The author was participating a TI-99 meeting in 2013 or 2014 in Vienna.

Hi! I have collected a list of all kind of TI-99 Specifications, that I have heard of or are referenced somewhere. internaldocuments.xls For sure I have missed some things. Most of them come from either whtech or The Cyc (cadd99.com). The list contains link references to Whtech and File Paths of TheCyc Encyclopedia DVD, if available. Many Specifications contain a section of "Applicable Documents" listing further related Specifications. Klaus

AMAZING!!!! TOP Graphics! Is the engine or your game using the GPU in any kind? This really shows the potential of the F18a Klaus

did anyone here have won the auction on the P-System Specification for the TI-99/8?

Is somebody from here bidding on this? I would be interesting in preserving the document: http://www.ebay.com/itm/The-P-System-Version-IV-14-For-The-TI99-8-Original-Specification-TI99-8-TI-99-4A-/131578028218?hash=item1ea2a960ba "The P-System Version IV.14 For The TI99/8 Original Specification" According to my list of documents, this Specification is not on whtech, nor in the Cyc DVD, nor online elsewhere.

Hi opry, I am interested in buying the cartridges. i only have 3-4 romox so far. and funware I only have.ambulance, rabbit trails, driving demon, vegas, st. nick. I am sending you a wanted list, I once did. Maybe you have something. Klaus

i have booked this week, so count with me

I have some "mapper" tool called com0com http://sourceforge.net/projects/com0com/ It creates two or more virtual serial ports for you. So you can connect Ti994w or Pc99 to one of the virtual ports and receive the send data on the other virtual port in another tool, staying on the same machine. Best is to use TI-99 print i guess. These virtual ports work with Web99 as well, it would shows the incoming chars in the communication window, however it's not styled nor does it support graphics, and without a Save option. For listing basic program its sufficient, but for anything else not. In a future release I want to support it all, inlcluding creating a pdf.

2015-06-04 Version 0.2 - during Indexing each TiFile of Type "PROGRAM" is checked whether it's actually a Basic or XB Program. The Basic Sourcecode is then saved into a field called SOURCE. The Type is changed from PROGRAM to BASIC. You can already perform a full text search within the SOURCE field and see matching documents in the result. Example: +documenttype:tifile +source:apesoft Nothing more is yet visualized (you don't see the source code yet) because this new feature opens up some questions. ? How to deal, if the Basic SourceCode is identical but the TiFile is not identical on binary level. ? How should embedded assembler code in a PROGRAM file be handled if there is any. (I don't know yet where to search for that in the binary). ? The algorithm for when a space shall be added or not added before/after a Token is not yet clear and seems to be solved different across all tools. If I create a Hash based on the Basic Sourcecode, it's essential that this is clear/correct before doing that. ? There is no output information yet why a certain Program failed to be identified as a Basic Program. ? The token size of the source field is limited to 256 bytes. This is suboptimal. You can visualize the source field or any other field with the external Tool Luke by pointing it to the Index Folder: https://code.google.com/p/luke/downloads/detail?name=luke-1.0.1.jar&can=2&q=

This is a very good idea for a thread. I want to extend Web99 to have the possibility to store information like this as part of every TiFile Document. The connection to a certain TiFile will be done via Hash of its Binary. The fields shall be editable from TI-99 & from Windows and can be shared worldwide. Just imagine a "HowToUse" Field. Of course this needs to be entered once manually (but not by everyone). But the good thing is, you have that information automatically next to every disk that features the same program (hash comparison). And you will get the entered information from other Users. Another field will be a pointer from the TiFile Program to the Documentation TiFile. So, if you have the program on Disk A, and the Documentation on Disk Z, you will have a connection between those two files. And get that data on your TI-99 screen, when you actually need it. There will be meta data fields that will be auto-populated like (TI-Basic, XB, Assembler,... instead of only seeing PROGRAM for Filetype)

I don't recommend using Hdx for verifiying a cable connection. As I said before the third party library inpout32.dll used by this tool is not initializing the port the correct way. Therefore you won't have success unless you initialize the port with some other program first, I use DoxBox for that. If you have a Hdx cable (which is non-twisted), you can try my software which is not having troubles with initalizing the serial port on Profilic Chipsets. http://atariage.com/forums/topic/238433-web99-search-your-tifilesdisks-version-01c-released/ It's good enough to verify the cable is working and to get a telecommunication program on the TI, when nothing is on it yet. Here is a video on how easy it is to connect a load the program via RS232 onto the TI-99: http://screencast.com/t/KxffrrrGrD6

I am planning for a bluetooth2Serial adapter. That way even the cable is no longer an issue. I verified a general issue with the HDX Windows Software, which is related to the dll Library that is used by the tool for Serial I/O. Are you using an USB2Serial Adapter? If yes, which chipset? I posted 3 videos in the facebook Ti-99ers group which shows an issue on initializting the widely used Chipset family: Prolific Technology Chips PL2303. schmitzi verified the issue on his adapters. This issue is not appearing when using a real Serial Port on Pc Side. YOu can view the posts/videos here: https://www.facebook.com/groups/2209774843/permalink/10153023277249844/ https://www.facebook.com/groups/2209774843/permalink/10153023287499844/ https://www.facebook.com/groups/2209774843/permalink/10153023311114844/ BR Klaus

I like the approach from Gazoo! atrax27407, what makes HDX usage complicated? I am working on a tool that does not yet cover your usecase, or at least not beyond prototype status. It's called Web99 and can be found here If you explain the weakness you see in the current tools and solution, I might be able to come up with something that you like as well.

My brother has got a QWERTZ (=german) TI-99/4a but that is a mod and was done by some usergroup before he got it. I think to remember there has been an how-to for such a mod in some german Usergroup Newsletter or german Magazine.

Here is a video demonstration on how to search on a TI-99 and load the selected program from the search result via RS232. http://screencast.com/t/KxffrrrGrD6

new verison released: see post #1 for download 2015-05-24 Version 0.1C - by accident the last version was published with DISKSIZE set hardcoded to 1440 (for testing purposes) and excluded SECTORSFREE, SECTORSUSED. fixed that. - NumericFields were changed by Lucene to StringFields when you clicked on Find Duplicates (which updated all documents). This behavior of Lucene was badly documented and is no longer an issue. - The QueryParser now generates a NumericRangeQuery when you use it on a numeric Field. Simply use it like +SECTORS:[3 TO 12] or when filtering disks you can try +DISKSIZE[360 TO 720] - The Field DISKNAME and PATH were not case insensitive yet. You can search for Path now: +PATH:*WHTECH*

I guess this is what I meant. When we talk about RS232, at some point you want to parse what is communicated via CRU to the Pc Serial or Parallel Port. When we talk about Disk DSR, at some point you pass in a Pc File or a Pc Directory. It is the problem that you don't see the original DSR running and can step by step start to understand what is happening, but a fake DSR. Classic99 doesn't support the RS232, PIO devices right now, so i can't use it to understand the ongoing things between DSR/CRU/PAB/Monitor. Please don't take this as critic, your program is fantastic and is running daily on my machine. And we can't thank you enough for this tool. One example I was thinking of when writing this was where I have tried to change the PAB for an opened file. I tried to set Device Filename from DSK1.TEST to DSK2.TEST. I had the file in both pc directories. As far as I remember I changed it in Scratch Pad Ram and Vdp. I got frustrated because it didn't work. I guess you are right, that Mess includes a very complete RS232, CRU, 9902, 9901 emulation and even connects to the outside world via this writing to the file. It's probably simply because I don't know how to properly debug Mess beyond having a CPU debugger. Since it's a complicated topic I have always found other things todo for Web99. What kept me from doing it on the real device until now? I have heard horror stories from fried 9901 chips (or 9902?) from Marc Hull, by nothing more than setting wrong CRU.