GF-Ler, Griff1, sounds like you're MISSING .net Framework 2.0
its required, and at the very least XMComm.dll MUST be registered
MJSG-RR-RunMe1st.cmd can be used to register
See I knew id forget to mention everything, I Edited top post
Printable View
GF-Ler, Griff1, sounds like you're MISSING .net Framework 2.0
its required, and at the very least XMComm.dll MUST be registered
MJSG-RR-RunMe1st.cmd can be used to register
See I knew id forget to mention everything, I Edited top post
Quote:
Originally Posted by mitchjs
thanks, i was the reason.
OK, i added .net 2.0 Framework check to the installer
this is also my 1st time using INNO setup, so bear with me guys!
and I cant think of everything, so much work involved here!
Unless the instructions are followed above, clearly spelled out my Mitch, there are going to be LOTS of "It does not work!" posts.
If you wish to use the new RoadRunner build:
- You MUST install .net 2.0
- You MUST use the installer, as the required DLL's are installed with it. If you were to try to run just the new RoadRunner.exe without the new dll's, (By say copying it another computer) RoadRunner will not start, period.
I've noticed a few issues so far, and it may just be my setup(checking on my work computer, haven't tried in the truck yet), or the fact that the plug-ins need to be updated.
The music progress slider isn't working, or any slider for that matter
iLists don't seem to be working
Well I'm sorry, I am not happy about having to have the DLLs for XM,Sirrus and HD installed, nor having to have .net framework 2.0 installed (although it may be installed anyway I have not checked)
We don't have XM or sirrus over here and probably not HD either, so is a cmplete waste of time.
May I ask why ? Surely it's not a program registering one more dll, but it oesn't really make sense to me :confused:.Quote:
Originally Posted by mitchjs
barnyard, its YOU.. you might not have gdiwrapper or dxvb7 dlls registered!!
my music progress deally moves on my skin while playing a MP3 :)
mitch
please dont ask for a technicall reason, its HOW VB6 references a TYPE variable in a COM OBJECT... if the com object doesnt exist, VB6 dont know what to do, and runs home to mamma... dealing with a UNSUPPORTED LEGACY Language here (VB6)
at this point, i have NO plans to Modify my XMComm.dll and remove the VB6 TYPE dependancy..
also. slightly mistated, only XMComm.dll is REQURIED, but what the hell have em all...
doesnt hurt.