[ecaz]

So, we all know about editing WaitingForLoginWindow with the code from a different PDF file with a HEX editor, blah blah, been doing that since System 7 w/ the "Welcome to Macintosh" and ResEdit.


I've been tinkering recently with the version 6.0 Java developer release from apple, which happens to have a -splash:image.jpg function build in, for example:

java -splash:image.jpg HelloWorldApp, or simply java -splash:image.jpg

unfortunatly, when I edit /etc/rc and comment the line about /usr/libexec/WaitingForLoginWindow and replace it with another application, such as

/System/Library/Frameworks/JavaVM/Versions/1.6/Commands/java -splash:image.jpg

nothing shows up in the timeframe between the grey screen and the desktop (also known as the blue screen that usually has WaitingForLoginWindow running.)

Does anyone know why java would not render in this environment? Any ideas at replacing WaitingForLoginWindow with something that looks cool, like a custom splash screen, but without editing the stupid program for a crappy 16k pdf file?


Thanks in advance!

[ecaz]

this is the /etc/rc change, pretty simple


if [ "${VerboseFlag}" != "-v" ] ; then
/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Commands/java -splash:5.jpg
# /usr/libexec/WaitingForLoginWindow
fi


I have tried both with and without calling a Java Class at the end of the java command.

I can run other applications, but they dont' show up until the desktop loads.. how does apples program work and ours does not? Grr!

[Chuckit]

I think Java depends on the window server to display, and the window server isn't running yet. This is a special program meant specifically to show up there.

[ecaz]

Any idea what its written in, or how to disassemble it so that it can be recompiled with a custom pdf, preferably one that's not 16k? =)



In any case, thanks for the info =)

[ecaz]

bump