Sierra's SCI System Scripts

[Collector]

Yeah, I was trying, too. I had thought about trying to see if I could set up a faux network share in DOSBox, but I have never played around with DOSBox and networking. I also don't know what kind of 'hand shaking' it might require. It would be nice if we had the source for the tools as well.

[lskovlun]

OK, you'll need an executable unpacker (I use http://unp.bencastricum.nl/) and a hex editor of your own choice.

First, unpack the file using unp (via DOSBox).
Then, for VE256.EXE: Using a hex editor, search for 75 13 B8 16 45, replace with EB 13 B8 16 45
For PE256.EXE: Search for 75 13 B8 88 23, replace with EB 13 B8 88 23.

I don't understand why the art programs enforce this; the compiler doesn't, and that would make more sense to me.

[MusicallyInspired]

Nice! Are those the only two tools that suffer from this problem/this method can work with?

[lskovlun]

Are those the only two that suffer from this?

Logically VE16 and PE16 (and VE and PE) do as well - but I don't think there are any non-art programs that do.

Also, I'd think something like MTEST would be more interesting to play with for you? it's a bit difficult to set up, but not protected like these are.

[MusicallyInspired]

I'm running through them bit by bit. I'll get to the sound ones soon.

I managed to open a picture finally. It seems the 256 tools are meant only for SCI1.0 resources. I couldn't get them to open SCI1.1 Views or Pictures. PE256 has a really neat feaure of overlaying control or priority lines on top of the bitmap image! Handy! I'm still trying to get VE256 to open anything, actually. Every SCI1.0 view I open it thinks each cel is corrupt, gives a message saying "blown", and then complains that the View is too large and needs to be split up. Maybe something to do with the way modern reverse engineered editors create them? (I was trying to view modified views I had made with Brian's old tools)

EDIT: I tried opening some original Views straight from a Sierra game and it works nicely. Must be something in how Brian's tools saved them that made this program complain. Interesting...sad that it doesn't support SCI1.1 resources, though.