Jump to content











Photo
- - - - -

WinBuilder 2013 issue with JAVA RTE


  • Please log in to reply
4 replies to this topic

#1 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12688 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 02 January 2014 - 02:57 PM

Try this:

  • Have a Windows system (in my case XP, but IMO there is the same behaviour in newer windows OS) which has never seen WinBuilder
  • Uninstall every JAVA
  • Install jdk1.7.0_45 as only JAVA
  • Download and unzip WinBuilder into an empty directory. You can see the subdirectory Java containing jre6
  • DoubleClick WinBuilder.exe

What happens?

Nothing!

 

When you delete the Java directory which came from the WinBuilder installation, everything works fine.

(WinBuilder seems to conflict with the attached RTE and uses the installed RTE)

 

Has somebody similar experiences and can give an "everytime valid" solution?

 

Peter



#2 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12688 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 04 January 2014 - 03:22 PM

Some new information:

 

The issue seems to exist only(?) under the above explained conditions.

 

I created a PE3 running under VirtualBox, downloaded WinBuilder there and run it.

It is 100% true that inside the VM / PE3 there is no java knowledge.

 

The result:

 

I could generate an ISO wich looks reasonable.

 

Just for fun:

Inside the VM / PE 3 a needed font seems to be not supported.

WinBuilder's console output looks very strange:

VM-Winbuilder.gif

I already tried to add the Consolas font to the PE, which is used in the WinBuilder GUI, but there seems to be an interruption to the RTE.

But that is not important. Important is the result of the test:

 

WinBuilder.exe 2013.09.01 works with the attached java RTE in (Windows) systems without any java installed.

 

Peter



#3 Nuno Brito

Nuno Brito

    Platinum Member

  • Team Reboot
  • 10440 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 04 January 2014 - 11:56 PM

As mentioned before, uninstalling java is not a reliable procedure. No guarantee this works.

Better to test with an XP installed fresh from a VM.

#4 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12688 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 05 January 2014 - 10:00 AM

We have to take care on the "Standard User".

 

He installs WinBuider on his system, double clicks WinBuilder.exe and is disappointed.

 

Reinstalling Java on my system was necessary for other reasons, not to test.

 

We must find out why this happens and prevent that failure.

 

Peter



#5 Nuno Brito

Nuno Brito

    Platinum Member

  • Team Reboot
  • 10440 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 05 January 2014 - 10:41 AM

Peter, I fully agree. The point I'm raising is that the way you describe to do the test is not reliable enough.

We should use machines as close enough to the end-user. When you are using your development machine that had infinite times the java runtime installed, there is no way to validate if it is your machine that is causing the problem or if this is indeed a generic problem that we can replicate and see happening with frequency to other people.

Reminds of that joke about a guy that goes to a doctor and complains that everywhere where he touches has pain. The stomach, the arm, the leg, ... The doctor looks and finds nothing. In the end he looks at the patient's hand and notices a wound on his pointing finger. There was the problem found.

Same thing here. Really no point in opening a new thread, call people to test or try to replicate what might really be a problem from your working machine. A clean Windows 7 machine installed from a VM is a more reliable indicator if indeed something is not working and needs to be fixed.

Hope this helps.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users