rasmus-m / js99er-angular Goto Github PK

previously worked - when using Stuart's web browser i can move the mouse with the pointer but it won't click on anything

I follow all the instructions, but I'm getting the following error, during build:

ERROR in ./node_modules/@angular-devkit/build-angular/src/angular-cli-files/models/jit-polyfills.js
Module not found: Error: Can't resolve 'core-js/es7/reflect' in '/Users/omar/Downloads/js99er-angular-master/node_modules/@angular-devkit/build-angular/src/angular-cli-files/models'

Please advise. Thx.

using a usb to retro joystick adapter
Retro Joystick Adapter v3.0 (Vendor: 16c0 Product: 0a99)
INDEX 2
CONNECTED Yes

this connects to joystick 2 instead of joystick 1.. this is the only controller I have in my system and classic99 connects it as joystick 1.. (confused)

Hiya

1. Installed newest NodeJS
2. Clone repository
3. Installed both angular and http-server
4. Did a npm install in src directory as always.
5. In js99er-angular base folder I did ng build --prod.

Get the following error:

An unhandled exception occurred: error TS5083: Cannot read file 'C:/js99er-angular/tsconfig.base.json'.

See "C:\Users\pjdup\AppData\Local\Temp\ng-R0qoX3\angular-errors.log" for further details.

Contents of that logfile is:

