If you run orbiter_ng without a graphics client, there won't be the splash screen displayed when you start a scenario, because this is done in the render window, so it isn't the case here, unless there is some graphics client installed and enabled, but he wouldn't get the console window stating there is no graphics client instead of the render window with splash screen in such case, while starting the simulation from orbiter_ng.
Also, did you give him your Orbiter folder, or the Zip file you downloaded from the website?
If it's copied Orbiter folder, he should try deleting Device.dat and Orbiter.cfg from Orbiter's root directory. There could be also file permissions issue if it was copied with preserved Access Control Lists (moved on a media using NTFS file system).
The source zipfile is set to run a compatibility check at the start. Nothing elaborate, but definately DXDiag.
The installation verification tool also installs Visual C++ 2005 redistributable libraries if they weren't found, but since the Orbiter launchpad appears without error, missing C++ libraries aren't the problem either.
There could be an error dialog box hiding under the splash screen (render window). He should try pressing alt-tab to check that. This could tell something more along with the Orbiter.log, like missing hardware T&L support, which can be worked around, without need for buying a new graphics card / a better laptop. Orbiter can run just fine with integrated graphics cards.