Anyone ever considered moving to Rhön-Grabfeld, Germany

So that you can have licence plates that starts with NES ?

No, but I did see a licence plate here the other day that said N64 GEX. I thought that was amusing.

Here in Rio a lot of license plates start with "L", so it's not uncommon to see opcodes like LDA, LDX, LDY, LSR and LAX. Some times the 4 numbers that follow don't make much sense with the opcode, but it's pretty cool when they do.

Personally I'd like something like this instead of "NES"... I like the fact that opcodes are more subtle and not everyone will get the reference.

Shades of a Wii hacker's STRNCMP?

One of the CDs I use at work has the disc length 65:02.

And last Saturday, I used the copier at work and my copy jobs were batch #s 6581 and 6582. =-DDDDDD

Funny.


Haha, very cool indeed !


Well almost nobody would get the reference I think... at least with NES some people would get it.

Also in that particular region of Germany, you are 100% guaranteed to have "NES". For you it sounds like you'd need luck to get LDA, LDX, etc... Unless you can choose (at least partially) your plate number.

It seems in Germany after the region code there is 1 or 2 letters, then a number. So you could use 2 letters and do publicity for a particular NES game (if they allow you to choose the number, I have no idea if they do). For example : NES-VN to make publicity for Castlevania III or NES-XR to make publicity for Mega Man 2. That'd be very cool. Also I bet some people in this region does publicity for NES game without even knowing it. If someone ever got to this place it'd be nice to share.


strncmp() is a standard C function, nothing much to do with the Wii or any other system.
It's strange there is number plate with only letters. Here in Switzerland it's the opposite, it's only numbers (except the region code 2 letters). Pretty boring.
I could get '6502' but unfortunately they ask 2000 Swiss francs if you want a number below 10k (they are normally reserved for trucks and taxis).

65C02 is greater than 10k if you consider it as HEX...

It's the name of the standard library function that was mistakenly used in the first version of the Wii system software's digital signature verification. This "Trucha bug" allowed homebrew developers to sign anything so long as the first byte of the resulting hash value was $00, which takes a few hundred passes of automated trial and error. Wii system software 3.3 switched to the correct memcmp for discs, and 3.4 switched for all executables.


In USA most states offer completely personalized "vanity plates" at a modest additional price.

As as said, in Switzerland you get only numbers, no letters. And the automobile service doesn't consider numbers in HEX anyway.


Well that's pretty cool actually, but I think only letters is really weird. It's easy to display messages, and that's not the role of an immatriculation place. I prefer greffing subliminal messages on existing systems

In my canton (swiss equivalent of an US sate) you can choose any free number between 10000 and 599999 for a little extra, but as I said if you want between 1 and 9999 you'll have to pay a huge extra which is really ridiculous.

Cantons are free to assign numbers as they want, so in other cantons it might be different. The closest I could do in Switzerland is move to Neuchatêl and have a number which start in 5, so that it looks like an S. For example I could have NE 56502. Unfortunately the spacing ruints it all

Hate the 68000?

I had couple fun coincidences. One time I made a chiptune in Fast Tracker that when saved, turned out to be 6,502 bytes. And yeah, it used all NES-style instruments. I later re-did it in Nerdtracker, not that it was anything special to listen to. Also one of my early NES projects, Roadkill, later on I had rewritten big parts of it and added music, on the date 6-5-02 (yeah it's US date format, but still).

I was thinking of getting a vanity plate that said "LDA 4016". Completely innocuous, looks exactly like the plates around here, but is pretty important when you're talking about the NES.

On the subject of vanity plates, you can choose 7 alphanumeric characters, and add one space or hyphen (because it's half the width of a character). In addition, most states have a selection of background pictures/designs you can choose from, and each state has their own overall style and "default" plate, and they're all unique, so it's always clear where someone's from.

There's an apartment building that I used to drive by every day that has an address of 6502. Coincidentally, I drove by it this morning for the first time in a few years.

Bender has a 6502 for a brain. Almost died when that reference came up.

Wouldn't it be a little extreme moving there just for a license plate? Why not just import a novelty one?




What in the world is LAX???...Did some searching and found this:

"LAX - This opcode loads both the accumulator and the X register with the contents
of a memory location."

So, I'm assuming it looks something like this example:


I've seen weird ones like BLT which is = BCC. And ADD, which is = CLC then an ADC (immediate value). Nice to add another mnemonic to my vocabulary (even though it's illegal with ASM6). Thanks.

--ShaneM

LAX $address is equivalent to running LDA $address and LDX $address at the exact same time. So it's still three bytes, still takes four cycles, but affects both registers.

Cool. Thanks for the list.

ShaneM

What would have been really useful is having an LAY. I could have definitely used that when I recreated Hard Mode in my SMB1 SRAM hack to check for set flags (within "inithardmode", my custom subroutine). I don't see that on the list. Even if it were there, ASM6 probably wouldn't assemble the binary output properly. --ShaneM

Jurisdictions requiring number plates on both the front and back of a vehicle, such as the U.S. state of Ohio, ban novelty plates.


Not the sandwich.


That depends on what macro pack you have installed. Or does ASM6 not have macros?

@tepples

The only assembler that I've used ADD and BLT for were my SMB3 assembler, which came with the disassembly by CaptainSouthBird. I think the included assembler was called NoDice(?). ASM6 (which I use for my FDS SMB series hacking) does not support those invalid instructions. ShaneM

asm6 does support macros (MACRO and ENDM statements; please see the readme), but you can't easily do this with macros in asm6 because the "assembler opcode" LAX can support multiple addressing schemes, which the assembler doesn't know how to handle/decode simply based on what you pass it:


But nothing stops you from using them manually using .db statements, e.g.


I don't know if you can do .db $bf, $0971. I'm thinking endianness might be incorrect in this situation (resulting machine code might be $bf 09 71 rather than $bf 71 09), but haven't tested.

And screw anyone using unofficial opcodes. But everyone already knows my stance on this. :)

