andym00

Wow, interesting.. Six five oh two. Six five eight one six.. Sixty eight K.. Sixty eight oh ten.. Sixty eight oh twenty.. Eighty eighty.. Eighty eighty eight Eight oh three eight six.. Zed eighty.. I think my rules are simple enough

No idea what you 2 are doing but the WMA samples from Jacobus play just fine.. I think you're just expecting something more raucous than it actually is..

That's perhaps the most utterly appalling rendition of Wizball I've ever heard in my years...

I was under the impression that Warner Bros. Entertainment now own all the Atari Games IP since 2009 ? http://www.sec.gov/Archives/edgar/data/1022080/000095012309009497/c51466exv2w1.htm Not that it's relevant to this thread (null)

Glad you mentioned that, because that explains why PAL artifacts didn't appear to work for me.. Forgot I still had VBXE enabled from some tinkerings

Personally I like something a little more luxurious than a 30+ year old basic, but then I'm probably a bit weird I prefer to have all the data massaging as project(s) inside my solution, of which the main 6502 project has dependencies upon the other projects, which themselves have dependencies upon the raw source data, whatever that is.. Same thing for any magic tables.. Simply press one button and if needed whatever tools are rebuilt, run, and the final target data built from whatever source data, and then the final project built using the fresh and always up to date data..

I recall there was some mention on the IDE thread about some option added to do only one instance, but I'm not mad about that way of doing things to be honest.. As for VS, I've never seen any option to not tear down the processes created by starting a debug session, but I could be wrong as it's not something I've ever wanted to not do.. I'm perfectly happy now anyway.. I can now export my breakpoints to a file and have the command line breakpoints constructed as part of the build process so it's as automagic as I want now, well from the point of being able to have breakpoints inserted each session anyway.. edit: Oh crikey! And as luck would have it I've just found the .batch command in the debugger, so I guess that's everything I was looking for really when combined with the /debugcmd option.. So now all you need is to do /debugcmd ".batch debuggercommands.txt" and bob's your sisters brother.. Bingo.. Phaeron really has thought of everything

I guess my problem is that I'm being super lazy and using Visual Studio, so I press F5 it fires up Altirra, and when I rebuild or end debugging it simply tears down all the processes created by the debugging session, so I'm not running a persistent Altirra session over builds, which would be the answer then I'd only need to set things once per session.. I just like a nice environment that's as consistent as possible for my simple brain That said... I just was about to start adding something to Altirra to do what I want, when I found this in the command line processing code, which isn't mentioned in the help output on the command line.. while(cmdLine.FindAndRemoveSwitch(L"debugcmd", arg)) { debugMode = true; debugModeSuspend = true; dbg->QueueCommand(VDTextWToA(arg).c_str(), false); } So, I can add debugger commands to the command line via /debugcmd "bp LabelName" for example.. Which is almost exactly what I wanted.. Now to write a utility match the export symbols to line numbers and then I can integrate the VS breakpoints directly into my build cycle, and just use F9 to enable/disable breakpoints

Is there any chance of having some way to set breakpoints from the command line or maybe, like Vice, a set of monitor commands that are loaded before execution begins although after any symbol file is loaded ? The /debug and /debugbreak command line options are really handy, but things can get a bit tedious having to re-enter the breakpoints..

How about a macro to add all the VBXE addresses to a relocation list ? And then patch them at run time ? !macro VBXE .VBXERegister { .codePC = * * = VBXERelocationTableTop !word .codePC VBXERelocationTableTop = * * = .codePC !word .VBXERegister-VBXEBase } And somewhere at the end of the image terminate the list.. Obviously, it's not ideal since you need to have enough space allocated for the storage of the relocation table, but that just needs a warning of doom when it runs out of space at assembly time.. That's if your assembler doesn't support relocation tables, in which case I'd just define the VBXE registers as externals, and then patch as you would when doing your late binding..

Cool, so it is as straight forward as I thought then.. Just wanted to support everything that was possible since the debugger is getting a lot of use here..

Any chance that someone has a file that demonstrates the full use of the Altirra label files ? I want to quickly add proper Altirra label output to Acme 0.93 whilst I'm changing some other things in it today, and so far I've added CC65 label support for now, but would like to add proper Altirra label file support since it seems there's all manner of groups, RWE flags and other goodies lurking in the specification..

I must admit, I would kill for a PAL60 (well, essentially an overclocked CPU) mode purely for development purposes.. A lot of the time I code using NTSC just because it's a smoother ride under emulation (null)

Mine arrived this morning all safe and sound though had received a good squishing somewhere along the line.. All in good shape though Looks fantastic though with the box and everything.. Very professional.. Thanks a lot for this, for this run, for such an awesome product and the rapid rate of knots it made it here given the time of year..

It's in the menus.. "System->Pause When Inactive" is what you want..

I look forward to his first game actually.. At least he's doing something about it..

Apparently mine is desperate to spend Christmas with me as well (null)

Those aren't entirely unstable.. http://sourceforge.net/tracker/index.php?func=detail&aid=3334602&group_id=223021&atid=1057617

I think that honour goes to the 8051 which has shipped several billion units since it came out in 1980. Surely ARM gets that with their January 2011 report that they'd shipped 15 Billion processors.. Which is a staggering number quite frankly!

$2A years old, and my field is in a place called Higher Denham, just west of London in the UK It's a nice field with tasty grass

lol, couldn't have put it better myself

On the c64 the screen has to scroll in 2 pixel (one multicolour pixel) steps anyway otherwise the background layer would judder by one (hires) pixel each move.. When you're walking in those games, the screen is scrolling at a rate of one multicolour clock per frame, therefore the background layer done through charset switching is only really moving every 2 frames, but in fact the charset is changing every frame.. If you see what I mean The A8 will be exactly the same as the 64 in this regard..

Deleted.. Stupid ipboard app on phone!!

Draw the stars in software after the sprites, and only if the whole byte or character is zero.. Restore it later.. You really won't notice the stars aren't properly clipped.. Take a look at any of the msx nemesis games to see it in action, plus byte aligned sprites (null)

Off the top of my head on the 64 I remember this one in particular.. Sure it's been improved upon since 1989 http://noname.c64.or...lease/?id=32951