Jump to content

RXB

Members
  • Posts

    5,828
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by RXB

  1. Here you go I fire it up sometimes for fun... LISP.zip
  2. Well in Classic99 you have 16Meg of SAMS memory? You could use a routine in FinalGROM to load it and run it?
  3. Would make sense to use LISP running under SAMS to do LISP programs?
  4. No the memory of the SAMS or AMS are not saved it you turn off the power. Does not matter if the mapper is on or off, the data is still there as long the SAMS or AMS has power. Does not matter to the data if the DSR is on or off, does not matter if in MAP Mode or PASS Mode the data is still there with power on. If the DSR is on you can use XB or TI Basic (EA Cart) to change RAM memory pages. RXB can talk to 16Meg of RAM pages in the SAMS.
  5. 64 bit? 64-bit data timeline 1961 IBM delivers the IBM 7030 Stretch supercomputer, which uses 64-bit data words and 32- or 64-bit instruction words. 1974 Control Data Corporation launches the CDC Star-100 vector supercomputer, which uses a 64-bit word architecture (prior CDC systems were based on a 60-bit architecture). International Computers Limited launches the ICL 2900 Series with 32-bit, 64-bit, and 128-bit two's complement integers; 64-bit and 128-bit floating point; 32-bit, 64-bit, and 128-bit packed decimal and a 128-bit accumulator register. The architecture has survived through a succession of ICL and Fujitsu machines. The latest is the Fujitsu Supernova, which emulates the original environment on 64-bit Intel processors. 1976 Cray Research delivers the first Cray-1 supercomputer, which is based on a 64-bit word architecture and will form the basis for later Cray vector supercomputers. 1983 Elxsi launches the Elxsi 6400 parallel minisupercomputer. The Elxsi architecture has 64-bit data registers but a 32-bit address space. 1989 Intel introduces the Intel i860 reduced instruction set computer (RISC) processor. Marketed as a "64-Bit Microprocessor", it had essentially a 32-bit architecture, enhanced with a 3D graphics unit capable of 64-bit integer operations.[6] 1993 Atari introduces the Atari Jaguar video game console, which includes some 64-bit wide data paths in its architecture.[7] 64-bit address timeline 1991 MIPS Computer Systems produces the first 64-bit microprocessor, the R4000, which implements the MIPS III architecture, the third revision of its MIPS architecture.[8] The CPU is used in SGI graphics workstations starting with the IRIS Crimson. Kendall Square Research deliver their first KSR1 supercomputer, based on a proprietary 64-bit RISC processor architecture running OSF/1. 1992 Digital Equipment Corporation (DEC) introduces the pure 64-bit Alpha architecture which was born from the PRISM project.[9] 1994 Intel announces plans for the 64-bit IA-64 architecture (jointly developed with Hewlett-Packard) as a successor to its 32-bit IA-32 processors. A 1998 to 1999 launch date was targeted. 1995 Sun launches a 64-bit SPARC processor, the UltraSPARC.[10] Fujitsu-owned HAL Computer Systems launches workstations based on a 64-bit CPU, HAL's independently designed first-generation SPARC64. IBM releases the A10 and A30 microprocessors, the first 64-bit PowerPC AS processors.[11] IBM also releases a 64-bit AS/400 system upgrade, which can convert the operating system, database and applications. 1996 Nintendo introduces the Nintendo 64 video game console, built around a low-cost variant of the MIPS R4000. HP releases the first implementation of its 64-bit PA-RISC 2.0 architecture, the PA-8000.[12] 1998 IBM releases the POWER3 line of full-64-bit PowerPC/POWER processors.[13] 1999 Intel releases the instruction set for the IA-64 architecture. AMD publicly discloses its set of 64-bit extensions to IA-32, called x86-64 (later branded AMD64). 2000 IBM ships its first 64-bit z/Architecture mainframe, the zSeries z900. z/Architecture is a 64-bit version of the 32-bit ESA/390 architecture, a descendant of the 32-bit System/360 architecture. 2001 Intel ships its IA-64 processor line, after repeated delays in getting to market. Now branded Itanium and targeting high-end servers, sales fail to meet expectations. 2003 AMD introduces its Opteron and Athlon 64 processor lines, based on its AMD64 architecture which is the first x86-based 64-bit processor architecture. Apple also ships the 64-bit "G5" PowerPC 970 CPU produced by IBM. Intel maintains that its Itanium chips would remain its only 64-bit processors. 2004 Intel, reacting to the market success of AMD, admits it has been developing a clone of the AMD64 extensions named IA-32e (later renamed EM64T, then yet again renamed to Intel 64). Intel ships updated versions of its Xeon and Pentium 4 processor families supporting the new 64-bit instruction set. VIA Technologies announces the Isaiah 64-bit processor.[14] 2006 Sony, IBM, and Toshiba begin manufacturing the 64-bit Cell processor for use in the PlayStation 3, servers, workstations, and other appliances. Intel released Core 2 Duo as the first mainstream x86-64 processor for its mobile, desktop, and workstation line. Prior 64-bit extension processor lines were not widely available in the consumer retail market (most of 64-bit Pentium 4/D were OEM), 64-bit Pentium 4, Pentium D, and Celeron were not into mass production until late 2006 due to poor yield issue (most of good yield wafers were targeted at server and mainframe while mainstream still remain 130 nm 32-bit processor line until 2006) and soon became low end after Core 2 debuted. AMD released their first 64-bit mobile processor and manufactured in 90 nm. 2011 ARM Holdings announces ARMv8-A, the first 64-bit version of the ARM architecture family.[15] 2012 ARM Holdings announced their Cortex-A53 and Cortex-A57 cores, their first cores based on their 64-bit architecture, on 30 October 2012.[16][17] 2013 Apple announces the iPhone 5S, with the world's first 64-bit processor in a smartphone, which uses their A7 ARMv8-A-based system-on-a-chip alongside the iPad Air and iPad Mini 2 which are the world's first 64-bit processor in a tablet. 2014 Google announces the Nexus 9 tablet, the first Android device to run on the 64-bit Tegra K1 chip. 2015 Apple announces the iPod Touch (6th generation), the first iPod Touch to use the 64-bit processor A8 ARMv8-A-based system-on-a-chip alongside the Apple TV (4th generation) which is the world's first 64-bit processor in an Apple TV. 2018 Apple announces the Apple Watch Series 4, the first Apple Watch to use the 64-bit processor S4 ARMv8-A-based system-on-a-chip. 2020 Synopsis announce the ARCv3 ISA, the first 64-bit version of the ARC ISA.[18] 64-bit operating system timeline 1985 Cray releases UNICOS, the first 64-bit implementation of the Unix operating system.[19] 1993 DEC releases the 64-bit DEC OSF/1 AXP Unix-like operating system (later renamed Tru64 UNIX) for its systems based on the Alpha architecture. 1994 Support for the R8000 processor is added by Silicon Graphics to the IRIX operating system in release 6.0. 1995 DEC releases OpenVMS 7.0, the first full 64-bit version of OpenVMS for Alpha. First 64-bit Linux distribution for the Alpha architecture is released.[20] 1996 Support for the R4x00 processors in 64-bit mode is added by Silicon Graphics to the IRIX operating system in release 6.2. 1998 Sun releases Solaris 7, with full 64-bit UltraSPARC support. 2000 IBM releases z/OS, a 64-bit operating system descended from MVS, for the new zSeries 64-bit mainframes; 64-bit Linux on z Systems follows the CPU release almost immediately. 2001 Linux becomes the first OS kernel to fully support x86-64 (on a simulator, as no x86-64 processors had been released yet).[21] 2001 Microsoft releases Windows XP 64-Bit Edition for the Itanium's IA-64 architecture; it could run 32-bit applications through an execution layer. 2003 Apple releases its Mac OS X 10.3 "Panther" operating system which adds support for native 64-bit integer arithmetic on PowerPC 970 processors.[22] Several Linux distributions release with support for AMD64. FreeBSD releases with support for AMD64. 2005 On January 4, Microsoft discontinues Windows XP 64-Bit Edition, as no PCs with IA-64 processors had been available since the previous September, and announces that it is developing x86-64 versions of Windows to replace it.[23] On January 31, Sun releases Solaris 10 with support for AMD64 and EM64T processors. On April 29, Apple releases Mac OS X 10.4 "Tiger" which provides limited support for 64-bit command-line applications on machines with PowerPC 970 processors; later versions for Intel-based Macs supported 64-bit command-line applications on Macs with EM64T processors. On April 30, Microsoft releases Windows XP Professional x64 Edition and Windows Server 2003 x64 Edition for AMD64 and EM64T processors.[24] 2006 Microsoft releases Windows Vista, including a 64-bit version for AMD64/EM64T processors that retains 32-bit compatibility. In the 64-bit version, all Windows applications and components are 64-bit, although many also have their 32-bit versions included for compatibility with plug-ins. 2007 Apple releases Mac OS X 10.5 "Leopard", which fully supports 64-bit applications on machines with PowerPC 970 or EM64T processors. 2009 Microsoft releases Windows 7, which, like Windows Vista, includes a full 64-bit version for AMD64/Intel 64 processors; most new computers are loaded by default with a 64-bit version. Microsoft also releases Windows Server 2008 R2, which is the first 64-bit only server operating system. Apple releases Mac OS X 10.6, "Snow Leopard", which ships with a 64-bit kernel for AMD64/Intel64 processors, although only certain recent models of Apple computers will run the 64-bit kernel by default. Most applications bundled with Mac OS X 10.6 are now also 64-bit.[22] 2011 Apple releases Mac OS X 10.7, "Lion", which runs the 64-bit kernel by default on supported machines. Older machines that are unable to run the 64-bit kernel run the 32-bit kernel, but, as with earlier releases, can still run 64-bit applications; Lion does not support machines with 32-bit processors. Nearly all applications bundled with Mac OS X 10.7 are now also 64-bit, including iTunes. 2012 Microsoft releases Windows 8 which supports UEFI Class 3 (UEFI without CSM) and Secure Boot.[25] 2013 Apple releases iOS 7, which, on machines with AArch64 processors, has a 64-bit kernel that supports 64-bit applications. 2014 Google releases Android Lollipop, the first version of the Android operating system with support for 64-bit processors. 2017 Apple releases iOS 11, supporting only machines with AArch64 processors. It has a 64-bit kernel that only supports 64-bit applications. 32-bit applications are no longer compatible. 2018 Apple releases watchOS 5, the first watchOS version to bring the 64-bit support. 2019 Apple releases macOS 10.15 "Catalina", dropping support for 32-bit Intel applications. 2021 Microsoft releases Windows 11 on October 5, which only supports 64-bit systems, dropping support for IA-32 systems. 2022 Google releases the Pixel 7, which drops support for non-64-bit applications. Apple releases watchOS 9, the first watchOS version to run exclusively on the Apple Watch models with 64-bit processors (including Apple Watch Series 4 or newer, Apple Watch SE (1st generation) or newer and the newly introduced Apple Watch Ultra), dropping support for Apple Watch Series 3 as the final Apple Watch model with 32-bit processor.
  6. RXB since 2000 has had a subroutine CALL IO that plays music lists the same ones we see used in cartridges and games. Is this new music player able to do more then what CALL IO does?
  7. Thanks for reply Ralph In making RXB using GPL most of my code was patching GPL so it was tons on AORG commands in GPL Assembler so address could remain the same for XB GPL and ROMs. Over time I have really reduced that number but many are still there for XB ROM routines mostly, or for tables that would be really hard to move. I did have one huge file at one time but the GPL Assembler would crash as way to many in symbol tables so I had to break it up for separate GROMs. I will be on ZOOM today at 11 AM and will show the problems I am having. Rich
  8. OK now I have another problem the xga99 Assembly creates Binary files but they are not the same size as the files that the Ryte Data GPL Assembler Object files in size? In my Source Code I have AORG >1FE0 which should be jumping forward to >5FE0 from that location forward and seems to be ignore by the Binary code generated by XGA99? Which explains why the size is just wrong. Also why every time I try to make the RXB module it shows huge gaps in wrong locations and just wrong? Should I assemble RXB in one huge Source file? Can someone explain what is going on?
  9. So is the format thing fixed or am I forced to use this secondary tool to use your GPL Assembly? I am very impressed with the insane speed and very effective result of your version of GPL Assembly. But the Tool from Lucien2 makes my GPL code almost impossible to read and edit. Any progress is making it more standardized?
  10. I have a sticky note on my monitor to Disassembly GPL of TOD and release it. You will find GPLDISASS in any RXB release.
  11. Yea you would think sticking to the the original TI standards for GPL would be pretty set in stone as TI invented GPL! Oh and the EA format too!
  12. Hmm Ryte Data GPL Assembler did not care if the it was first one as * asterisk is the comment character just like ! or REM is for XB. Exactly the same as the original TI GPL Assembler for the 990 and the GPL Code for XB version 110 and TI GPL Manual and GPL Device Service Manual. Rather oddball is ; semicolon being used as comment symbol for GPL Source, that must come from something like Python or C or another language. I really like your GPL Assembler except for the strange changes like 2 spaces after a command or using a ; is just so weird since I have been writing GPL for over 35 years now. Can you think of a EA or GPL command that would begin with *something? Commands like CLR *R8 or CLR *>8300 so why would it matter if the second character is a * as it would not be valid as any command and only a comment!
  13. Yea here is the PREDEFINED SYMBOLS for Ryte Data GPL Assembler. ******************************************************************************** PREDEFINED SYMBOLS ******************************************************************************** Symbol Table #4 (Def,alpha) 0034 ACCTON 835C ARG 0032 ATN 0036 BADTON 003B BITREV 0012 CFI 0014 CNS 002C COS 0010 CSN 8372 DATSTK 0001 DIVZER 0003 ERRIOV 0006 ERRLOG 0005 ERRNIP 0002 ERRSNN 0004 ERRSQR 0028 EXP 834A FAC 0006 FADD 000A FCOMP 0009 FDIV 0008 FMUL 836C FPERAD 0007 FSUB 0038 GETSPACE 0022 INT 0010 LINK 0018 LOCASE 002A LOG 8370 MEMSIZ 003D NAMLNK 8300 PAD 0024 PWR 0012 RETURN 000B SADD 000F SCOMP 000E SDIV 8375 SGN 002E SIN 000D SMUL 8400 SOUND 0026 SQR 000C SSUB 837C STATUS 0016 STCASE 8373 SUBSTK 0030 TAN 0007 TRIGER 004A UPCASE 836E VSPTR 0001 WRNOV 837F XPT 837E YPT Can you imagine if that is the standard in C or other languages with no format settings. It would be impossible to debug or to even write the language. So I am going to have to stick with notepad and txt files as at least it is readable. Thanks for your help.
  14. Sure it is mostly finished. The DV80 files are in RXB GPL GROM The DOS TEXT files are in RXB GPL SOURCE TEXT RXB 2024C.zip
  15. Ok did that and the .gpl files have a kind of listing but where is the rest of the file? Like srxb3 is missing most of the code? Where did it go? Or srxb7.gpl is only like 1/3rd of the entire module code? Using Ti99Dir to look at them and they are DOS files and I did use TI Files from srxb3.txt converted by Ti99Dir
  16. Cool tool thanks! Does not fix srxb6.txt that crashes at END and I guess ralph is working on that one.
  17. Oh I see it lists undefined EQU that have not been defined!
  18. What kind of files as the ones you have here are not text from Notepad? When I try to view them they look like gobbly gook? And is this a disassembler or something else? Ok it makes my source files like srxb3.txt into a 1K file srxb3.gpl but 90% of the stuff is missing? What exactly am I looking at here? No list file to read and this is even more of a mystery? gromcart.exe rxb.cmd rxb.js srxb3.gpl srxb3.txt srxb4.gpl srxb4.txt srxb5.gpl srxb5.txt srxb6.gpl srxb6.txt srxb7.gpl srxb7.txt xcommon.py xga99.py
  19. I think a $20 wireless USB keyboard from Wallmart is a great option. Goes well with a 22 inch video flat screen monitor. I can sit farther away and see the screen better.
  20. Ok thanks, but RXB 2012 was hella long time ago. (over 12 years ago so kind old version) Considering I just released RXB 2024B and have RXB 2024C on my desktop being debugged.
  21. Problems with Ryte Data GPL Assembler and RAG GPL Assembler and even Thierry GPL Assembler all crash for various reasons. None of these apparently are designed to deal with this project. Some commands just crash Ryte Data GPL Assembler due to 35 year old bugs. RAG GPL Assembler only lists to Printer so unusable to list to Disk or Hard drive Thierry GPL Assembler gives errors that are not defined or why it crashed as there is a error it just stops working with no clue what is wrong! With no list file to explain what is wrong it makes the Assembler totally useless, same exact problem I had with RAG GPL Assembler. So had Ralph help me install to use XGA99 on my PC to use it instead, but OMG still problems that thankfully Ralph is working on fixing. But some success as replacing many of the VDP Flags and Temp locations from VDP to RAM has shown this is going to work. I have yet to put the Crunch Buffer from VDP to RAM or the VDP STACK from VDP to RAM but that requires some XB ROM modifications first. (This is going to free up some XB ROM space for more features.)
  22. Actually you can still do a CALL GPOKE in Classic99 it you turn on that option. Most XB have CALL GPOKE so it works fine. Why well you can rewrite XB from XB!
  23. ******************************************************************************** PREDEFINED SYMBOLS ******************************************************************************** Symbol Table #4 (Def,alpha) 0034 ACCTON 835C ARG 0032 ATN 0036 BADTON 003B BITREV 0012 CFI 0014 CNS 002C COS 0010 CSN 8372 DATSTK 0001 DIVZER 0003 ERRIOV 0006 ERRLOG 0005 ERRNIP 0002 ERRSNN 0004 ERRSQR 0028 EXP 834A FAC 0006 FADD 000A FCOMP 0009 FDIV 0008 FMUL 836C FPERAD 0007 FSUB 0038 GETSPACE 0022 INT 0010 LINK 0018 LOCASE 002A LOG 8370 MEMSIZ 003D NAMLNK 8300 PAD 0024 PWR 0012 RETURN 000B SADD 000F SCOMP 000E SDIV 8375 SGN 002E SIN 000D SMUL 8400 SOUND 0026 SQR 000C SSUB 837C STATUS 0016 STCASE 8373 SUBSTK 0030 TAN 0007 TRIGER 004A UPCASE 836E VSPTR 0001 WRNOV 837F XPT 837E YPT Sorry where is this tool looked for it and can not seem to find it? CFI, LINK, RETURN, ACTION and BADTON are all predefined in Ryte Data GPL Assembler why I never need EQU to define them. ASSM-DOC.txt
  24. Well here is another error and I am clueless why it exists? C:\Users\Rich\Desktop\SAMS>xga99.py srxb6.txt -o brxb6 -L lrxb6.txt : xga99, version 3.6.1 > srxb6.txt <0> 1938 - * END * ***** Error: Syntax error 1 Error found. THIS IS THE END OF THE PROGRAM WHERE IT SAYS SYNTAX ERROR *********************************************************** * CALL VERSION(numeric-variable) * *********************************************************** VERSN DATA >0000 STRI 'VERSION' DATA $+2 CALL COMB Insure have left parenthesis XML PGMCHR Skip ( CALL SNDER Get variable info DST 2024,@FAC 11/29/2023 CALL CIFSND Convert to floating point * Assign and return to caller B LNKRTN ************************************************************** END I moved the END all the way from the * END * but get the same exact error even if it iis 20 lines from the line of ***** Why is it saying this?
×
×
  • Create New...