Jump to content


+AtariAge Subscriber
  • Content Count

  • Joined

  • Last visited

  • Days Won


Vorticon last won the day on October 14 2016

Vorticon had the most liked content!

Community Reputation

3,218 Excellent

About Vorticon

  • Rank
    River Patroller

Contact / Social Media

Profile Information

  • Gender
  • Location
  • Interests
    Retrocomputing, electronics, astronomy, tabletop wargaming, tennis

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. That would cool indeed. I'm of those people who still uses CP/M on a fairly regular basis
  2. Works perfectly with the F18A in 80 columns. Love it! Below is Turbo Pascal 3 and Wordstar.
  3. I played with the p-code tool, and overall it works great. I was able to replicate the issue of not being able to edit a text file imported from Windows although it does show up in the directory under the p-code system. However, if I edit an existing text file on the diskette, then the edits do show up. So I suspect that the creation of a new p-code text file is buggy. One way around this issue is to create a nub of a text file under the pcode system on either a new disk or an existing disk then continue the editing process in Notepad using the p-code tool facility. I tested that and it does work. I do hope the author will get around to correcting that bug at some point though. One point: there seems to be an issue with accessing the right mouse button menu for the files on disk. Sometimes it works and sometimes not. So yeah, the tool is still a bit rough on the edges, but even as is I have found it to be incredibly useful. I wish I knew about it previously! Does anyone know the AA handle for Antoon Jansen, the author?
  4. Here's the translated p-code tools document into English. P-code_tools.doc
  5. With the exception of integer math, the latest version of the compiler has removed most of the original limitations. I was able to compile Stratego, a large and complex program in XB, without issues which is frankly quite an achievement.
  6. I definitely plan on implementing an opening library, but I'm not sure I need AMS for that. Too early to worry about it yet
  7. It actually takes 44 minutes, but that's with only a dummy evaluation function. I won't know for sure how much a proper function will add to the processing time until it's complete. The processing time does not increment linearly with each level obviously.
  8. I finally picked this project up again after 4 years as I got tired of feeling guilty over it every time I saw the stack of printouts and notes I conspicuously kept around In any case, it took me almost a week to go over the code again and gain a good understanding of what the hell I was trying to do, although having taken copious notes did help quite a bit. I corrected several bugs along the way and made a few optimizations and now the move generator works as it should down to a depth of 6 ply and I am ready to tackle the position evaluation function, really the heart of the whole project and will determine how well the computer opponent will play. My goal is simple: Phoenix Chess should be able to beat Video Chess at its highest level 100% of the time, otherwise why bother with another chess program! The main issue with coding something like that in UCSD Pascal is that execution speed is quite slow: the program is expected to have 35 levels, and the first level already takes an average of 4 minutes per move. Obviously this will get longer with each level. Anyone wants to take bets on how long level 35 will take? 😄 But hey, this is primarily an educational experience as far as I am concerned so that's fine.
  9. The cart version has a couple of subtle bugs with scoring and play. This was corrected with the disk version. JetPac.dsk
  10. Here are all the pcode disks and documentation in one zip file. Also includes the Turtle Graphics disk by apersson. UCSD Pascal.zip
  11. Here are all the UCSD pascal disks and documentation in one zip file. Perhaps this could go in the Development Thread for ease of use. UCSD Pascal.zip
  12. I think you cannot go wrong with either MAME or Classic99 when it comes to pcode. Your main issue is really going to be how to transfer back the files to the TI. I use Fred Kaal's DSK2PC to transfer the disk images created in the emulator coupled with a USB to serial cable and an RS232 card upgraded with the HDX system (you can also use an unmodified RS232 card but with more limited options). This set up lets you create a real disk on the TI side which is usable with the pcode system. Make sure that you check the disk image for bad blocks with the Filer, correct those with Examine, then Crunch the disk before transferring. This process has worked for up to DSSD disks with the standard TI disk controller. Here's the link for more info Alternatively, I understand that there was a terminal emulator with file transfer capabilities made for the pcode system on the TI, so you could connect the PC and TI with a null modem cable with a USB to serial adapter on the PC end and transfer the files one by one that way. Finally, the Transfer command in the Filer could theoretically also transfer a file via the RS232 and a null modem set up but I'm not sure if this will work with binary files or just text source files. The transfer settings can be changed with the MODRS232 facility on the Utility disk (REMIN/REMOUT), then with Transfer you can enter something like this: REMIN,#4:TEST.CODE . I have not tried this.
  13. Having a mask on all day long as well the requisite distancing will make for a very tiring and awkward day to say the least. Not to mention that this is likely an unsafe situation given that we will be cooped up in one room for the duration and I am willing to bet anything that not everyone will comply with the masking policy. If Hal wants to go for it, that's up to him... Personally I don't need any more exposures than I already get at the hospital every day.
  • Create New...