Kowalski Simulator Updates

[JenniferDigital]

Might there ever be a Linux native build of Kowalski Simulator? I've been running it in Wine for a long time but there have been issues that just might be because of that.

[BigDumbDinosaur]

DigitalDunc wrote:

Might there ever be a Linux native build of Kowalski Simulator? I've been running it in Wine for a long time but there have been issues that just might be because of that.

The simulator is strongly dependent on Microsoftness to function. While I wouldn't say a Linux rendition is impossible, it would likely be a lot of work to get there.

Due to the usefulness of the simulator, I keep a Windows XP box functioning for that, as well as for my mechanical CAD software. I've not tried the simulator in WINE (running on SLES 11SP4), but have testing the CAD software in that environment. It's not as stable in WINE as it is on an actual Windows box.

[JenniferDigital]

Well, (shuffles shoes and sulks) I do have an old Athlon XP box doing nothing but getting in the way under the desk. I suppose I could use that and certainly find avoiding WinBlows makes for some interesting tool choices.

[BigDumbDinosaur]

DigitalDunc wrote:

Well, (shuffles shoes and sulks) I do have an old Athlon XP box doing nothing but getting in the way under the desk. I suppose I could use that and certainly find avoiding WinBlows makes for some interesting tool choices.

Regarding the use of Window$ to run the simulator, sometimes you just have to get down in the mud and wallow with the hogs to get the job done.

[JenniferDigital]

I'll set it up Friday and see if it's better than the experience I'm getting now. I'll let the world know if things work better natively with it since others might appreciate such info. Right, I've gotta go read up on tapes. I'm building a tape interface for the ToE (not because it's any good but because it was how things were in the day). I'll give the new build of the sim a go too as I'm on an old build and see how things have changed.

Mud, mud, GLORIOUS MUD!

[Druzyek]

Something like Chrome Remote Desktop might work for you. It works on at least some versions of Linux. I keep an old laptop from 2011 on my work table with all of my electronics stuff hooked up and access it from my newer laptop. That way, I can write and test all of my programs on the newer laptop even if I'm not at home but still use the old one to program EEPROMs and microcontrollers. My build scripts automatically copy compiled files to a network drive shared between the two, so if I happen to be at my desk, I can put the EEPROM in the programmer, switch to the Remote Desktop window and press program. I even stack the new laptop on top of the old one when I'm at my desk because there's no reason to ever open the screen on the old one since I can just see it with Remote Desktop. Something like that might work if you have an old Windows box you can access with your Linux machine. You wouldn't even have to keep a monitor or keyboard for it once you had it set up.

[jdimeglio]

dclxvi wrote:

jdimeglio wrote:

https://github.com/jdimeglio/6502-Monitor

Looks like you've got a bug in the T command; there should be a CLD at NBRNCH (after JSR SAVE) and BRANCH, otherwise the PCADJ calculations can be wrong if you step through code that runs in decimal mode. The S command from the Apple II old monitor ROM has this same bug for the BRANCH case (the SAVE registers routine contained a CLD so NBRNCH was ok).

See also this post on the same subject:
viewtopic.php?p=68234#p68234

@dclxvi Great thanks for the feedback, i'll check it out.. Ive also since burnt it to ROM and found/fixed several other bugs that only was able to be found in real world. eg: the simulator sets RAM to zero and well long story short thats not the case on my baord.

[8BIT]

I had another small bug reported. The use of the /x override for an operand size was not working for forward referenced variables. It has been corrected and the new version is 1.3.3.5. It is attached here and on my website.

Thanks!

Daryl

[BigDumbDinosaur]

Excellent!

[8BIT]

In my haste to get the update published, I inadvertently left some troubleshooting code in the program. I won't affect assembly, other than changing 1 error message. However, I cleaned that up and have updated the files on my website. Version did not change - still 1.3.3.5

Here's a copy of the update as well.

Thanks!

Daryl

[BigDumbDinosaur]

8BIT wrote:

I have created a new option flag "SwapBin" which swaps the symbols % and @ functions. When added to the source, % will be the binary radix and @ will be the Modulo operator.

I mentioned this in the past, but will repeat it for anyone who missed it.

.opt swapbin (the option is not case-sensitive) affects the % operator in macros. % is used to select a macro parameter, e.g., %0, %1, etc. during expansion. If swapbin is declared, a parameter would be identified as @0, @1, etc. If you use the wrong operator in a macro, assembly will halt with a cryptic error, such as ERROR E041: Text expression not allowed.

[jdimeglio]

So um pretty much completed my monitor for my 65C02 using nothing but the Kowalski (Darly) good work. Thats guys.

[cjs]

Druzyek wrote:

Something like Chrome Remote Desktop might work for you. It works on at least some versions of Linux.

Chome Remote Desktop has worked reasonably well for me on Linux, the few times I've used it, but for remote desktop into my own Windows machines (as opposed to just connecting to a session to work with someone else) I've found rdesktop, a Linux RDP client, to be better.

[8BIT]

jdimeglio wrote:

So um pretty much completed my monitor for my 65C02 using nothing but the Kowalski (Darly) good work. Thats guys.

That's awesome. I'm glad you are finding it useful. I'll be releasing a minor update later this week. More to follow once its done.

Daryl

[Drass]

Hi Daryl,

I'm using the Kowalski emulator to write a test suite for the C74-100's 65816 features. It's all been working very well. Thank you.

In running through the opcodes, I did note that PHB and PLB are incorrectly documented as pushing and pulling the B accumulator. In fact the opcodes push and pull the Data Bank Register (DBR). Similarly, PHD and PLD are documented as operating on DBR when in fact they operate on the D register.

I'll let you know if I see anything else.

Cheers,
Drass