Staredit Network > Forums > Modding Assistance > Topic: Mods on Battle Chest Starcraft?
Mods on Battle Chest Starcraft?
Jan 6 2010, 11:39 am
By: Darkmega  

Jan 6 2010, 11:39 am Darkmega Post #1



Apologies if this is in the wrong section cause I know this is a mod MAKING area but it's also a helping area about mods so please hear me out:

My friend go the Starcraft Battle chest set just this morning and we were playing it together it worked perfectly on normal 1.152 versions. Then he wanted to play some mods because I caught his attention to them, but when we managed to use the downgrader (which works perfectly with my SC and still to this day allows me to play my mods from ages ago) and "play" them (double click on the mods EXE icons) we kept getting an annoying error about some sort of disk read fail.

Would someone know of anyone else who has mod playing failures with the battle chest version of Starcraft?
Cause I suspect an anti-downgrade something or rather or an anti-mod something of rather... Although he does run on vista, but another friend who I lent the game too could play mods on vista regardless but I have the original separated CDs of SC and SC:BW so I suspect it's something to do with the starcraft Bchest itself... Could someone shed some light on me and this subject or has no-one actually come across something of this sort before?



None.

Jan 6 2010, 12:58 pm Magicide Post #2

Sleeping wolves wake hungry.

The so-called Battlechest edition is just both the game and the expansion in one pack, there's nothing else added.

Also, Vista doesn't like mods. I had to disable DEP to make them work.




Jan 6 2010, 1:53 pm Darkmega Post #3



DEP? explain please.
I'm slow with abbreviations...then explain why they are chosing not to work for him while my other vistafied friends mods worked just perfectly? or is it just simply his computer doesn't like the mods or is being annoying about it? ...or perhaps we need to disable something?



None.

Jan 6 2010, 2:46 pm Symmetry Post #4

Dungeon Master

Quote from Darkmega
we kept getting an annoying error about some sort of disk read fail.

Older versions of StarCraft don't support the no-cd feature, so if you downloaded the battle chest off of Blizzard's online store, that'd explain it. Use the BWAIDowngrader here to get around this. It has its own no-cd crack.



:voy: :jaff: :voy: :jaff:

Jan 6 2010, 11:13 pm Darkmega Post #5



....eh whut? he bought it from ebgames... ok, I'll try that thing then...

EDIT: Never mind sirs! looks like we must've been using a corruptified downgrader or something :><:
cause when we used the BWAIdowngrader and replaced the old downgrader we were using it worked fine.

Post has been edited 2 time(s), last time on Jan 7 2010, 1:19 am by Darkmega.



None.

Jan 7 2010, 6:08 am ShadowFlare Post #6



Quote from Magicide
The so-called Battlechest edition is just both the game and the expansion in one pack, there's nothing else added.

Also, Vista doesn't like mods. I had to disable DEP to make them work.
Data Execution Prevention (DEP) should not cause any problems with it if you aren't using an old version of MPQDraft. Other than that MPQDraft version, other mod loaders should be DEP-compatible that are for StarCraft versions that are DEP-compatible.

By the way, there is generally no reason to fully disable Data Execution Prevention. The default mode only runs programs with it enabled when the developer of the program marked the program as compatible.

It is very easy for a program to be made compatible with it. All that needs to be done is to make sure that any executable code that is written to memory by the program is put into memory that the program has marked as executable.

Post has been edited 1 time(s), last time on Jan 7 2010, 6:14 am by ShadowFlare.



None.

Options
  Back to forum
Please log in to reply to this topic or to report it.
Members in this topic: None.
[03:29 am]
DarkenedFantasies -- Probably just didn't care. For example, at some point before release, they've updated the graphics of some of the Protoss buildings (Forge, CyberCore, Citadel, Observatory, Arbiter Tribunal), but instead of properly re-rendering them with edited 3D models, they did crappy copy-paste jobs on the rendered graphics.
[08:35 pm]
Ultraviolet -- :wob:
[2026-6-21. : 11:38 pm]
Symmetry -- :wob:
[2026-6-21. : 4:56 am]
Ultraviolet -- I suppose we'll likely never know, but my guess would be that they already saw it operating successfully and there was no monetary incentive to finish the original work. And the dev cycle in old school Blizzard was so hectic, it's possible it just got forgotten about after the original game got released. Plus there's an element of existing MPQ files that were packaged with the original discs becoming outdated if they updated it. And it's not like they remade the original MPQs, they just made new ones for BW specifically
[2026-6-21. : 4:26 am]
Oh_Man -- so that makes me think maybe the theory they are unfinished is not true and its a deliberate design decision, coz why not finish them wen ur making brood war?
[2026-6-21. : 4:25 am]
Oh_Man -- the thing is thos buildings are from classic. that means they went ahead and made brood war without ever finishing the 'unfinished' buildings
[2026-6-20. : 6:15 pm]
Ultraviolet -- Yeah he's talked about a lot of that stuff in his casts before. It seems plausible. Especially knowing how Blizzard of yesteryear operated.
[2026-6-20. : 3:47 pm]
NudeRaider -- to clarify: couldn't recall the behavior for every single Protoss building but I was aware the disparity exists.
[2026-6-20. : 3:43 pm]
NudeRaider -- Contained nothing new for me. Didn't know all building's behavior, but very much all unit's. Also Terran balance whine - also nothing new :lol:
[2026-6-19. : 9:57 am]
Oh_Man -- makes me wonder if SEN knows anything about the topic
Please log in to shout.


Members Online: jy2413804