Invalid projector file message
Ian Lewis
I have to start by admitting that I known very little about director.
I have a program, produced by a third party, that executes with no
problems. However, when I append some data to the end of this
executable and I then excecute it, a message box with the caption
"Director Player 6.0" and message "Invalid projector file: c:\fred.exe"
is displayed. The program terminates when I click on the OK button.
I am executing on Windows 95 (Version 4.0.950 C).
Can anyone tell me why I get this error when I append data to the end of
the original executable?
I want to append data to the end of this executable without it producing
errors, can anyone tell me how I can do this?
Thanks.
rsingh
> However, when I append some data to the end of this
> executable and I then excecute it, a message box with the caption
> "Director Player 6.0" and message "Invalid projector file:
My guess is the following. Since Director is NOT a compiler it most
likely is taking a playback engine and adding the data file that
contains the images,code,sounds,... of the movie to the end of the exe.
When you add the other data it thinks this is part of the movie data and
therefore unrecognized.
Ravi Singh
RavWare
Ian Lewis
That explains the chunk of data that resides at the end of PE image. It
looks like the data is just appended onto the end of the file, which is just
what I want to do!
Do know anything about how the Player uses this data? and how I may be able
to append data without upsetting it?
Ian.
rsingh
My guess is this. Since , as you probably already now, the PE has an old
DOS header that starts the file and then the PE information, the win32
loader only pays attention to the file size in the PE Header. So MY
guess is that possibly Director attaches the data onto the file in
reverse so... the last byte may be the first byte of data it is
expecting. Try reading the header and subtract of the real file size
from the exe file size. If the file is in reverse you would want to
stick your data at the end of EXE and then append all the MacroMedia
data. The other possible thing is that they just CRC the EXE or all data
after the EXE in which case it is much harder. The other possibility you
might want to try is this. Make your data a custom resource of the EXE
file and then use win32 resource functions to retrieve the data. This is
not a trivial solution but you may be able to pull off what you need
doing this.
Ravi Singh
http://www.ravware.com