You may want to change the install script so that when it gets to the part about the white box, it says something more like, "Go ahead and follow the instructions from the installation, clicking "Next" and making your selections as normal until a blank, white window pops up. When it does, then click next below (in this window) to continue with the installation."
The reason I say this is because it just says something like "Click next when the white box appears," which made me think that I should see the white box RIGHT AT THAT MOMENT, and since I didn't, I figured it wasn't an issue for my system, and I clicked next. And then later it made sense. I think other users may similarly make the same conclusion.
It's just a little thing though, and isn't actually an error or anything on your part, heh.
Update: Alright, so I've investigated a little bit more, and it turns out that I didn't need to start the install over after all. Apparently the white box can simply be closed normally like I did the first time, and your script is just being nice and closing it for us if we take advantage of it. Still, might be nice to have that notice.
This left me to wonder what the real reason for C&C3 not working for me was, since your script seems to work so nicely.
I headed over to
the WineHQ Application Database entry for C&C3 and figured a few things out that got it to sort of work for me.
The error message that it gave me after about twenty seconds of staring at the loading screen read, "Please make sure you have DirectX 9.0 or higher installed. Also verify that your video card meets the minimum requirements, and that you do not have hardware acceleration disabled in the Display control panel." This was solved by me editing the Wine configuration so that it used an 800x600 virtual desktop. The WineDB page made it sound like I could do this temporarily just to get to the settings page to change the resolution to what I actually used, but after I did it and then turned off the virtual desktop, the error came back just like before. But hey, at least I know how to make it work, so I'm pleased with myself.
Unfortunately though, there was no cursor at all. Sure enough, this is also talked about on the WineDB page I linked to above, and it sounds like they've actually got a fix for it. However, the instructions they have to get the cursor to display are rather intimidating. Apparently there is a patch that needs to be installed and wine needs to be recompiled or something. It would be very, very cool if your script took care of this, or if there was another script that would install this patch to wine perhaps since it sounds like it isn't just an issue for C&C:3.
The next thing I'm going to try to do is run the script that installs the game update patch to C&C:3. I'm crossing my fingers that this will fix the remaining two issues I just explained, but since I'm betting the point of the script is just to install the game update, I won't hold my breath, heh.
Anyway, I hope that the issues I'm facing turn out to be isolated to just being me, but since it all seems to line up with the issues that are reported on the AppDB page, maybe it would be good to incorporate these fixes into the script that installs C&C:3.
Thank you very much for you hard work! It is appreciated!
Update 2: Looked more into the mouse issue while the game update patch script runs. Reading the comments, it seems like the new version of Wine did broke it a little. It looks like the previous version of Wine at least had it display the regular mouse without needing that Wine patch instead of not displaying no cursor at all. Just an observation that I thought you might find relevant.
Edited by Square Bottle