Jump to content

yock1960

Members
  • Posts

    19
  • Joined

  • Last visited

  • Days Won

    1

yock1960 last won the day on November 17 2021

yock1960 had the most liked content!

Recent Profile Visitors

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

yock1960's Achievements

Apprentice

Apprentice (3/14)

One Year In Dedicated One Month Later Collaborator Rare Reacting Well

Recent Badges

13

Reputation

  1. I can get 800 euros for my 1581? I'll have to let my kids know for when I 'check out'. With prices for retro gear being so inflated now, I won't get rid of any more of my retro gear. Sadly, I didn't realize that I would live to see the day when this stuff would be collectible! Best I recollect, I...got rid of my original 1581 last century some time, then bought a drive-less case and popped in a compatible floppy in it when I went retro in the early oughts. As a matter of fact, I just dug it out to hook up to my modded Hummer-DTV today; still works!
  2. Here is a test program that demonstrates an apparent issue with calculations, that I can't figure out. I have no problem in another program, but this clearly is not working here. There is also a difference between these calculations using uwords & ubytes in some cases and in using a literal (8) instead of a variable defined as 8 here. testp8.p8
  3. Use case is arrays of 320 & 256 of floating point values that I pre-calculate for 'speed' for the madelbrot & julia set calculations. It's not a huge deal and as you say, I could rip the assembly code from my assembly program. A more serious issue is one I'm wrestling with now that I just can't get my hands around! I have a couple of lines of text that I popup at the top of the fractal dsiplay, the hires text printing that I adapted from a Youtube channel, has two variables that track x&y , much like printing from basic. You can change them to relocate, like print@, newline etc.. With the hires text printing that you include, they need x&y positions, so I am attempting to keep track in variables...only I keep getting bad results. See the attached screenshot, where I have built a test program to try and figure things out, but am not making much headway, since I don't understand the results!
  4. Yeah, I guess many people are using CC65, but as it doesn't natively support floating point (last I checked), I've never considered using it. Syntax is similar to many high level languages, so no issues there, other than what I personally would have with anything else...speaking as a non formally trained programmer. Other than my own bone-headed errors, I'm satisfied with my progress in porting the fractal program as a 'learning Prog8' task. Doing that program in assembly, which was a learning task in itself, took 4 months, albeit switching from the framebuffer routines, in order to use the entire screen, added some extra time at the end. This should go much faster. So far, the only thing that has caused me any heartache, is the limit on array size, which I worked around, by using multiple arrays...but it's a bit ugly. I could probably do an inline assembly routine....maybe...haven't thought about it too much...it's not a time critical part of the program and I'm trying to do as much as possible in Prog8 anyway. I would be happy if compiling generated the assembly listing from 64tass....a little thing...but it would keep me from having to load/assemble the .asm file again in order to get it. This will do a nice job as a replacement for Slang, which I used to do some BASIC porting for the C64 and CX16 back in early 2020, but floating point was broken for the CX16. More feedback as it occurs to me!
  5. I think this must be a similar issue....and very strange, since as I say, my assembly code works as expected and I essentially inlined that code into the Prog8 source. I've added some 'unnecessary' instructions and have at least gotten it to react to button presses, but the x&y positions returned are garbage.
  6. Is there anything different going on 'under the hood' as far as the mouse is concerned? As part of learning to code in Prog8, I've been working on porting my fractal explorer from assembly, but I just can't seem to be able to read the mouse buttons. I've got the assembly version working under R39 & Box16, so I know the code works...but even inlining it refuses to work from Prog8. I'm out of ideas!
  7. So, just dipping my toes into the water, writing the ubiquitous Hello World program, but outputting to 640x480x4 hires mode. I can see that I'm going to need to print out Borgar's code to get more example code to peruse, this in addition to the Prog8 manual and various library sources. After a few errors, I got the program working, but I have a warning that, while it doesn't hurt anything, I have no clue how to properly code: keyp = c64.GETIN() to avoid the warning. Also, I'd like to use, I guess cx16.enter_basic() to gracefully exit the program, but don't know how to pass...and what to pass...@Pc! Oh and in the GFX2 source for the text() sub, you may want to note that the screen code 'string' requires a terminating null....seems obvious....but to an even ranker novice than I...
  8. I know that an IDE for Prog8 is being worked on, but for the time being, if anyone is interested, Relaunch64 works, except that you need to name your source files .asm and add the -out /dir command option to the 'run' script, to send the output files to another directory to prevent your source from being overwritten. I had hoped there was a way to open any text file, but it's limited to .asm only. One could modify the source to allow this, but that's beyond me currently. A really talented and determined individual could even create additional Quick Reference tabs specific to the CX16, to add to the nice ones that already exist for the C64!
  9. By the way....this emulator looks way cool.....even if I don't know how to use all the extra goodies yet!
  10. Well, what I meant was to figure out what it was...which I did, downloaded the redistributable on the desktop and was rewarded with the clean white screen. Intel graphics incompatibility I guess, but it's working on one machine anyway!
  11. Well...I didn't know that! So, this 'fancy' gaming laptop that I bought years ago, that has Nvidia graphics...apparently doesn't always use it....but you can force it to...and so now the emulator looks as it should, yay! Thanks everyone!
  12. So, the laptop that I originally tried this on is an oem Windows 10, with Nvidia graphics...white screen window, with title bar, etc.. Next tried a Win7 laptop with on chip Intel graphic and then a self built desktop upgraded from Win7 to Win10 with on chip Intel graphics. Both of these machines failed to open the application, giving a 'can't proceed because VCRUNTIME140_1.dll was not found'. Guess I'll try and run this .dll down.
  13. Well, I've downloaded the emulator and rom, but it must not be meant for me to use it. It opens a window....white and empty. Apparently there is something I don't understand about this.
  14. Yes well, after some difficulties with multiple versions of Java, SET-ing environment variables was not quite the thing. I can compile now, but lacking an r39 emulator, I can't do what I'd like to, as it requires floating point. No, I'm not going to build my own, this 'limbo' r39 issue has caused me and likely others too, a fair bit of aggravation....but not enough to figure out how to use another tool set that I will never use again! They should post version 39, how long has it been? There are plenty more numbers after that....40,41,42.....
×
×
  • Create New...

Important Information

Please review our Terms of Use