I've been forced to do this due to the rise of "Null.bmp" error posts and topics.
It's as easy as 1-2-3.

1.Copy Null.bmp
2.Paste it into "Devices"
3.Finish

(Mods, please sticky/announcement this please)

Moved, but no sticky.

It'd be better if people just fixed their mods so that this error doesn't come up. It'd be a whole lot easier for everyone.

but this is a simple and easy solution, I mean you obviously have two options:

1 sticky this topic.
2 keep telling many many many many many modders NOT to use the null.bmp in devices.

which do you think is the quicker/easier solution?

Telling many many many many many modders NOT to use the null.bmp in devices is the best solution.
Because it's their fault for using the old filepath.
And everyone who downloads Cortex Command who didn't have B18/19 is going to get this error.
Which will add up to a number greater than the number of modders.

See above.

Also, for future reference:
"(Mods, please sticky/announcement this please)"

ASKING for a sticky is as likely to get you a sticky as, oh, asking to be a mod is to get you modded.

It just doesn't work that way. If something's going to be a sticky, it's very likely that a mod is the one who's going to create it.