Stuck in Boot Screen

Discuss issues and ideas you have to configuring displays with PowerVision
muhit
Posts: 14
Joined: Fri Nov 22, 2013 7:09 am

Stuck in Boot Screen

Post by muhit » Tue Mar 11, 2014 4:51 am

I have Powervision Configuration Studio 2.3.20007 installed on my computer(Windows 7). I created configuration package on my computer and loaded that configuration to PV450 Murphy Display. The load process is successful but while starting up the display, the display stucks in boot screen logo and doesn't start PV450 configuration. I have re-installed PowerVision Configuration Studio. But the result was same.

I tried the same scenario on another computer (Windows 7) and after the successful loading process, booting process completed successfully and the configuration works like a charm.

Then I decided to compare two configuration package files created on those two different machines with Beyond Compare software. You could see the result screen in the attachment. Could you give me detailed information on these result? Why does the same two configuration created on different machines bring different output packages? Why does one of them work successfully but the other one stuck on the boot screen?

Hoping to hear from you as soon as possible.
Thanks for your time.
Attachments
comparison.JPG
package comparison window screenshot
comparison.JPG (157.02 KiB) Viewed 89 times
jpratt
Enovation Controls Development
Enovation Controls Development
Posts: 222
Joined: Mon Jun 21, 2010 11:18 am

Re: Stuck in Boot Screen

Post by jpratt » Tue Mar 11, 2014 10:02 am

Due to timestamps in the files, you probably can't rely on a diff between the files. If you compare size that might help but the files (especially the 2.3 xml files) are not going to be comparable due to our internal rekey process and timestamps that are put in the files.

Its possible there is some difference between the two machines that causes this. Some things to check are...1) Are the regional settings the same. For example are both set to English or is one a different language. 2) More important the language is the symbols used for numbers. For example, do you have "," used for a decimal separator rather than a full stop? That could be causing trouble as well. 3) Compare the versions of PowerVision (i assume they are the same). 4) Make sure you are creating a "FULL" install and not a "CONFIG" install. You may have different applications loaded on the display that are incompatible.
Jake Pratt
Software Development Manager