OXO LOLA of CPUe-1

Post Reply
Mick70

OXO LOLA of CPUe-1

Post by Mick70 »

Hi all,

I seam to have a problem LOLA-ing CPUe-1 CPU's.

I set the three dip switches as requested. I start the CPU. The 4 files are getting FTP'ed into the CPU. After that it just sits there not starting to load the binaries.
Im trying to load OXORelease 4.1 and I use LOLA 300 8.1 :cry:

I only have the problem with the CPUe-1. All other CPU's are fine to LOLA.

Appreaciate any comment.

M.
astro

Post by astro »

Not sure what it's like in the states (I'm assuming that's where you are), but here in Aus we only have to change one dip switch. Which ones do your documentation say you need to change?

From the Australian Documentation:

Image
User avatar
tot3nkopf
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 4058
Joined: 02 Feb 2006 10:41
Location: Germany & Romania
Contact:

Post by tot3nkopf »

Hi,
I had the same problem with a rel. 2.1 CPU (Aspen though), using the same release of LOLA like you. I've used LOLA 2.0 and everything worked just fine (loading the four tickets and then immediately uploading the OS).
So my advice is that you use LOLA 2.0 (LOLA 3.0 seams to have a problem).

Hope this helps.
astro

Post by astro »

LoLa 2 was definately a little less buggy than LoLa 3. That being said, there are some ways around it. If you use Regedit and go to HKEY_LOCAL MACHINE > Software > PCX Tools > LoLa300R8.1, you'll see the registry settings that control the account that LoLa uses to log on with. It creates it every time you start a new LoLa.

The solutions I've found to LoLa's many problems are as follows:
  • Set your IP to 192.168.92.245, then reboot. This helps as sometimes your route settings don't update immediately
  • Manually create user LoLa300R8.1 and set the password to #LoLa300R8.1 using the User Management tool in your control panel
  • Make sure that windows firewall (and all other firewalls) are totally disabled. They'll wreak all sorts of havoc on a LoLa
  • Use a network switch or hub instead of a crossover cable.
  • Move your downloadingitems folder (containing the system software) to a folder like c:\lola\downloadingitems. Sometimes LoLa can't access really long directory trees
If all else fails, try from a different computer or use a different network card - I use a PCMCIA network adaptor just for LoLaing, and don't have any problems.

Cheers,
asro.
Mick70

Post by Mick70 »

Thanks guys,

none of the suggestions worked. I can Lola any of the older ( Aspen) but none of the new one with the 3 dip switches(intel).

The dip switch setting I use are the same as in AUS.

Thank you so much anyway.
OZ-PBX

Post by OZ-PBX »

Thanks astro your tips helped me with my Rel2 and Rel3 system problems..
astro wrote:LoLa 2 was definately a little less buggy than LoLa 3. That being said, there are some ways around it. If you use Regedit and go to HKEY_LOCAL MACHINE > Software > PCX Tools > LoLa300R8.1, you'll see the registry settings that control the account that LoLa uses to log on with. It creates it every time you start a new LoLa.

The solutions I've found to LoLa's many problems are as follows:
  • Set your IP to 192.168.92.245, then reboot. This helps as sometimes your route settings don't update immediately
  • Manually create user LoLa300R8.1 and set the password to #LoLa300R8.1 using the User Management tool in your control panel
  • Make sure that windows firewall (and all other firewalls) are totally disabled. They'll wreak all sorts of havoc on a LoLa
  • Use a network switch or hub instead of a crossover cable.
  • Move your downloadingitems folder (containing the system software) to a folder like c:\lola\downloadingitems. Sometimes LoLa can't access really long directory trees
If all else fails, try from a different computer or use a different network card - I use a PCMCIA network adaptor just for LoLaing, and don't have any problems.

Cheers,
asro.
Post Reply

Return to “MAIN”