Yes, you did.

First thing I noticed is that you're doing horrible abuses of threadding
there.

Your main() method is most probably on a different thread than the UI.
All UI operations *should* be done on a single thread ('the' UI thread),
so that's one source of problems.

Another point is null layout managers. Don't set the layout manager
null. Either use an existing layout manager or create a custom one.
Either of those will result in less code on your part and fewer bugs and
display anomalities. (So, among other things, you should never be
calling setSize(), setLocation(), etc ). [yes, there are exceptions, but
they should be treated as not the desired approach]

Next minor point:
   window.show();
and
   window.setVisible(true);
do the same thing.

Oh, and aside from doing all UI work on the UI itself, one main point is
to *never* sleep on the UI thread.

And, sleep() is actually a static method, so
    Thread ct = Thread.currentThread();
    try
    { ct.sleep(mili); }
    catch(IllegalArgumentException e){}
    catch(InterruptedException e){}
should be
    try
    { Thread.sleep(mili); }
    catch(InterruptedException e){}

Anyway...

* Have a main() that *only* creates an AWT splash frame. Ensure that
there are no references to classes in the rest of your app there.

* Once that's up, use reflection to get the real main access point to
your application. (Call from the splash on the UI thread once the splash
screen is displayed)

* Spawn a new thread to do creation of your new app. Pass it an
interface for status updates to call back the AWT splash with.

* Make sure that in your main creation you use
SwingUtilities.invokeLater() to get updates back to the AWT splash.
Don't call that interface directly from the construction thread (since
by design it will *not* be the UI thread)

* To get sizes in your construction, call pack() on your frames after
they've been constructed and *before* they're to be displayed.

* Maybe have a call on your splash interface that passes the AWT splash
screen the instance of your app's main window to display, but ensure
that it does the switchover on the UI thread.