> Today I am filing:
> 1. A payment dispute with the email payment processor for the 7/29 transaction of $451.15
> 2. A complaint with the FTC and California Attorney General (retention of payment without delivery)
> 3. A small claims filing in San Francisco County for $451.15 plus costs
I wonder did their prompts include a fake location or have the models assumed that Silicon Valley is the center of the universe :)
The bottleneck was with the serial protocol between the drive and C64. It was done via bit banging in software due to some chip bug. The fastloaders replaced the protocol with something more amenable to bitbanging.
Quite safe in practice, even Nintendo games have had no issues. GTA 3 / Vice City decompilers did get sued though, but IIRC mainly because they did not comply with DMCA requests at all.
Yes, exact version of the original compiler is required.
Generally bit-for-bit equivalence to the original executable is expected. However I think for some cases where the original executable included debug info (eg. PS2 ELFs) then the unused-at-runtime sections need not match.
Even if it could, it would be ridiculously token inefficient to update huge amount of addresses instead when some small change is done to the middle of a binary
What does "long term memory" mean? It can write down notes from past/recent support requests? If so, that sounds like risk of one customer's data leaking to another.
Some stricter interpretations also require that maximum stack usage can be statically analyzed (ie. no recursion, no function pointers, no VLAs/alloca).