FLSHELL

@Xarian_Prime:

Check out M0tah’s posts history, in there there will be a link to the latest v1.6.3 on the forge… add a few plugins… and your more stable that ever… with only 1 extra proggy running… ;D

There’s obviously some misunderstanding about the different versions of FLHook, so I’ll try to clear it up.

As far as I know there’s currently two versions of FLHook that extend the functionality of v1.5.5 and that have had recent releases: the plugin version, developed by w0dk4, and '88 Flak’s version, developed by me. There is another version, the Leipzig City version, but it was released a while ago and doesn’t seem to be actively developed anymore.

My ('88 Flak’s) version has many more built-in features than the plugin version does, but it does not support plugins. I have ported some of the features from my version to plugins for the plugin version, but many of the features have not been ported. The latest release of the plugin version is v1.6.0 and the latest release of my version is v1.6.4.

sry m8… ;D haven’t actualy had a chance to play with the new one… then i woulda known about the plugins

in fact i haven’t played with the tech since i replaced w0dk4’s with yours… a few weeks ago… with 1.6.3… which looks real good ;D i must say… just been busy in other areas of coding heaven/hell…

Im not sure, but you may can try to Disable the Windows DEP if you enabled it.

I m not sure

• but as far as i remember,
  FlShell wants a ‘path’ to it’s own directory and to freelancer\exe.

And possibly the names of the directories are wanted
shorter than this one : “\PROGRA~1”.

Don’t know if you use CD. Otherwise you can think of using the msgboard.
Use it now for  a while and works fine

For FLShell the first things i can think of is this:

Did you put it on the right way in the dacom.ini file? C:\PROGRA~1\FLShell\FLShell.dll
Did you check FLSchell is on the place you put in the ini file? Maybe you installed it on another disc.
Or maybe a corrupt dll file.

@Xarian_Prime - no problem, I just didn’t want people thinking that I was the one who coded the plugin version or that my version supports plugins.

@khayman:

Thanks everyone for your reply’s

Dependency Walker says that 1 or more files dont support 32 or 64 bit files or something, so im guessing my pc cant run flshell…

I guess it don’t run on 64 bit. Because i run xp to, the 32 bit version, and it works without any probs

I agree with Nieckey, i had that same problem and solved it by disabling DEP for flserver.exe.

And flshell doesn’t support x64 AFAIK.

What’s DEP and where and how to disable it?

I take it your on Vista m8

Data Execution Prevention… the most evil thing ms has thought up in years…
It’s supposed to save you from malware… but most of the time its crazyware itself blocking things
without telling you… or just plain forgeting what you’ve told it b4…

with the “old view” active
Control Pannel/System -->> advanced system settings… under Advanced tab click “settings” in the performance area…
DEP is the last tab… but oh nelly u only half way now…

You have 2 options… leave it as is… or go though every program and tell DEP its safe… and i mean EVERY program windows apps the lot… fauilire to do just that forced my PC to “prevent” windows login… that was a fun week i tell ye…

Best of luck…

Safest way is not to install programs to the “Program Files” or “Program Files (x86)” folders, as it’s those 2 that DEP “interferes” with.

Oh and it also helps to “kill” that PITFA UAC as well

And flshell doesn’t support x64 AFAIK.

Well here we go… Now i’m running flshell on x64 ;D
Anyone had experience with that? What kind of bugs can i encounter?
Flserver is running as 32-bit process though, may be in this case flshell is okay?

I had already some strange things happend like kicks with no reason when trying to buy a ship, very seldom though. And i don’t even know where are they come from…

Btw! On x64 machine with x64 Os : How about to copy x86 dlls to flshell folder from x86 xp (or google)?

Safest way is not to install programs to the “Program Files” or “Program Files (x86)” folders, as it’s those 2 that DEP “interferes” with.

Hell yeah… took me a while to work that one out…

Its all C:\ now baby!.. or D:\ but not in the “evil” Program files… grrrrrr even my games & production software has
all been reinstalled “outside” of Proggyfiles…

Worst MS mistake ever!!.. oh that and Vitsa in general… (and i actually like V lol… but i’m certified carzy!! )

no idea about x64… i wont go near one… hear way too many bad things about it (incompatible stuff)… seems it’s more of a
hassle than its worth?..

Nah, x64 is actually more secure, faster and it support a gazillion amount of RAM. 4gb total is getting small (and that includes all other memory, so I barely had a 3gb cap here). Driver problems are mostly a thing of the past; as long as your hardware isn’t 5 years old or built by a totally unknown company, it’ll have proper 64 bit support.

OutCast wrote:
I agree with Nieckey, i had that same problem and solved it by disabling DEP for flserver.exe.

And flshell doesn’t support x64 AFAIK.

CorFlags /32BIT+ flserver.exe
```:D
EDIT: Fiasco :D