[error] Error: �[91merror�[0m�[90m TS5083: �[0mCannot read file 'C:/js99er-angular/tsconfig.base.json'.

at Object.readTsconfig (C:\js99er-angular\node_modules\@angular-devkit\build-angular\src\angular-cli-files\utilities\read-tsconfig.js:28:15)
at Object.configureI18nBuild (C:\js99er-angular\node_modules\@angular-devkit\build-angular\src\utils\i18n-options.js:98:38)
at Object.generateI18nBrowserWebpackConfigFromContext (C:\js99er-angular\node_modules\@angular-devkit\build-angular\src\utils\webpack-browser-config.js:86:57)
at buildBrowserWebpackConfigFromContext (C:\js99er-angular\node_modules\@angular-devkit\build-angular\src\browser\index.js:68:41)
at initialize (C:\js99er-angular\node_modules\@angular-devkit\build-angular\src\browser\index.js:97:69)
at buildWebpackBrowser (C:\js99er-angular\node_modules\@angular-devkit\build-angular\src\browser\index.js:115:24)
at onInput (C:\js99er-angular\node_modules\@angular-devkit\architect\src\create-builder.js:151:30)
at SafeSubscriber._next (C:\js99er-angular\node_modules\@angular-devkit\architect\src\create-builder.js:65:29)
at SafeSubscriber.__tryOrUnsub (C:\js99er-angular\node_modules\rxjs\internal\Subscriber.js:205:16)
at SafeSubscriber.next (C:\js99er-angular\node_modules\rxjs\internal\Subscriber.js:143:22)
at Subscriber._next (C:\js99er-angular\node_modules\rxjs\internal\Subscriber.js:89:26)
at Subscriber.next (C:\js99er-angular\node_modules\rxjs\internal\Subscriber.js:66:18)
at Object.next (C:\js99er-angular\node_modules\rxjs\internal\observable\onErrorResumeNext.js:22:49)
at SafeSubscriber.__tryOrUnsub (C:\js99er-angular\node_modules\rxjs\internal\Subscriber.js:205:16)
at SafeSubscriber.next (C:\js99er-angular\node_modules\rxjs\internal\Subscriber.js:143:22)
at Subscriber._next (C:\js99er-angular\node_modules\rxjs\internal\Subscriber.js:89:26)

Can you help please?

All on Windows

last week I was debugging code that erroneously wrote to the screen when in 80x30 mode.
js99er is the only emulator that handles that mode correctly.

I had no idea what code was writing that character.. it was part of some level 2 io code... just shouldn't have touched hte screen at all.. but I could identify visually approximately where the write was in vdp, then pinpoint the address I wanted to break on, but couldn't figure out if there was a way to set a vdp breakpoint.

So I ran in classic99, which does let me break point, to find that the io routine was using a vdpchar routine out of libti99 that we hijacked to automatically fill in the color attribute when writing a byte... anyway, vdpchar in libti99 with extended attributes on is no longer a generalized VSBW routine, so it shouldn't be used as such in the dsrlnk implementation... ( ok that was still a long story )

A breakpoint on VDP write would have allowed discovering and resolving this with one emulator instead of 2.

If I do something like this in regular TI BASIC

100 OPEN #1:"GDR1.BASE01",RELATIVE,INTERNAL,INPUT,FIXED
110 IF EOF(1) THEN 150
...
150 CLOSE #1

I get an I/O Error 93.

I tried it with several other options (SEQUENTIAL, DISPLAY, VARIABLE) and had the same experience.

Looking at the debug log, I see I'm getting a return value of 3 from the STATUS DSR call.

I don't get this behaviour if I open a file on DSK1 (or presumably any other local emulated disk.)

Is this a known bug? If so, is there an ETA to fix it? I'm happy to dig into it and do some more debugging if you're hip to pull requests.

After clicking the Restore State button to restore a previously-saved state, the video goes back to a damaged TI-99/4A title screen. The restored program does seem to be running in the background, but the title screen obscures it.

Steps to reproduce (I am using a particular program, I don't know if it affects other programs).

1. Load Blackjack and Poker
2. Press any key to dismiss console title screen
3. Press 2 to start Blackjack and Poker
4. Start a game of Poker
5. Click the Save State button.
6. Click the Restore State button. The console title screen will appear and you will not be able to see the running program.

This seems to have been introduced in the 9.0.0 release.

setting to full tipi does nothing. nothing in logs about trying to attach, no attempts to connect on the tipi side

Sprites appear to be written to the character table instead of the sprite table

Attached is an image of what i mean

Hi.

I am trying to build a production version (again) after reinstalling my pc.

I am using the instructions you gave on AtariAge forum, and using both NodeJS 18.16.1 and 20.4.0. (By the way, with newer versions of NodeJS you now have to use ng build --configuration production, in stead of ng build --prod).

The angular install does not give any errors, as well as the npm install part in the src folder.

The ng build now gives me an error. It worked a week or so ago on NodeJS 18.6.0, but not on 18.6.1 or on 20.4.0.

See screenshot:

Do you have any idea on how to solve this?

Regards

Pieter

Hi Rasmus

I am getting the following build error:

ERROR in Template parse errors:
Unexpected closing tag "mat-select". It may happen when the tag has already been closed by another tag. For more info see https://www.w3.org/TR/html5/syntax.html#closing-elements-that-have-implied-end-tags (">Hex view
<mat-option [value]="2">Split view/mat-option>
[ERROR ->]


"): C:/js99er-angular/src/app/components/debugger/debugger.component.html@11:12
Unexpected closing tag "mat-form-field". It may happen when the tag has already been closed by another tag. For more info see https://www.w3.org/TR/html5/syntax.html#closing-elements-that-have-implied-end-tags ("
<mat-option [value]="2">Split view/mat-option>

[ERROR ->]

<mat-form-field class="memory-"): C:/js99er-angular/src/app/components/debugger/debugger.component.html@12:8
Unexpected closing tag "div". It may happen when the tag has already been closed by another tag. For more info see https://www.w3.org/TR/html5/syntax.html#closing-elements-that-have-implied-end-tags ("
Hexadecimal

[ERROR ->]

I am using nodejs ltr version12.16.1 npm version 6.14.1, and angular 9.0.4.

npm install worked, but not ng build --prod

Pieter

For some reason if the program in memory is above a critical size, get a I/O ERROR 03 when trying to save it to CS1.

Steps:

1. Load a .TIDisk into js99er (used you website)
2. OLD DSK1.BJ or MERGE DSK1.BLACKJACK
3. LIST 100 (to ensure it loaded properly)
4. SAVE CS1

Result:

• I/O Error 03

If the program loaded into memory is small enough or you just add a few lines by hand, the save to .wav goes as planned. I am not sure how big is too big.

Here is a .TIDisk I am using with some homebrew programs: https://github.com/seanwo/ti994a/blob/main/github.TIDisk (it contains 2 program files BJ and BS along with the source files that can be merged BLACKJACK and BATTLESHIP) if you want something to reproduce with.

So I have my homebrew cart is built as both a ROM and GROM.

When I use the "cartridgeURL" element to specify the cartridge, I can point it to either one and it shows up in the launch menu after the title screen, but only the ROM works.

If I point it to the ROM it will launch.
If I point it to the equivalent GROM it hangs with a long beep.

I have no problem using the toolbar to load either the ROM or GROM manually.

Works:

<js99er config='{"sidePanelVisible": true, "toolbarVisible": true, "cartridgeURL": "mysoftware/BLACKJAC-8.BIN", "settings": {}}'>

Does not work:

<js99er config='{"sidePanelVisible": true, "toolbarVisible": true, "cartridgeURL": "mysoftware/BLACKJAC-G.BIN", "settings": {}}'>

Testing in development mode

ng serve

ROM and GROM:

https://github.com/seanwo/ti994a/blob/main/BLACKJACK/BLACKJAC-8.BIN
https://github.com/seanwo/ti994a/blob/main/BLACKJACK/BLACKJAC-G.BIN

Is there some setting I need to add? Thanks!