Can someone help me out plz....
I made my own LiveXP (see attached image)... but autosearch DIPE gives me an error.
It says can;t find script engine JSCRIPT for script dipe.js???
What should i do now in winbuilder? (i use v.080)
TiA!
P.S.: i used drvimpe62.script from amalux site.
Autosearch DIPE from Amalux not working?
Started by
ScarySpons
, Mar 31 2010 08:02 AM
4 replies to this topic
#1
Posted 31 March 2010 - 08:02 AM
#2
Posted 03 April 2010 - 01:26 AM
Hi ScarySpons,
Sorry for late response,
Thanks for reporting,
Download new ScriptingMS (v2) from LiveXP server ( \Components\Core\1 System --> ScriptingMS) and make your build with it
ps: there is no difference between amalux's dipe script from amalux site or LiveXP server. Both are same and great work from amalux.
Sorry for late response,
Thanks for reporting,
Download new ScriptingMS (v2) from LiveXP server ( \Components\Core\1 System --> ScriptingMS) and make your build with it
ps: there is no difference between amalux's dipe script from amalux site or LiveXP server. Both are same and great work from amalux.
#3
Posted 03 April 2010 - 01:07 PM
Hi ScarySpons,
Sorry for late response,
Thanks for reporting,
Download new ScriptingMS (v2) from LiveXP server ( \Components\Core\1 System --> ScriptingMS) and make your build with it
ps: there is no difference between amalux's dipe script from amalux site or LiveXP server. Both are same and great work from amalux.
Thanx for your help lancelot (kardas )
Now working flawlessly!
Even VirtualBox is working now! (also from amalux site)
I love LiveXP
#4
Posted 03 April 2010 - 05:16 PM
Glad it's working now, I was also having issue in new builds so I'm glad Lancelot came to the rescue!
#5
Posted 03 April 2010 - 08:29 PM
Hi amalux,
sorry, it was my mistake ..... but all for good goal to have single united script
Now on application scripts a single expression can be used easly without causing further confusions.
ex: vbox script requires 'Scripting Support' (ps: I just renamed title, check new ScriptingMS.script v3)
I guess you like.
sorry, it was my mistake ..... but all for good goal to have single united script
Now on application scripts a single expression can be used easly without causing further confusions.
ex: vbox script requires 'Scripting Support' (ps: I just renamed title, check new ScriptingMS.script v3)
I guess you like.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users