RTi Core v1.3 Enigma 2

[afred]

_{Beter een losse server dan de box zelf.}

 

_{Prima "losse" server maar dat betekend dat er in de E2 box wel een CD kaart moet, of heb ik dat mis?}

_afred.

10 november 2011 aangepast door afred

[Perdi]

Als je een losse server gebruikt, dan kan je daar je kaart in doen. Je kan een oud PC'tje als (Linux)server inrichten, maar een oude DM7000 doet het ook prima.

Je beide andere boxen laat je dan als client naar je server connecten.

Dat werkt inderdaad het fijnste, want je kan dan aan de ene box klooien, zonder dat de andere daar last van heeft.

[maanvol]

After the installation of 'RTI_Core_1.3' my receiver always remains stuck on '=s' (Loading enigma2). In order to get the ip on the receiver, I've placed the file 'patch.bin' on a usb stick, but when the receiver boots up; the image 'RTI' writes a folder 'usr' on the usb stick -- making it impossible for the receiver to start from the 'patch.bin'. What to do? Many thanks.

 

 

With the DB9/RJ45 cable the first step on'VU+ Util' is all right:"Serial port open success", but when I turn on the box; there is no reaction from 'VU+ Util'.

 

 

How might this be explained -- 192.168.1.6, is the box:

 

 

 

Microsoft Windows [Version 6.1.7600]

Copyright © 2009 Microsoft Corporation. All rights reserved.

 

C:\Users\maanvol>ping 192.168.1.6

 

Pinging 192.168.1.6 with 32 bytes of data:

Reply from 192.168.1.2: Destination host unreachable.

Reply from 192.168.1.2: Destination host unreachable.

Reply from 192.168.1.2: Destination host unreachable.

Reply from 192.168.1.2: Destination host unreachable.

 

Ping statistics for 192.168.1.6:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

 

C:\Users\maanvol>

[zorlith1]

After the installation of 'RTI_Core_1.3' my receiver always remains stuck on '=s' (Loading enigma2). In order to get the ip on the receiver, I've placed the file 'patch.bin' on a usb stick, but when the receiver boots up; the image 'RTI' writes a folder 'usr' on the usb stick -- making it impossible for the receiver to start from the 'patch.bin'. What to do? Many thanks.

 

 

With the DB9/RJ45 cable the first step on'VU+ Util' is all right:"Serial port open success", but when I turn on the box; there is no reaction from 'VU+ Util'.

 

 

How might this be explained -- 192.168.1.6, is the box:

 

 

 

Microsoft Windows [Version 6.1.7600]

Copyright © 2009 Microsoft Corporation. All rights reserved.

 

C:\Users\maanvol>ping 192.168.1.6

 

Pinging 192.168.1.6 with 32 bytes of data:

Reply from 192.168.1.2: Destination host unreachable.

Reply from 192.168.1.2: Destination host unreachable.

Reply from 192.168.1.2: Destination host unreachable.

Reply from 192.168.1.2: Destination host unreachable.

 

Ping statistics for 192.168.1.6:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

 

C:\Users\maanvol>

 

I think you missed something.

 

In order to re-flash your Azbox, turn on your box and press (and hold) the Volume Up key on your remote until the Azbox starts in rescue mode and will display the IP number in the display. As soon as the IP number is displayed, the box is ready to be reflashed, using Azup.

 

Keep in mind that you should uncheck EXT4 and select EXT3 in Azup. Most likely, that is your problem right now.

 

Zorlith

 

**** NEDERLANDS ****

Ik denk dat je iets hebt gemist.

 

Om de Azbox opnieuw te flashen, zet je de box aan en drukt je op (ingedrukt houden) de Volume+ toest van de afstandsbediening, totdat de Azbox in Rescue Mode is opgestart en het IP nummer in de display wordt getoond. Zodra het IP nummer wordt getoond, kan je beginnen met flashen via Azup.

 

Denk eraan dat je het vinkje weghaalt bij EXT4 en EXT3 selecteert. Dat is denk ik het probleem.

15 november 2011 aangepast door zorlith1

[M_Z]

@ maanvol: This is a Dutch Forum only ! Please only post in Dutch language, if you can't we would to ask not to post anymore on Sat4all.

 

M_Z