Log in to your RCTgo account

v.RCT3, Vista, already fixed SecureRom, hangs after copyright disappears. No errors.

#1
My son got a new computer. It's a Lenovo laotop using Intel dual cores. the first problem with Visual C++ runtime error was resolved after running SecureRom's utility and updating the RCT3plus.exe using their software.

However, now when the game starts up, the usual Atari copyright screen appears and disappears then hangs at a blank white screen.

If memory serves, this is where the actual splash screens would start and the audio as well.

Does anyone know if this is a driver issue?

I hate it when things crash without errors! TIA
Reply
#2
Hi Amy,

Being a new computer, it is common for users not to carry out essential system updates. They assume that snce the PC/Laptop is new that it is ready to go.

Have you carried out all the essential security and program updates using Windows Update? If you use the custom option you can also check if there are any non-essential program updates and also driver updates.

Are you using a full administrator account to try and run the program?

Try the above and see how you go.
Reply
#3
(Jun 5, 2010, 04:30 AM)Cobraderra Wrote: Hi Amy,

Being a new computer, it is common for users not to carry out essential system updates. They assume that snce the PC/Laptop is new that it is ready to go.

Have you carried out all the essential security and program updates using Windows Update? If you use the custom option you can also check if there are any non-essential program updates and also driver updates.

Are you using a full administrator account to try and run the program?

Try the above and see how you go.

Thanks, I think I nailed it.... It's a built in video chip and not a card...sigh
Reply
#4
(Jun 5, 2010, 02:27 PM)amyc Wrote: Thanks, I think I nailed it.... It's a built in video chip and not a card...sigh

I was going to ease into that one next. Try the updates anyway ... you never know although I suspect as is the case with many games these days, the onboard card that shares system ram is more the likely the problem.
Reply

Users browsing this thread: 1 Guest(s)
Advertisement