It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
lumin: You said, "There are "no-cd fixes" out there, but they're all 16-bit "cracks" and even if you can find one, it won't run on any modern system". As I said, this is just plain false. I'm running the game on 3 desktop computers and my Linux Mint Laptop without any Hellfire CD at all with the GOG Diablo. So don't bullshit with me.
avatar
CLBrown: You know, you've got a bit of attitude there.

Do you have a link to a "no-CD" fix which can be run on a 64-bit Windows system? If so, provide it here and now.

Every one I've seen is a 16-bit executable, which means it cannot run on a 64-bit system (except, perhaps, in a virtual machine).

You say "I have it." Fine. Explain how. It's EASY to say "well, I did it, so stop bullshitting me." It's a lot harder to actually make a POSITIVE statement, about how you did it.

C'mon. Give up the details. Or I'm "calling bullshit" on you. Because I KNOW that every single "no-CD fix" I've seen has been coded in 16-bit, and that means it cannot be run on a 64-bit Windows OS.

And I KNOW that the CD check is hard-coded into the game executable, meaning you can't just "copy over files" to bypass this. You need to alter the EXE. If you've done it using a HEX editor, please tell us what data you altered, by address and by content (original versus updated).

Want to do any of that?
Sure will. I'm using the executable provided from Hellfire Enhanced.
https://www.moddb.com/mods/hellfire-enhanced/downloads/hellfire-enhanced-latest

This was linked in the sticky thread at the very top of this forum (which I already pointed out earlier), but don't tell anyone, it's a secret. I'm running it without the CD on my 64 bit Windows desktop PC, my 32 bit Windows PC, and my 64 bit Linux Mint Laptop.
Post edited April 05, 2019 by lumin
avatar
CLBrown: You know, you've got a bit of attitude there.

Do you have a link to a "no-CD" fix which can be run on a 64-bit Windows system? If so, provide it here and now.

Every one I've seen is a 16-bit executable, which means it cannot run on a 64-bit system (except, perhaps, in a virtual machine).

You say "I have it." Fine. Explain how. It's EASY to say "well, I did it, so stop bullshitting me." It's a lot harder to actually make a POSITIVE statement, about how you did it.

C'mon. Give up the details. Or I'm "calling bullshit" on you. Because I KNOW that every single "no-CD fix" I've seen has been coded in 16-bit, and that means it cannot be run on a 64-bit Windows OS.

And I KNOW that the CD check is hard-coded into the game executable, meaning you can't just "copy over files" to bypass this. You need to alter the EXE. If you've done it using a HEX editor, please tell us what data you altered, by address and by content (original versus updated).

Want to do any of that?
avatar
lumin: Sure will. I'm using the executable provided from Hellfire Enhanced.
https://www.moddb.com/mods/hellfire-enhanced/downloads/hellfire-enhanced-latest

This was linked in the sticky thread at the very top of this forum (which I already pointed out earlier), but don't tell anyone, it's a secret. I'm running it without the CD on my 64 bit Windows desktop PC, my 32 bit Windows PC, and my 64 bit Linux Mint Laptop.
So, you're not running "Hellfire." You are running a 3rd-party port of Hellfire.

Nothing wrong with 3rd-party ports... that's what GoG has given us with their "tweaked" version of Diablo.

But your "hellfire enhanced" is not "Hellfire."

That's sort of like claiming that running the "Dark Places" engine is the same as running retail Quake.
avatar
CLBrown: And I KNOW that the CD check is hard-coded into the game executable, meaning you can't just "copy over files" to bypass this. You need to alter the EXE. If you've done it using a HEX editor, please tell us what data you altered, by address and by content (original versus updated).
It's not in the .exe at all, it's in storm.dll.
For Hellfire you need to change the byte at offset 52177 from 0x75 to 0xEB.
avatar
lumin: Sure will. I'm using the executable provided from Hellfire Enhanced.
https://www.moddb.com/mods/hellfire-enhanced/downloads/hellfire-enhanced-latest

This was linked in the sticky thread at the very top of this forum (which I already pointed out earlier), but don't tell anyone, it's a secret. I'm running it without the CD on my 64 bit Windows desktop PC, my 32 bit Windows PC, and my 64 bit Linux Mint Laptop.
avatar
CLBrown: So, you're not running "Hellfire." You are running a 3rd-party port of Hellfire.

Nothing wrong with 3rd-party ports... that's what GoG has given us with their "tweaked" version of Diablo.

But your "hellfire enhanced" is not "Hellfire."

That's sort of like claiming that running the "Dark Places" engine is the same as running retail Quake.
Please, just stop. There's no shame in admitting you were wrong. I admitted I was wrong about the options. Saying that I'm not "really" playing Hellfire because I'm using a fix to bypass the disk is just silly. This is like saying I'm not really playing any older game on GOG because they have all been manipulated to run on modern operating systems correctly.
Damn, after reading through this thread, I kind of wish Acti-Blizz WOULD release Hellfire on here now.
avatar
CymTyr: Damn, after reading through this thread, I kind of wish Acti-Blizz WOULD release Hellfire on here now.
Its actually super simple to download and install Hellfire. Took me less than 10 minutes. Dont listen to the lying trolls above trying to obfuscate the process.

Follow the instructions on the sticky thread at the top of this forum.