Chaito
Led Storm.
I have a stupid question... which programming languaje do you use for this???
Alchemist said:2Telecide:
AFAICS, you are trying to compile a source code which contains preprocessor directives without a preprocessor at all. No wonder that you get 'Undefined symbol' error and other unexpected behavior.
Download the preprocessor by the link I gave before.
Make p.bat with the following contetnts:
Code:@if not exist %1.ssl goto DONE @copy %1.ssl temp.c @wcc386 temp.c /pc /fo=temp.i /w4 @copy temp.i temp.ssl @compile temp.ssl @if not errorlevel == 0 goto ERROR @copy temp.int %1.int @del temp.c @del temp.i @del temp.ssl @del temp.int @goto DONE :ERROR @echo ERROR: %_CWDS%%1.ssl >> errors.log :DONE
And compile your scripts like this (note filename WITHOUT SSL extention):Code:p.bat perksperlevel
My example assumes that all binaries and source code a located in the same directory. So may want to change pathnames in the batch file suitable to your project's structure.
Nirran said:ok then the problem is probably the version of sfall your using,download sfall from timeslip page and be sure to copy over all the settings in ddraw.ini in the one restoration installed to the new one should fix it
Telecide said:Nirran said:ok then the problem is probably the version of sfall your using,download sfall from timeslip page and be sure to copy over all the settings in ddraw.ini in the one restoration installed to the new one should fix it
I tried comparing the ddraw.dll in the restoration project with the one that comes with sfall. I can't find any differences that seem like they would effect the scripts, but I'll try just replacing the file and see if that works.
Nirran said:Telecide said:Nirran said:ok then the problem is probably the version of sfall your using,download sfall from timeslip page and be sure to copy over all the settings in ddraw.ini in the one restoration installed to the new one should fix it
I tried comparing the ddraw.dll in the restoration project with the one that comes with sfall. I can't find any differences that seem like they would effect the scripts, but I'll try just replacing the file and see if that works.
i assumed you had installed custom perks and level per perk scripts,if you did you should have had several perks to pick at level 1,from that assumption i figured the sfall version frp installed was outdated and that sfall did not recognize the add_perk commands,if not ignore my post,if my assumption is right it is probably why FO2 is crashing at start,as the scripts are trying to make new perks selectable and sfall doesn't recognize the commands
Telecide said:Nirran said:Telecide said:Nirran said:ok then the problem is probably the version of sfall your using,download sfall from timeslip page and be sure to copy over all the settings in ddraw.ini in the one restoration installed to the new one should fix it
I tried comparing the ddraw.dll in the restoration project with the one that comes with sfall. I can't find any differences that seem like they would effect the scripts, but I'll try just replacing the file and see if that works.
i assumed you had installed custom perks and level per perk scripts,if you did you should have had several perks to pick at level 1,from that assumption i figured the sfall version frp installed was outdated and that sfall did not recognize the add_perk commands,if not ignore my post,if my assumption is right it is probably why FO2 is crashing at start,as the scripts are trying to make new perks selectable and sfall doesn't recognize the commands
Ok NOW I understand. I wasn't actually looking at the dll file. I was looking at the ini file. Replacing the dll file DID work and now your two scripts seem to run perfectly. Thank you!
Now I'm just wondering if the newer ddraw.dll will be completely compatible with the restoration mod. Only one way to find out I guess.
Chaito said:I have a stupid question... which programming languaje do you use for this???
Alchemist said:I'm not sure, what version of the preprocessor you are using. This one definitely dose not require the extender.
If yours depends on DOS4GW, it's better to put Watcom's dos4gw.exe into one of the directories specified in the PATH variable rather to have it along with the compile.exe. DOS4G-based application loaders will find your extender automatically in this case. And there will be no need to mention DOS4GW in the batch file at all.
Jargo will be amused when he knows that you re-named Interplay's language after him. SSL stands for the StarTreck Scripting Language. Question was not stupid enough to give such a stupid answer.language is jargo
Well, Vista, especially 64-bit, is the worst choice to use obsolete DOS-based applications with.tried to run the compiler and preprocc in vista 64,to no avail heh