.db is a single byte, .dw is for two bytes and .dbw is three bytes. So it'll need to be: .dbw $bf, $71, $09, since ROM addressing is assembled in Little-Endian. But good point. The question is, will it run? I've already finished my hack, but if I ever find more unknown original glitches (so far, I fixed em' all), I'll definitely give these a whirl! --ShaneM

However, macros in ca65 can examine the token list to determine which addressing mode was intended. See this done for 6502 (as a proof of concept) and SPC700.

I think the answer to this depends on what emulator is being used. Some may support invalid/supernumerary opcodes while others may not. Whether the NES/FDS officially supports these are a mystery to me.

The documentation for asm6 that I have doesn't mention anything about a .dbw pseudo-op. I believe you're thinking of .dcw (more appropriately known as .dw), which you WOULD NOT use here. Quoting the manual:

.dw will generate a word (16-bit) value, so .dw $bf, $71, $09 would actually "generate" the following values: $00bf, $0071, $0009, which would get stored in the file as $bf 00 71 00 09 00 (due to the 6502 being little-endian). This isn't what you want, and would result in some very broken code. Think about how those values would get turned into opcodes:

An opcode is a single byte value, while the operand for opcode $bf would be a 16-bit address. The other addressing modes for LAX vary as well. I described this already though.

My point was that I don't know how .db will react if you give it a word (16-bit) value. I suppose I can find out easily enough.

Maybe I should redownload the ASM6 package. I've had that thing for so long and I didn't realize that it came with instructions. I actually mixed up .dbw with RGBDS, my Z80 assembler.

EDIT: Or, you could do:

...and that's already what I said above, other than the .dw value being reversed in your example (in your code you write it "how you want it", what gets written to the file / stored in memory is "reversed" because that's how little-endian works). So we've come full circle now, and why did I just spend an hour doing this? :P Haha

Or just the obvious one:


Of course it's likely that $0971 is a label instead, so the .db .dw method is actually better in that case. Or you could just make a macro that takes two parameters and does it for you, so you don't need to be spending two lines every time you want to use the opcode.

NES/Famicom supports the unofficial opcodes just fine. CopyNES has used them for ages. My game STREEMERZ also uses them, and I haven't heard a single complaint about it not being able to run on any system.

Not only the licence plates, but the official codename for this whole district is "NES".

The licence plates are just the most visible part of it. Since I don't live in Germany I don't know how much those region codes are used in daily lives outside of licence plates, but someone german could give more details.


Well, I didn't know that existed. It is of course not legal to drive with unoficial plates installed, but as long as your car keeps parked in front of the house in a private parking slot I'd belive this would be legal. But in this case, the car itself becomes useless so I'd be more optimal to paste the plate directly on the front door of the house or something.

Unofficial plates are for places like Indiana that issue only one official plate, not two. The official plate goes on the back of the vehicle and the unofficial plate goes on the front.

Mmh, interesting. But then, moving to Indiana one of the USA states that emits only back plates just to be allowed to have a fake german plate in the front of your car is just as extreme as moving to Germany to have real german plates.

Indiana isn't the only U.S. state not to use front license plates.

This is getting totally out of topic, but who cares. I wonder.

I'd guess in the states where they only issue back plates, they have to adapt speed control radar, to contain two photographs units to flash in both directions, in order to catch cars that breaks the limit driving in both directions. But then, the states that emits 2 plates have normal radar units observing only one direction.

Then if someone from a state that issue 2 plates drives in a state that issue just 1, if he's catched from the front side, the picture would show no plate, or even worse, a (legal) fake plate correct ? How can this not cause some problems ?

Kentucky, too. Since we are neighbors.

The local school zone speed limit enforcement cameras take pictures of both the front and back of the car, even though Washington (the state!) law requires 2 license plates.


I think this is why all of the cameras take pictures of both sides of the car.

This thread was already pretty random and off-topic from the start...

I can touch my nose with my tongue.