Thread: Lsx Void 3.0

Well, I have some type of bug that isn't letting me run RR at all. I don't know if this is a RR bug or LSX bug, but I thought I'd try here first.

I'll load RR and no more than a couple minutes into it (sometimes immediately) I get an error forcing RR to exit. When I get the error report details, its linked to a ziplocator.dll. I assumed it had something to do with the GPS so I changed the RR GPS comport to 0 so it doesnt access the GPS at all.. It seems to have fixed the problem for the short time Ive tried it. But now, obviously, I don't have a working compass, speed indicator, or fuel price updates in LSX..

Anyone know how this can be fixed??

Originally Posted by HJC

I had a similar problem. Running RR starts off with no iList runs, then press the AUDIO and it freezes. Debug shows the same initDX error.

What worked for me was changing the settings in LogMeIn, which is a free remote desktop webapp. If you happen to be running this, go into the Preferences>Remote Control Settings and uncheck "Use Mirror Display Driver".

If you're running some other kind of remote control program, look into something similar.

Works for me perfectly now.... at last!

Spoke too soon , I just realize that if I hibernate while in the audio screen, the iList resumes blank! Nothing will bring it back except for restarting RR.

Originally Posted by CARLOS_CET

Are you using Radmin to connect to your CarPC? Is that when you see the problem? If so, that's the reason that your RR is hanging when clicking on the Audio screen. I had this problem using Logmein to the CarPC. It does not support DirectX which is used by the skin. When I tried pressing the Audio button from inside the car, I had no problem. Only when accessing the CarPC remotely. Hope that helps.

No, only used Radmin to do system updates and other installations stuff.

I have pretty much given up. I'm reinstalling XP.

This is the order to setup LSX:
1) use installer of RR
2) copy updated binary files into RR folder
3) install LSX Void 3.2
4) run rrconfig.exe to setup everything
5) cross fingers when starting up RR

or can I do this

1) create Road Runner folder on any drive and extract the updated binary file download into it
2) install LSX Void 3.2 into that created folder
3) download the updated rrconfig.exe from forum and put into RR folder
4) run rrconfig.exe and setup everything
5) cross fingers when starting up RR

Will either of these be fine or is there a different preferred method when installing everything?

Thanks guys!

Originally Posted by MrTrunks

No, only used Radmin to do system updates and other installations stuff.

I have pretty much given up. I'm reinstalling XP.

This is the order to setup LSX:
1) use installer of RR
2) copy updated binary files into RR folder
3) install LSX Void 3.2
4) run rrconfig.exe to setup everything
5) cross fingers when starting up RR

or can I do this

1) create Road Runner folder on any drive and extract the updated binary file download into it
2) install LSX Void 3.2 into that created folder
3) download the updated rrconfig.exe from forum and put into RR folder
4) run rrconfig.exe and setup everything
5) cross fingers when starting up RR

Will either of these be fine or is there a different preferred method when installing everything?

Thanks guys!

Well, I can only give you what I did when I installed on the Mputer after wiping everything clean except the OS (Full Xp sp2 with all MS updates):

1.winamp 5.13 (default location)
2.RR installer (default location)
3.RR binary 12-06-07 (RR root folder)
4.Void 3.2 (default location, newest release)

All running fine after a proper config.

One thing I did find was if I installed winamp after RR, it was slow to start and sometimes wouldn't start at all. Not sure why, that's just what it did.

Also, as LS has stated, it is very important to setup your media paths correctly. Void seems to not like being told to do something and not know how to do it..........

To those that are having lockup problems on your audio selection:
is winamp running? Are your ilists blank? I've had lock up problems but it seems to have been caused by winamp. A reinstall of winamp has solvedmy problems it seems. Same with the ilists, if RR starts up and winamp lags behind, my ilists are blank. Shutting down RR and restarting usually solves this for me. Doesn't happen often, but occationally. If I click audio with a blank ilist, it may lock up, it may do nothing. Blank Ilists are my cue that something didn't start right and it's time to do a restart. It may not be your problem, it's just what works for me.

Cheers

Originally Posted by HJC

I had a similar problem. Running RR starts off with no iList runs, then press the AUDIO and it freezes. Debug shows the same initDX error.

What worked for me was changing the settings in LogMeIn, which is a free remote desktop webapp. If you happen to be running this, go into the Preferences>Remote Control Settings and uncheck "Use Mirror Display Driver".

If you're running some other kind of remote control program, look into something similar.

Works for me perfectly now.... at last!

yes, this is something i forgot to mention also. Sometimes just having 3rd party remote software installed it will screw with things. I had the same problem with other software failing to run because of a mirror display driver that was turning off my hardware acceleration. Unfortunately this sucks big time if you ask me as using remote software to administer the carpc in my book is a requirement.

also to those who have tried everything and are about to reinstall xp because of the direct x init error, personally i would NOT do this. There is likely nothing wrong with your directx install or your OS. Run dxdiag (start>run>dxdiag) and if your system passes all the test, then your setup is fine. This is an issue with RoadRunner. There is nothing i can change inside the skin that will fix the direct x init error except for removing the ilist from the skin completely, which is what i think im going to do. There are just far to many people having issues or unable to run the skin because of the ilist. So there will be another version of the skin that does not use it at all.

Originally Posted by HJC

I think the scheme of 2.x was perfect for day and night. If the day version of 3.x is the same, it would be perfect.

Actually, to be honest, I really love the way 2.x looks.. even more so than 3.x. The buttons are modern and sharp looking. I've got it running perfectly on my carPC. Only reason why I've got 3.2 running now is the iList function. Yet, I may still go back to 2.x Day/Night after running 3.x to see how things go.

unfortunately i dont feel the same about 2.x. The day version IMO is pretty ugly. Its just too blown out for me. The buttons in 3.x arent that much different than 2.x. In 2.x it was mostly just a glass bar with the text ontop. 3.x has that but with an extra button shape ontop of that. But visually they still have a lot in common.

There is a lot more to 3.x than ilist. The ilist feature was an afterthought for the most part.


I have a solid idea in my mind for the next skin though, ether, which is supposed to start development after the new year (if i remember correctly) and it will not suffer from having to have a day or night version and will look better than any of the LS, LSX, or VOID series of skins.

fix for preset button in audio player leaving audio in a muted state when switching presets.

unzip attached file into the skins folder, overwrite existing file.

also, im currently looking at freefone intergration. I have some bluetooth driver issues right now from trying to get a stereo headset to work a few days ago so ill need to fix that before i proceed.

Well, been running 3 days in the car now.

No issues. Running great!

Thanks LS, fantastic release. had some troubles early on, but it was mostly all on my end.
3.2 is, without a doubt, the best looking skin out there. And your level of support on it is commendable.

Well done!

Cheers