Hellfire critical error @ startup.
#7
The original error message comes from storm.dll!SMemAlloc when an allocation request cannot be satisfied. Most likely, Hellfire was misreading your modified MPQ and trying to request an excessively large chunk of memory. The D:\ was the path to the source file which called SMemAlloc. That is, whoever build Hellfire had the source to it on their D: drive.:)

Interesting that Diablo is not SMP/SMT safe, but not really surprising given how rare SMP was when Diablo came out. Note that affinity is inherited, so you could change the affinity of some other process and then always use that process to create Diablo. Similarly, one could create a launcher that always launches Diablo with the correct affinity. Affinity is process metadata, and so is not checked by the current version checking procedure (which does tend to break any hacks which are applied pre-connect). Changing the affinity for Diablo makes it very unlikely that the crash will occur, but does not fix the underlying problem that caused it. An inopportune context switch could still cause Diablo to crash. The fact that you haven't seen any such crash says that you most likely never will. Just remember that it is still theoretically possible.:)
Reply


Messages In This Thread
Hellfire critical error @ startup. - by Belix - 02-11-2007, 04:34 AM
Hellfire critical error @ startup. - by Alamara - 02-11-2007, 04:55 AM
Hellfire critical error @ startup. - by Zamal - 02-11-2007, 08:59 AM
Hellfire critical error @ startup. - by Belix - 02-11-2007, 10:38 AM
Hellfire critical error @ startup. - by Thenryb - 02-11-2007, 06:44 PM
Hellfire critical error @ startup. - by Alamara - 02-11-2007, 07:09 PM
Hellfire critical error @ startup. - by [vL]Kp - 02-15-2007, 01:14 AM
Hellfire critical error @ startup. - by splatz - 03-29-2007, 08:31 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)