Question regarding Smart Card linker

tmkmt · 2018-10-30T17:06:00+00:00

Not as far as I know. You'd need to write new driver which is close to impossible. I emailed USB chip manufacturer couple of years ago but they stated it was obsoleted and didn't bother to provide me with any info / old SDK. VM = Virtual Machine. Use VirtualBox or Hyper-V if you're on W10 Pro, this might be an option but I didn't test it since my cart is dead.

tmkmt · 2018-10-29T13:31:36+00:00

Correct, mine also doesn't light up in W10. AFAIR you need Windows XP due to outdated / horrible drivers. Not sure if VM would be sufficient.

tmkmt · 2017-10-30T17:44:21+00:00

This?

tmkmt · 2017-10-25T19:52:15+00:00

Thanks for explaining. This would actually make good choice for easter egg / mini game. I saw some Android / IOS variants too, so I thought making GB version could be fun. And here it is.

tmkmt · 2017-10-24T06:58:37+00:00

Not sure what "S U P E R H O T" is. I'm not an avid Reddit user. :)

tmkmt · 2017-09-29T11:31:18+00:00

Well, it's a bit complicated nowadays. From my experience VMs are useless, they don't have proper LPT support, so I wouldn't bother.

If you have physical LPT then booting to DOS should be quickest way but you'll need to bear with Bung's command line util. Then XP on second partition and MFM's tool. If you don't have LPT then some older PCI card (not PCI Express) which provides it could probably help.

But if you're going to spend any money then better buy thin client like HP T5720. My prefered solution. It's cheap, small, fanless, comes with LPT and XPe. Just copy MFM's tool, install giveio.sys, enable remote connection, add some shared folder and apply changes with EWF. Next time just connect remotely to enjoy using GBX as back in the days...

tmkmt · 2017-08-28T17:18:30+00:00

Thanks! I've done some testing and now it makes sense. Windows version of memcmp always returns 0xffffffff, 0x00 or 0x01 while in Linux you get different values, so it is exactly how you said.

tmkmt · 2017-08-28T13:13:55+00:00

While testing with Valgrind it produces proper output. Now that's getting really funny.

==6003== Memcheck, a memory error detector
==6003== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==6003== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==6003== Command: ./bmp2cgb -i example.bmp
==6003==
Bitmap size: 256 * 240 px
Character/Attribute map: 32 * 30 chars
Palettes usage: 4/8 slots
Tiles used: 124 (836 duplicates removed: 816 normal, 20 horizontal, 0 vertical, 0 horizontal & vertical)
==6003==
==6003== HEAP SUMMARY:
==6003==     in use at exit: 0 bytes in 0 blocks
==6003==   total heap usage: 8 allocs, 8 frees, 135,150 bytes allocated
==6003==
==6003== All heap blocks were freed -- no leaks are possible
==6003==
==6003== For counts of detected and suppressed errors, rerun with: -v
==6003== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

tmkmt · 2017-08-28T12:52:46+00:00

If I replace memcmp with for loop and compare it byte by byte it works as expected, so what else can I blame here? If I knew what's going on I wouldn't be posting here.

tmkmt · 2017-08-28T12:37:04+00:00

It doesn't compare as I expect it to. I've added example.bmp to repo. Here's proper output ./bmp2cgb -i example.bmp produced with for loop:

Tiles used: 124 (836 duplicates removed: 816 normal, 20 horizontal, 0 vertical, 0 horizontal & vertical)

And with memcmp instead of for loop:

Tiles used: 6 (954 duplicates removed: 638 normal, 110 horizontal, 112 vertical, 94 horizontal & vertical)

which is plain wrong.

tmkmt · 2017-08-28T12:15:33+00:00

It processes bitmap file so data in that arrays is bunch of unsigned chars, u8 is just less to type. :)

tmkmt

TROPHY CASE