Jump to content

TomXP411

Members
  • Content Count

    475
  • Joined

  • Last visited

  • Days Won

    17

TomXP411 last won the day on March 31

TomXP411 had the most liked content!

Community Reputation

357 Excellent

3 Followers

Recent Profile Visitors

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

  1. I recently just found old Pentium II PC at a yard sale, so I may be looking for an ISA sound card real soon. I haven't taken the time to really start working on this thing, though.
  2. Right, the issue is that the VERA registers are read only. So when you read data back from the locations used for things like the palette, what you are actually reading is the RAM at those same locations. Once you have written your own palette data there, it's easy enough to read it back, but remember that you're always reading the cached information - not the actual register values. Having said all that... the palette is (or will be) documented in the VERA programmer's reference, so it should be possible to create a default state, so you can fall back to it. You'll have to create your initial palette by hand, but once you do, you can reload that at any time.
  3. You can do all of that you want; that's the beauty of having customizable character sets. Just create whatever character set you like and save it to disk, then load it with your program.
  4. Not exactly. There is some support in the kernel for choosing to load a file directly to VERA, but you have to invoke that function yourself. So the way to handle that would be to load your "loader" program, which would then load your assets into the correct places before starting the main part of your game.
  5. GPL requires you to GPL (or compatible) anything you create with GPL code. This is the primary distinction between GPL and things like the BSD or Apache license, which allow you to use those products to build software that is not necessarily open source. The requirement to GPL anything that includes or statically links to GPL code is why the GPL is often called a "viral" license... and so you can't mix GPL with more permissive licenses like the BSD license. On one hand, it forces companies like Red Hat to continue giving away their Linux distros for free... on the other hand, it makes it difficult to use open source bits of code in commercial programs. So if I make a BSD licensed audio program, and I want to use something like LAME to encode the audio to MP3, I can't without adding the GPL's restrictions to my product.
  6. @Michael Steil I just found this article about a bug fix to BASIC 2 regarding temporary strings of 3 characters. Is this present in Commander BASIC, and is the same fix necessary? https://c65gs.blogspot.com/2021/03/guest-post-from-bitshifter-fixing.html?fbclid=IwAR15E_DWVjfHab1Ehs_8GUIYKQJ4UjfbGjhPao8SKr9AUlYmBUY83FcHvtY
  7. Yeah, that's one of those things that you don't bother buying "just because", but when you find you actually need one, it's impossible to live without.
  8. No way. WordPerfect 5.1 was the best in the series. It was 6 that started the downward spiral...
  9. Sure, I happened to have a Brother label maker that I bought a couple of years ago for a network install; I picked up some transparent label tape and just printed out the labels. The P-Touch has a fairly large selection of symbols, including tape transport controls (the <<, >>, and >| symbols) and the speaker icon. The Volume up and Volume down are just a speaker icon followed by an arrow - so two separate symbols for each. The print you see there is a 12 point font; while I think that was about the right size for the icons, it's too large for the text. I may peel those off and replace them with the next size down - I think it's 9pt on this machine. Links: Brother P-Touch Black on clear label tape As a side note: the Brother works well, but it can be a little limited if you're doing sophisticated stuff, like keyboard glyphs. There are some USB label printers that should let you print graphics. Those are worth looking at if you really want to do a keyboard up right. I'd also suggest some sort of jig to allow you to more precisely place the labels. Mine are all over the place (as you can tell), and I definitely want to re-do them to make them more consistent.
  10. Here is what my labels look like. Ignore the off center application... my hands aren’t very steady right now.
  11. Thanks for the tip. I just grabbed all the .bin files in the build directory. I figure they were only a few KB, so it didn't hurt either way.
  12. Yeah, while the symbol tables aren't used by the emulator, they are useful. My menu program works by printing the LOAD command to the screen and stuffing CR into the keyboard buffer. So I looked that up in the symbol table... So it's super useful to know where KERNAL and BASIC variables are located. I was actually going to include them, but forgot and didn't want to spin my Linux VM back up.
  13. Good news... the new KERNAL fixes the load bug. Programs loaded with ,8 now properly start at $0801, no matter what address is at the beginning of the file, and programs loaded with ,8,1 properly load to the original address in the beginning of the file. I have confirmed it with a program saved from the Commodore 128, which has a different start of BASIC address. This is in the new Proto 2 KERNAL that Michael announced on Friday, here: Someone also added BIN$ and HEX$ functions, to print binary and hexadecimal values: super convenient.
  14. Windows version is WORKING. I compiled the executable with the help of Steven's GitHub project file for Visual Studio 2019, and I built the ROMs on Linux. Here's a Zip with the executable and ROMs in it. This should tide Windows users over until the weekend. x16emu-2021-03-29.zip
  15. I will check. I probably didn't install CLANG since I do mostly c# development. ** yeah, I had to dig into the Optional Components to explicitly install it. I'm doing that now. I also managed to get the Linux version and the ROMs to compile, so I'm just working on a Windows executable.
×
×
  • Create New...

Important Information

Please review our Terms of Use