BrokenThorn Entertainment

Im not really sure what you mean there. If you mean that if your code checked to see if the value pointed to was null you could do whatever you feel like with the pointer with no ill effects im afraid that this is incorrect. Actually it is pretty much unsafe to do what you are trying to do at all d...

But, if the code checked for null, its fine though?

To prevent this spam from having an effect, you could maybe disable signatures for anyone whos not a moderator, or has below a certain number of posts?, or maybe use a captcha on registration so they can't spam in the first place as well(I suppos it only helps wiht bots......., and annoys us all tho...

Oh, thanks!
So, if he did testfname = " "; above that code, its fine?
If so, I now understand !

A post on OSDev. Pointer to null terminated string. It said you need to have malloc first, but C doesn't use malloc if you do char * test; test = "test"; Does it? int findfile (char *fname) { unsigned short entry = 1; char *testfname; DebugPrintf("\nLooking for file: %s\n\n", fname); while (true) { ...

In C/C++, I use char * to define a string. Why is it not OK to use a character array in your operating system, when its fine for a normal program, and also, how does the compiler set where a char * oints too when you make it?
I believe there is something important I don't know here.....

That fixed that...... But still: MISSING OR CORRUPT KRNL32.EXE

In Visual Studio 2008. I get an unresolved external reference to __aullshr for every Unsigned shift right.
In Visual C++ 2005 Express it compiles, but it says its corrupt...(Ot, it can't find it).

Is this (VS2008) bug known?
And, is there a way of fixing either of these problems?