Batronix USB EPROM programmer Windows 7 driver help?

[maxlords]

I thought I'd burn a couple EPROMS today, and I went to install my Batronix BX40 onto my Windows 7 64-bit system. Unfortunately, while the software installed, the hardware got a "failed to detect" on the drivers and they don't seem to want to install manually. Any help? I emailed Batronix....but if anyone has already done this...

[Womble]

Not specifically Batronix but if the driver isn't properly signed then Win 7x64 will not load it, and by default non functioning hardware gets hidden. You have to press one of the F keys at bootup to allow it to accept unsigned drivers and you have to do this everytime which is a PITA.

Assuming this is the 1st time you have tried to get it to work under 64 bit its probably the unsigned drivers at fault.

[maxlords]

Ugh...that sounds like a damnable hassle. Does it leave your puter vulnerable to allow that? I almost never reboot or turn my puter off....

[ZOM]

There's actually a little tool floating around the web that allows you to fake sign drivers for windows 7's test mode, which you can activate through the command prompt.
But I dunno if it's against forum rules to post it, so, I'm afraid no link for now mate - google is yer friend. Hope that helps.

[Ed Oscuro]

If you only use the ROM burner occasionally, it seems like it wouldn't be too big a hassle just to go through the motions only when you need that driver. Don't know if Win7 spits out anything nasty at you when it finds an evil unsigned driver, or just fails them quietly (i.e. no prompts to click through).

[maxlords]

Turns out that the box it came in is not the same model that I have...and the one I have is incompatible with 64-bit operating systems. *sigh*

Ah well. Guess it'll be up for sale soon!

[ZOM]

Don't know if Win7 spits out anything nasty at you when it finds an evil unsigned driver, or just fails them quietly (i.e. no prompts to click through).

Windows simply won't load the device driver at startup and it shows you a meager "driver was not successfully installed" message in the notification area. The only solution I know of, is to put Windows in driver test mode by the "Bcdedit.exe -set TESTSIGNING ON" command, which allows you to run drivers specifically signed for this test mode. Like mentioned before, this method needs a patcher for your unsigned sys files though...
...or download the Windows Driver Kit.(needs Windows Live ID)

Ah well. Guess it'll be up for sale soon!

Do you have a list of supported devices for that unit?


EDIT: found it on the net - it's just an EPROM prgrammer... I was looking for a more "universal" solution (EPROM, PIC, etc). Oh well.

[Ed Oscuro]

I just had a random thought:

Virtual PC (is free from Microsoft) -> Install virtual XP operating system -> install device there -> ???? -> RIP & BURN BAYBEE

Or not, I'm not sure how VPC treats products like this that require direct access and stuff.

Are you saying that they make a model whose drivers actually support x64, Maxlords?

[maxlords]

Yeah, they have a newer model that does support x64 architecture.

[ZOM]

Just got an Advantech Lab Tool-48 for cheap; it's a parallel port device and the software&drivers don't support win7 x64, ran it in Win XP mode (virtual pc), and works like a charm!