Recent content by ClassicHasClass

Thanks! I am always worried my one Portable PSU might blow.

Any current limiter you might recommend for this?

Hey, thank you, that's very helpful.

I'm going through the code in the extension and I see the string but not where it is checked. What offset in the code fragment did you see that at?

Did you talk to someone specific about that? I'm still getting stiffarmed and they owe me a lot more than $12.

It could be the shipper. UPS still owes me $600 in tariffs that they overcharged me (it was reduced down to $51, but they still haven't sent me the difference).

I actually like CodeWarrior and find it very productive to work in, but I respect your preferences. I may try to convert it anyway for my own use.

I see you mention CodeWarrior for the shlbs. Can this be built from scratch in CodeWarrior? Are there .mcps available? Thank you for posting it!

You mean like the Asante EN/SC? Works pretty well, considering.

Weird SCSI peripherals are the best, aren't they?

What a fascinating idea. I assume they were implemented as LUNs or something.

Will you be offering these libraries for use in other projects?

That means the loader could not allocate that much stack space to your process, so you get a null pointer. If this is the browser, it's likely because your code in memory is much bigger than TenFourFox's was (you get about 2GB total which must be split between your code pages, data pages and the...

If you don't do it, you'll get crashes in the browser trying to run any code of substance. The test suite will mostly run, but most of those are trivial. Because so many registers need to be saved in each stack frame and calls can be recursive, it's pretty much unavoidable.

Yes, it was a lot easier debugging it when I could run automated tests. The command line shell was massively faster at that. It won't catch every bug but it catches a lot. Be mindful of the fact that the JIT has monstrous stack requirements. There is specific code in the TenFourFox build system...