User forums > Using Code::Blocks

Disable certain compiler access

<< < (3/3)

thomas:

--- Quote ---TweakUI cannot block CDROM access, it can only hide it from Explorer.... going into command prompt or typing in a pathname still works, regardless...
--- End quote ---
At least command prompt can be disabled in the registry. The pathname issue should not be too much of a hindrance. You can also obfuscate things a bit by assinging an unusual drive letter (M: or X:). This is still far from being safe, but it is as good as you can do (apart from disabling the CDROM in the BIOS).


--- Quote ---Anyway, I guess I will have to wait for XML to be the configuration style...... How hard would it be to implement it?
--- End quote ---
11 days exactly.
But your problem is not one of configuration. Your problem is that you are not using the proper tools. Windows 98 is not suitable for an untrusted installation. Someone using another compiler is absolutely the smallest problem that you will encounter. You should really abandon that idea and use an operating system that allows you to properly restrict access rights.

Conan Kudo:
I would if I had the money  :( I gotta work with what I got... I only have ONE NT-based machine, and that is where all the code changes merge at and send back out to the machines with updates on the fly.... (not thru C::B, since my SVN-based system does not work until SVN plugin works)
It is also where the one copy of Visual Studio is.... Windows MCE 2005.... Good development machine, I can say that much...
I just want to turn off the other compilers, so that they do not get confused when they are adding other directories, SDKs, etc.
They tend to put on all the lists, even when I tell them not to... And multicompiling works best on Windows 98 since it uses the least amount of RAM of all the M$ OSes that are still in use today...

Navigation

[0] Message Index

[*] Previous page