LSX Void Error

**TeamRSX** · 12-30-2007, 02:25 AM

First off i would like to say this is a great skin.

I have just installed it and havent had much time to play around with it, but i am receiving an error.

I have attached a pic of the errors from the audio menu.

Once the skin loads and i click on 'Audio' from the main menu. Once i am in this menu and click on Up Directory i receive the first error. When i click on Down directory i receive the second error.

I am sure its something i am doing wrong.

Also, if there are any other bugs or fixes that i should be aware of that would be great. I am using version 3.2

UPDATE:

The solution to this fix was to install winamp version 5.13 instead of an earlier release. Once this was done i had no problems with the directory button on the audio screen.

I also made sure that rr.ini was pointing to the correct music directory and made sure i hade the correct directory structure in my music folder.

**mnickolson** · 12-30-2007, 07:25 AM

Do you have winamp 3.15 or earlier installed and set in RR Config?

**TeamRSX** · 12-30-2007, 12:00 PM

Originally Posted by mnickolson

Do you have winamp 3.15 or earlier installed and set in RR Config?

I have winamp version 3.0 installed and pointing to that directory in rr config.

What are the requirements to run lsx void 3.2?

Also, does anyone know how to embed FreeFone into LSX Void 3.2?? Not sure exactly how?

**TeamRSX** · 12-30-2007, 07:27 PM

BUMP..

I am still getting the above mentioned errors.

Any help would be appriciated.

**treetop777** · 12-30-2007, 09:00 PM

your original helper probably meant winamp 5.13; try installing that version (5.13)

You would probably also get better response if you posted in the LSX Void thread..

**liquid_smoke** · 12-30-2007, 11:03 PM

use winamp 5.13 (not 3) and make sure you have your music path setup in rr.ini

**TeamRSX** · 12-30-2007, 11:29 PM

Thanks for your help everyone.

I have managed to get this problem resolved.

**liquid_smoke** · 12-31-2007, 12:52 AM

also, all bug fixes are posted on the first post of the skins thread, as well as any updates etc.

also, for future reference for anyone else having the same problem. What was the fix