EUCardsharing
For this example, we will use the Adult bouquet to lock and hide.
* Select Setup menu then Parental Lock
* Select Parental Lock button and change pin to what you want and re-enter
* Select Save
* Select Service Organising
* Select Lock/Unlock Services
* Enter pin code
* Select Adult bouquet then select NO to lock it
You should have a padlock icon next to the bouquet now. You will be prompted to enter the pin when selecting this bouquet.
If you now want to hide the bouquet from the list…
Setup > Parental Lock > Hide Locked Bouquets > Save
How Do I Lock A Single Channels On An Enigma Image?
* Select Setup menu then Parental Lock
* Select Parental Lock button and change pin to what you want and re-enter
* Select Save
* Exit menus
* Press OK then RED (All Services)
* Scroll to channel you want to lock
* Press MENU
* Select Lock
Now even if the box is rebooted that channel will always be locked.
If the box is rebooted on a locked channel, it will ask for the unlock code on bootup.
How Do I Unlock A Single Channels On An Enigma Image?
* Press OK then RED (All Services)
* Scroll to channel you want to unlock
* Press MENU
* Select Unlock
* Enter Unlock Code
EUCardsharing
Friday, September 12, 2008
How to flash your dreambox using dreamup
EUCardsharing
How Do I Use Dreamup?
If, for any reason, your dreambox won’t boot, you will have to use Dreamup to flash an image instead of Flash Wizard Pro or any other method. You won’t be able to connect via ethernet so no ip address is required. It may be that the process simply hung up during flashing or you accidentally pulled the plug half way through (yes it did happen to me). This will get you back on track.
Required
* Null Modem Cable
* Image File (.img)
* DreamUp Program
Instructions
* Disconnect all cables from your dreambox, including the power
* Connect the null modem cable to the dreambox and to your PC
* Load Dreamup.exe
* Click Connect and you will see a message like this
dreamup2
* Connect the power and the bootloader should be copied to the box
* The message should now say ‘Box attached and Ready’
* Click Flash on the right hand side and select the image to be flashed
* Click Yes or Ya (depending on the version)
Note: If you’re flashing a backup image, select NO.
* The image should then be uploaded to the box
* There will be a countdown timer at the bottom of the program
dreamup6
dreamup5
* After the image is uploaded, it will be flashed to memory
* The finished process should look like this:
dreamup7
* Click OK and close down Dreamup
* Power off the dreambox for 30 seconds then power up
* If any errors appear, check all cables are connected properly and repeat the process but do not use the PC while it’s running
EUCardsharing
How Do I Use Dreamup?
If, for any reason, your dreambox won’t boot, you will have to use Dreamup to flash an image instead of Flash Wizard Pro or any other method. You won’t be able to connect via ethernet so no ip address is required. It may be that the process simply hung up during flashing or you accidentally pulled the plug half way through (yes it did happen to me). This will get you back on track.
Required
* Null Modem Cable
* Image File (.img)
* DreamUp Program
Instructions
* Disconnect all cables from your dreambox, including the power
* Connect the null modem cable to the dreambox and to your PC
* Load Dreamup.exe
* Click Connect and you will see a message like this
dreamup2
* Connect the power and the bootloader should be copied to the box
* The message should now say ‘Box attached and Ready’
* Click Flash on the right hand side and select the image to be flashed
* Click Yes or Ya (depending on the version)
Note: If you’re flashing a backup image, select NO.
* The image should then be uploaded to the box
* There will be a countdown timer at the bottom of the program
dreamup6
dreamup5
* After the image is uploaded, it will be flashed to memory
* The finished process should look like this:
dreamup7
* Click OK and close down Dreamup
* Power off the dreambox for 30 seconds then power up
* If any errors appear, check all cables are connected properly and repeat the process but do not use the PC while it’s running
EUCardsharing
How to flash a dreambox 7020
EUCardsharing
here a little how to
this is to install a firmware in flash i would advise you to flash your box with latest nabilo blackhole.
give us a shout if you get stuck
Flashing a new firmware (image) by Browser
What you need to flash
You need the image file you want to flash. Image files have the extension *.nfi. You can't flash other
images like *.img files from the DM7000. Don't try it - it won't work.
You need either a DHCP server, a configured bootloader or a serial cable and a terminal program
like HyperTerm.[/color]
You need a browser, and a network cable. If you connect the Dreambox directly to the PC,
you need a cross cable, if you connect trough a switch/hub/router you need a normal
(non-cross) cable.[/color]
To flash a new image, you can use the second stage loader. It must be present and not broken.[/color]
The following steps assume you have a DHCP server. If you don't have one, you have to setup
an IP address in the bootloader's [/color]serial setup[/color]. Oh, and it assumes you have a second-stage
loader newer than Version 37. The Second-stage version is displayed when you poweron the box,
in the LCD. look for "BOOT #37" (which is version 37). If it says "CF FOUND" instead, remove the
compact flash card to see the version message. If it doesn't say anything, it's probably an even
older version.
- Power down the Dreambox, either using "shutdown" (to enter the deep-standby mode) or by
using the power-switch. Standby is not enough!
[/color]
- (1.) Press and hold the lower frontpanel button.
- (2.) Switch on the dreambox, either by using the powerswitch or, in deep-standby mode,
press the power button. Still, hold the lower button.
- (3.) A text "*** STOP ***" should appear. If something like "/flash".. appears, you didn't
hold the right button. Now you can release the button.
The bootloader entered the "waiting" mode.
- (4.) Above the "*** STOP ***" text, there should appear an IP-address
(four decimal values with a dot in between). If there appears the string "dhcp" instead,
the box still searches for a DHCP server. Wait a bit. If it doesn't change, something doesn't
work with the DHCP server. Check wether network cable is plugged in etc. If it just doesn't
work, set an IP using the serial terminal[/color])
[/color]
[/color]
- Now, open a browser on your PC.
(1.) enter in the address line "http://ip/" (where ip must be replaced with the value in the LCD).
- (2.) on the bottom of the page, there's a link called "firmware upgrade". Click it.
[/color]
[/color]
On the next page, you can select the flash image you want to flash. be sure that it has the ".nfi" extension.
You can't flash other images (like .img)!
- Click on "FLASH!" and wait. It might take some time to upload and flash the image.
- Switch the box off again, and on again. The new image should be flashed and working.
EUCardsharing
here a little how to
this is to install a firmware in flash i would advise you to flash your box with latest nabilo blackhole.
give us a shout if you get stuck
Flashing a new firmware (image) by Browser
What you need to flash
You need the image file you want to flash. Image files have the extension *.nfi. You can't flash other
images like *.img files from the DM7000. Don't try it - it won't work.
You need either a DHCP server, a configured bootloader or a serial cable and a terminal program
like HyperTerm.[/color]
You need a browser, and a network cable. If you connect the Dreambox directly to the PC,
you need a cross cable, if you connect trough a switch/hub/router you need a normal
(non-cross) cable.[/color]
To flash a new image, you can use the second stage loader. It must be present and not broken.[/color]
The following steps assume you have a DHCP server. If you don't have one, you have to setup
an IP address in the bootloader's [/color]serial setup[/color]. Oh, and it assumes you have a second-stage
loader newer than Version 37. The Second-stage version is displayed when you poweron the box,
in the LCD. look for "BOOT #37" (which is version 37). If it says "CF FOUND" instead, remove the
compact flash card to see the version message. If it doesn't say anything, it's probably an even
older version.
- Power down the Dreambox, either using "shutdown" (to enter the deep-standby mode) or by
using the power-switch. Standby is not enough!
[/color]
- (1.) Press and hold the lower frontpanel button.
- (2.) Switch on the dreambox, either by using the powerswitch or, in deep-standby mode,
press the power button. Still, hold the lower button.
- (3.) A text "*** STOP ***" should appear. If something like "/flash".. appears, you didn't
hold the right button. Now you can release the button.
The bootloader entered the "waiting" mode.
- (4.) Above the "*** STOP ***" text, there should appear an IP-address
(four decimal values with a dot in between). If there appears the string "dhcp" instead,
the box still searches for a DHCP server. Wait a bit. If it doesn't change, something doesn't
work with the DHCP server. Check wether network cable is plugged in etc. If it just doesn't
work, set an IP using the serial terminal[/color])
[/color]
[/color]
- Now, open a browser on your PC.
(1.) enter in the address line "http://ip/" (where ip must be replaced with the value in the LCD).
- (2.) on the bottom of the page, there's a link called "firmware upgrade". Click it.
[/color]
[/color]
On the next page, you can select the flash image you want to flash. be sure that it has the ".nfi" extension.
You can't flash other images (like .img)!
- Click on "FLASH!" and wait. It might take some time to upload and flash the image.
- Switch the box off again, and on again. The new image should be flashed and working.
EUCardsharing
cwshare.cfg Turorial
EUCardsharing
Re: W in cwshare.cfg
The W line decides how your local card shall be used and shared on the network, and goes
in cwshare.cfg like this:
W: { 0A 0B 0C } P001 P002 P003 ...
A= Slot number (1 to 8 )
B= How your card shall be used locally (on your own box)
-0= Dont use card
-1= Use card for all Pid's
-2= Use card only for following Pid's
-3= Don't use card for following Pid's
C= How the card shall be shared on the network
-0= Dont share card
-1= Share all Pid's on card
-2= Share only following Pid's on card
-3= Don't share following Pid's on card
P is the Pid's
Example 1: I want my card in slot 1 to be used for all Pid's locally, and to be shared
on the network with all Pid's ( 1FFF means all Pid's):
W: { 01 01 01 } 1FFF
Example 2: I want my card in slot 1 to be used locally for all Pid's on card, and DONT want
it to be shared on the network at all:
W: { 01 01 00 } 1FFF
Example 3: I want my card in slot 1 to be used locally with the following Pids only, and to
be shared on the network too with the following Pid's only:
W: { 01 02 02 } Pid1 Pid2 Pid3 ...
rk, and goes in cwshare.cfg like this:
W: { 0A 0B 0C } P001 P002 P003 ...
A= Slot number (1 to 8 )
B= How your card shall be used locally (on your own box)
-0= Dont use card
-1= Use card for all Pid's
-2= Use card only for following Pid's
-3= Don't use card for following Pid's
C= How the card shall be shared on the network
-0= Dont share card
-1= Share all Pid's on card
-2= Share only following Pid's on card
-3= Don't share following Pid's on card
P is the Pid's
Another thing in the cwshare.cfg is the use of the ports.
There is absolutely no need to use a different port locally and remotely.
Both can be the same!
We all want as little ports open as possible, don´t we?
Well you can have lot´s of D lines all using the same Port(s).
GBOX Share/Reshare how is it done.
In the share/reshare concept there are two files we must fill
with the correct parameters
These files are: CWSHARE.CFG and GBOX.CFG
Depending on what gbox type is installed(windows,dream,Linux)
these files are either in the root directory or in VAR/KEYS.
CWSHARE.CFG
M:
M: { ipadress(alias) { password }
Ipadress(alias) can be LAN(10.x.x.x or 192.x.x.x) or WAN( 82.212.50.24 or myip.alias.com)
LAN is used for internal resharing. As an internal ipadress is used it wil only travel over the
local area network.
WAN is for internet sharing, ipadress can be the real adress like 82.x.x.x or a more meaningfull alias.
All internet traffic is encrypted by GBOX so it doesn´t really matter however numbers
are easier decrypted. The use of aliasses is recommended for WAN sharing.
D:
D: {something.dynalias.com { 4525 4526 { FFFF0065 { A5 A5 }}}}
What does this all mean?
1....{something.dynalias.com same as in M line
2................................................{ 4525 4526 myport friendsport
3................................................. ....................{ FFFF0065 password to be used at both ends
4................................................. ..........................................{ A5 A5 }}}} mylevel friendslevel
1 is explained in the M section
2 myport is the transmitting port friendsport is the listening port
2.a as these are Tx and Rx the D line at friends should be { 4526 4525 TX talks to Rx
3 password is in hexadecimal so A...F and 0...9 length must be 8
3.a never tried it but I believe it also has to be 4 characters and 4 digits
3.b uppercase lowercase distinction? Can´t tell maybe on a Linux system yes and Windows no
4 mylevel is the share level for LOCAL cards. A local card is a card which is in the ...Dreambox internal card reader slot(sc is the name used in gbox for the internal card rdr)
...friendslevel is the level for VIRTUAL cards. A virtual card is a card shared to you by a peer
4.a Levels are also in hexadecimal and specify the depth of sharing
.....A is used(in the NDS card owners D line to tell GBOX to change the ECM/EMM rate
.....0->9 are used where 0 means your local card is used only to decrypt and can´t be reshared
.....1 means your local card is shared to your friend but he can´t reshare
.....2 means your local card is shared to your friend and he can reshare it to his friends
.....3 same as 2 but the friend friends can reshare to their friends but they can´t reshare
.....4 same as 3 but well think you can figure this out now
.....9 would mean you share your local card to the whole world. DON´T do that!
5 friendslevel same as mylevel but for virtual cards
General remarks:
a level1 at mylevel will be received as an INTERNAL gbox level 0 at the friendslevel
INTERNAL meaning within the programm itself(re-sharing mechanism).
I:
I: { 06 } sets the maximum share depth you want to receive.
..............when set to 2 you will only receive ECM/EMM from peers at distance 2
..............in/decrease this number to get at the optimum number of cards
..............maximum number of cards is 1024 after that I will be set to 3 by the gbox programm
N:
N: { 01 01 00 3F 1500 3000 }
This is a very important parameter. Settings of it is done at byte position
N: { 01 is the first byte
Can be set to 00 every EMM is handled once only whether it opens the channel or not
......................01 EMM is repeated
N: { xx 01 is the second byte
Restart pid on overflow well so be it. Documentation does not say whether it can be set to 00
N: { xx xx 00 third byte
If the firmware of the receiver is capable of recognizing freezes it will reset the ENX and
you don´t have to switch up down a channel to resolve the freeze
N: { xx xx xx 3F fourth byte
This is used to configure what is written in attack.txt./online.log/share.stat
00 write nothing
01 password is wrong will be written in attack.tx
02 ID unknown will be written in attack.tx
04 IP is wrong will be written in attack.tx
08 Port is wrong will be written in attack.tx
20 create online.log come online/offline msg´s
1F all but the come online/oflline msg´s
3F all is written in to the log files
N: { xx xx xx xx 1500 fifth byte
It sets the repeat time for sending ECM´s in milli seconds to the internet.
N: { xx xx xx xx xxxx 3000 } sixth byte
Sets the resynchronisation time in milli seconds when internet decoding fails
X:
X: { 10 }
Sets how many cards wil receive a ECM request from you.
This option also influences the number of cards online to you cq channels which decode
W: is used for multicam a card reader device which can contain upto 8 cards
S: is the same as W but W uses pid information S uses sid information
G: is used to exclude cards example is old Irdeto or old Seca1 card
Y:
Y: { AD A7 }
Is used to exclude level 0 cards which can´t be reshared by a server but do count in the
number of cards which is limited to 1024.
AD A7 is the card id to be excluded.
Makes no sense to include these lines in a receiver only set up as a level 0 still decodes the
channels serviced on that card.
This concludes the cwshare.cfg part.
Only those parameters which matter to our setup have been detailed.
Now lets take a look at the gbox.cfg
First let me say something about the F parameter
F is short for MODIFY now the F makes sense to me important things are bold
# gbox config file
# Trace/Debug
# xx yz ; xx=00 no konsole output
# xx yz ; xx=01 konsole output
# xx yz ; y=0 debug output (don't use)
# xx yz ; y=1 no debug output
# xx yz ; z=0 ouput to konsole
# xx yz ; z=1 output to /var/tmp/debug.txt
# xx yz ; z=2 Output to UDP (to capture with gboxt)
Z: { 01 10 } 192.168.1.29 8024
Useful to find what is wrong
# Task type
# 00 ** normal mode gbox mode (no season, use Multicam instead)
# 01 ** Season Emulation in a Irdeto allcam chid 0602 nonZ
# 10 ** Season Emulation in a Irdeto allcam chid 1702 nonZ
# 11 ** Season Emulation in a Irdeto allcam chid 1702 Z
# 12 ** Season Emulation in a Irdeto allcam chid 1722 Z
# 13 ** Season Emulation in a Irdeto allcam chid 1762 Z
# ** *1 Com port to use for season emulatiom (1 or 2)
# ** 0* Use CTS fﾁr RST detection
# ** 1* Use DCD fﾁr RST detection
# ** ** 9600 = Baudrate to be used (working only on dbox2)
W: { 00 00 } 9600
# gbox working mode
# 00 pure Emu
# 01 pure SoftCam (when card inside), Emu (when no card inside)
# 02 pure Net Client
# 03 Mixed mode !!!!! always use this !!!!!
G: { 03 }
# Display ECM messages on Konsole
# 00 don't show any ECM's
# 01 show only valid ECM's
# 02 show valid and bad ECM's with complete data display
C: { 00 }
# Display EMM messages on Konsole
# *0 don't show any EMM's
# *1 show only valid EMM's
# *2 show valid and bad EMM's with complete data display
# 1* Log any tier change on PW-Nagra-17xx cards into /var/keys/pwupdate.log
M: { 00 }
# AutoUpdate
# 00 is ignored (default)
# 01 enable AU
# 02 Auto AU !!!!! always use this !!!!!
A: { 02 }
Make sure your card gets its updates
# Key update
# 01 update only new keys, default setting
# 02 update all keys (used for valid PMK checking)
U: { 01 }
# Hash pids
# 00 hash all pids, DO NOT USE THIS OPTION, IT IS ONLY FOR TESTING STUFF
# 01 hash only pids with implemented algos and available keys !!!!! always use this !!!!!
H: { 01 }
# Key files folder
# 00 keyfiles in /var/keys
# 01 keyfiles in /var/tmp
T: { 01 }
# On Screen Display for the Multysystemcam on com1/com2
# 00 No OSD (default)
# 01 display Smartcard messages in Neutrino
# 02 display Smartcard messages in Neutrino new nhttpd format
# 03 display Smartcard messages in Enigma
# mypass (use user=root and pass=mypass for nhttpd)
O: { 01 } 192.168.1.51
# Logger and NET-mode UDP port Init
# 00 do not init UDP port
# 01 Init UDP port for IP, port, UDP
L: { 00 } 192.168.1.29 8017
# demux, multicam/comport configuration
# *x ** ; x = device nummber to be used (0= default)
# D* ** ; force use of /proc/bus/gtx for cw write operations
(in the dbox2 the gbox writes directly the CW's, 00 is the
recommended mode ! No drivers are required) use D* ** ONLY if
you have Problems. 0* ** should be prefered !!!
# F* ** ; write CW's in both devices (used for PVR in STB04xxx devices)
# ** y* ; y=0001b (0x1*) use slot1 as Multicam (only on STB04xxx)
# ** y* ; y=0010b (0x2*) use slot2 as Multicam (only on STB04xxx)
# ** y* ; y=0011b (0x3*) use slot1 and slot2 as Multicams (only on STB04xxx)
# ** *z ; z=0001b (0x*1) use com1 as Multicam
# ** *z ; z=0010b (0x*2) use com2 as Multicam
# ** *z ; z=0011b (0x*3) use com1 and com2 as Multicams
# ** yz ; yz=00110011b (0x33) use slot1+slot2+com1+com2 as Multicams
# ** *z ; z=0100b (0x*4) invert CTS detection on com1
# ** *z ; z=1000b (0x* invert CTS detection on com2
# example: yz = 0x0A = 00001010 (use com2 with inverted CTS detection line)
V: { 00 02 }
V: { 00 36 } 00 use slot1/2 as multicams this enables the internal card reader of the Dream
# ================================================== ===========================
# extra options to override default seting in case you expirience Problems,
# normaly these setings are not required.
#
# cpu, api, cw write method
#
# 00 auto
# 01 80X86
# 02 MPC823
# 03 IBM STB04xxx
# 00 auto
# 01 ibm
# 02 api2
# 03 api3
# 00 cw write style = use internal routine (only dbox2)
# 01 cw write style = CA_SET_DESCR type1 (dbox2, vdr)
# 02 cw write style = CA_SET_DESCR type2
# 03 cw write style = CA_SET_DESCR type3
# 04 cw write style = 16 byte /proc/bus/gtx
# 05 cw write style = 4096 byte /proc/bus/gtx, cw offset=0x04D0
# xx write cw in 1st device with index=xx
# yy write cw in 2nd device with index=yy
# 01 means with .index=0 (default)
# 02 means with .index=1
# 03 means with .index=0 and .index=1
# .. any bitwise combination ...
# FF means with all 8 indexes (0-7)
#J: { 01 00 00 01 01 }
# Files, folders, devices
# folder/device comment
#
#F: { 01 } /var/tmp/pmt.tmp // pmt file
#F: { 02 } /var/tmp/emm.info // key update log file
#F: { 03 } /var/tmp/ecm.info // ecm info file
#F: { 04 } /var/tmp/atack.txt // atack info file
#F: { 11 } /var/keys // folder for config files
#F: { 12 } /var/tmp // folder for temporary file
#F: { 13 } /var/tmp // folder for keyfiles
#F: { 21 } /dev/dvb/adapter0/ca0 // ca device
#F: { 22 } /dev/dvb/adapter0/dvr0 // dvr device
#F: { 23 } /dev/dvb/adapter0/demux0 // demux device
#F: { 31 } /dev/dvb/adapter0/ca1 // second ca device to write cw's (recording)
#F: { 41 } /dev/sci0 // STB04xxx slot1
#F: { 42 } /dev/sci1 // STB04xxx slot1
#F: { 43 } /dev/tts/0 // rs232 com1
#F: { 44 } /dev/tts/1 // rs232 com2
# For overclocking freaks, Clocking internal STB04xxx slots with:
# 1=7.80MHz 2=6.30MHz 3=5.25MHz 4=4.50MHz 5=3.94MHz 6=3.50MHz 7=3.15MHz
# Irdeto works fine on 7.8MHz, all other fine on 6.30MHz or 5.25MHz
# The Dream has not a clean clock signal, some cards that are sensitive will
# refuse to work even on 3.5MHz, thats why 3.15MHz is the default value there.
# On other STB04xxx recievers the same cards work with 6.30MHz
#
#F: { 51 } 02 // irdeto
#F: { 52 } 03 // seca
#F: { 53 } 03 // viaccess
#F: { 54 } 03 // nagra
#F: { 55 } 03 // crypto
#F: { 57 } 03 // conax
#F: { 58 } 03 // nds
EUCardsharing
Re: W in cwshare.cfg
The W line decides how your local card shall be used and shared on the network, and goes
in cwshare.cfg like this:
W: { 0A 0B 0C } P001 P002 P003 ...
A= Slot number (1 to 8 )
B= How your card shall be used locally (on your own box)
-0= Dont use card
-1= Use card for all Pid's
-2= Use card only for following Pid's
-3= Don't use card for following Pid's
C= How the card shall be shared on the network
-0= Dont share card
-1= Share all Pid's on card
-2= Share only following Pid's on card
-3= Don't share following Pid's on card
P is the Pid's
Example 1: I want my card in slot 1 to be used for all Pid's locally, and to be shared
on the network with all Pid's ( 1FFF means all Pid's):
W: { 01 01 01 } 1FFF
Example 2: I want my card in slot 1 to be used locally for all Pid's on card, and DONT want
it to be shared on the network at all:
W: { 01 01 00 } 1FFF
Example 3: I want my card in slot 1 to be used locally with the following Pids only, and to
be shared on the network too with the following Pid's only:
W: { 01 02 02 } Pid1 Pid2 Pid3 ...
rk, and goes in cwshare.cfg like this:
W: { 0A 0B 0C } P001 P002 P003 ...
A= Slot number (1 to 8 )
B= How your card shall be used locally (on your own box)
-0= Dont use card
-1= Use card for all Pid's
-2= Use card only for following Pid's
-3= Don't use card for following Pid's
C= How the card shall be shared on the network
-0= Dont share card
-1= Share all Pid's on card
-2= Share only following Pid's on card
-3= Don't share following Pid's on card
P is the Pid's
Another thing in the cwshare.cfg is the use of the ports.
There is absolutely no need to use a different port locally and remotely.
Both can be the same!
We all want as little ports open as possible, don´t we?
Well you can have lot´s of D lines all using the same Port(s).
GBOX Share/Reshare how is it done.
In the share/reshare concept there are two files we must fill
with the correct parameters
These files are: CWSHARE.CFG and GBOX.CFG
Depending on what gbox type is installed(windows,dream,Linux)
these files are either in the root directory or in VAR/KEYS.
CWSHARE.CFG
M:
M: { ipadress(alias) { password }
Ipadress(alias) can be LAN(10.x.x.x or 192.x.x.x) or WAN( 82.212.50.24 or myip.alias.com)
LAN is used for internal resharing. As an internal ipadress is used it wil only travel over the
local area network.
WAN is for internet sharing, ipadress can be the real adress like 82.x.x.x or a more meaningfull alias.
All internet traffic is encrypted by GBOX so it doesn´t really matter however numbers
are easier decrypted. The use of aliasses is recommended for WAN sharing.
D:
D: {something.dynalias.com { 4525 4526 { FFFF0065 { A5 A5 }}}}
What does this all mean?
1....{something.dynalias.com same as in M line
2................................................{ 4525 4526 myport friendsport
3................................................. ....................{ FFFF0065 password to be used at both ends
4................................................. ..........................................{ A5 A5 }}}} mylevel friendslevel
1 is explained in the M section
2 myport is the transmitting port friendsport is the listening port
2.a as these are Tx and Rx the D line at friends should be { 4526 4525 TX talks to Rx
3 password is in hexadecimal so A...F and 0...9 length must be 8
3.a never tried it but I believe it also has to be 4 characters and 4 digits
3.b uppercase lowercase distinction? Can´t tell maybe on a Linux system yes and Windows no
4 mylevel is the share level for LOCAL cards. A local card is a card which is in the ...Dreambox internal card reader slot(sc is the name used in gbox for the internal card rdr)
...friendslevel is the level for VIRTUAL cards. A virtual card is a card shared to you by a peer
4.a Levels are also in hexadecimal and specify the depth of sharing
.....A is used(in the NDS card owners D line to tell GBOX to change the ECM/EMM rate
.....0->9 are used where 0 means your local card is used only to decrypt and can´t be reshared
.....1 means your local card is shared to your friend but he can´t reshare
.....2 means your local card is shared to your friend and he can reshare it to his friends
.....3 same as 2 but the friend friends can reshare to their friends but they can´t reshare
.....4 same as 3 but well think you can figure this out now
.....9 would mean you share your local card to the whole world. DON´T do that!
5 friendslevel same as mylevel but for virtual cards
General remarks:
a level1 at mylevel will be received as an INTERNAL gbox level 0 at the friendslevel
INTERNAL meaning within the programm itself(re-sharing mechanism).
I:
I: { 06 } sets the maximum share depth you want to receive.
..............when set to 2 you will only receive ECM/EMM from peers at distance 2
..............in/decrease this number to get at the optimum number of cards
..............maximum number of cards is 1024 after that I will be set to 3 by the gbox programm
N:
N: { 01 01 00 3F 1500 3000 }
This is a very important parameter. Settings of it is done at byte position
N: { 01 is the first byte
Can be set to 00 every EMM is handled once only whether it opens the channel or not
......................01 EMM is repeated
N: { xx 01 is the second byte
Restart pid on overflow well so be it. Documentation does not say whether it can be set to 00
N: { xx xx 00 third byte
If the firmware of the receiver is capable of recognizing freezes it will reset the ENX and
you don´t have to switch up down a channel to resolve the freeze
N: { xx xx xx 3F fourth byte
This is used to configure what is written in attack.txt./online.log/share.stat
00 write nothing
01 password is wrong will be written in attack.tx
02 ID unknown will be written in attack.tx
04 IP is wrong will be written in attack.tx
08 Port is wrong will be written in attack.tx
20 create online.log come online/offline msg´s
1F all but the come online/oflline msg´s
3F all is written in to the log files
N: { xx xx xx xx 1500 fifth byte
It sets the repeat time for sending ECM´s in milli seconds to the internet.
N: { xx xx xx xx xxxx 3000 } sixth byte
Sets the resynchronisation time in milli seconds when internet decoding fails
X:
X: { 10 }
Sets how many cards wil receive a ECM request from you.
This option also influences the number of cards online to you cq channels which decode
W: is used for multicam a card reader device which can contain upto 8 cards
S: is the same as W but W uses pid information S uses sid information
G: is used to exclude cards example is old Irdeto or old Seca1 card
Y:
Y: { AD A7 }
Is used to exclude level 0 cards which can´t be reshared by a server but do count in the
number of cards which is limited to 1024.
AD A7 is the card id to be excluded.
Makes no sense to include these lines in a receiver only set up as a level 0 still decodes the
channels serviced on that card.
This concludes the cwshare.cfg part.
Only those parameters which matter to our setup have been detailed.
Now lets take a look at the gbox.cfg
First let me say something about the F parameter
F is short for MODIFY now the F makes sense to me important things are bold
# gbox config file
# Trace/Debug
# xx yz ; xx=00 no konsole output
# xx yz ; xx=01 konsole output
# xx yz ; y=0 debug output (don't use)
# xx yz ; y=1 no debug output
# xx yz ; z=0 ouput to konsole
# xx yz ; z=1 output to /var/tmp/debug.txt
# xx yz ; z=2 Output to UDP (to capture with gboxt)
Z: { 01 10 } 192.168.1.29 8024
Useful to find what is wrong
# Task type
# 00 ** normal mode gbox mode (no season, use Multicam instead)
# 01 ** Season Emulation in a Irdeto allcam chid 0602 nonZ
# 10 ** Season Emulation in a Irdeto allcam chid 1702 nonZ
# 11 ** Season Emulation in a Irdeto allcam chid 1702 Z
# 12 ** Season Emulation in a Irdeto allcam chid 1722 Z
# 13 ** Season Emulation in a Irdeto allcam chid 1762 Z
# ** *1 Com port to use for season emulatiom (1 or 2)
# ** 0* Use CTS fﾁr RST detection
# ** 1* Use DCD fﾁr RST detection
# ** ** 9600 = Baudrate to be used (working only on dbox2)
W: { 00 00 } 9600
# gbox working mode
# 00 pure Emu
# 01 pure SoftCam (when card inside), Emu (when no card inside)
# 02 pure Net Client
# 03 Mixed mode !!!!! always use this !!!!!
G: { 03 }
# Display ECM messages on Konsole
# 00 don't show any ECM's
# 01 show only valid ECM's
# 02 show valid and bad ECM's with complete data display
C: { 00 }
# Display EMM messages on Konsole
# *0 don't show any EMM's
# *1 show only valid EMM's
# *2 show valid and bad EMM's with complete data display
# 1* Log any tier change on PW-Nagra-17xx cards into /var/keys/pwupdate.log
M: { 00 }
# AutoUpdate
# 00 is ignored (default)
# 01 enable AU
# 02 Auto AU !!!!! always use this !!!!!
A: { 02 }
Make sure your card gets its updates
# Key update
# 01 update only new keys, default setting
# 02 update all keys (used for valid PMK checking)
U: { 01 }
# Hash pids
# 00 hash all pids, DO NOT USE THIS OPTION, IT IS ONLY FOR TESTING STUFF
# 01 hash only pids with implemented algos and available keys !!!!! always use this !!!!!
H: { 01 }
# Key files folder
# 00 keyfiles in /var/keys
# 01 keyfiles in /var/tmp
T: { 01 }
# On Screen Display for the Multysystemcam on com1/com2
# 00 No OSD (default)
# 01 display Smartcard messages in Neutrino
# 02 display Smartcard messages in Neutrino new nhttpd format
# 03 display Smartcard messages in Enigma
# mypass (use user=root and pass=mypass for nhttpd)
O: { 01 } 192.168.1.51
# Logger and NET-mode UDP port Init
# 00 do not init UDP port
# 01 Init UDP port for IP, port, UDP
L: { 00 } 192.168.1.29 8017
# demux, multicam/comport configuration
# *x ** ; x = device nummber to be used (0= default)
# D* ** ; force use of /proc/bus/gtx for cw write operations
(in the dbox2 the gbox writes directly the CW's, 00 is the
recommended mode ! No drivers are required) use D* ** ONLY if
you have Problems. 0* ** should be prefered !!!
# F* ** ; write CW's in both devices (used for PVR in STB04xxx devices)
# ** y* ; y=0001b (0x1*) use slot1 as Multicam (only on STB04xxx)
# ** y* ; y=0010b (0x2*) use slot2 as Multicam (only on STB04xxx)
# ** y* ; y=0011b (0x3*) use slot1 and slot2 as Multicams (only on STB04xxx)
# ** *z ; z=0001b (0x*1) use com1 as Multicam
# ** *z ; z=0010b (0x*2) use com2 as Multicam
# ** *z ; z=0011b (0x*3) use com1 and com2 as Multicams
# ** yz ; yz=00110011b (0x33) use slot1+slot2+com1+com2 as Multicams
# ** *z ; z=0100b (0x*4) invert CTS detection on com1
# ** *z ; z=1000b (0x* invert CTS detection on com2
# example: yz = 0x0A = 00001010 (use com2 with inverted CTS detection line)
V: { 00 02 }
V: { 00 36 } 00 use slot1/2 as multicams this enables the internal card reader of the Dream
# ================================================== ===========================
# extra options to override default seting in case you expirience Problems,
# normaly these setings are not required.
#
# cpu, api, cw write method
#
# 00 auto
# 01 80X86
# 02 MPC823
# 03 IBM STB04xxx
# 00 auto
# 01 ibm
# 02 api2
# 03 api3
# 00 cw write style = use internal routine (only dbox2)
# 01 cw write style = CA_SET_DESCR type1 (dbox2, vdr)
# 02 cw write style = CA_SET_DESCR type2
# 03 cw write style = CA_SET_DESCR type3
# 04 cw write style = 16 byte /proc/bus/gtx
# 05 cw write style = 4096 byte /proc/bus/gtx, cw offset=0x04D0
# xx write cw in 1st device with index=xx
# yy write cw in 2nd device with index=yy
# 01 means with .index=0 (default)
# 02 means with .index=1
# 03 means with .index=0 and .index=1
# .. any bitwise combination ...
# FF means with all 8 indexes (0-7)
#J: { 01 00 00 01 01 }
# Files, folders, devices
# folder/device comment
#
#F: { 01 } /var/tmp/pmt.tmp // pmt file
#F: { 02 } /var/tmp/emm.info // key update log file
#F: { 03 } /var/tmp/ecm.info // ecm info file
#F: { 04 } /var/tmp/atack.txt // atack info file
#F: { 11 } /var/keys // folder for config files
#F: { 12 } /var/tmp // folder for temporary file
#F: { 13 } /var/tmp // folder for keyfiles
#F: { 21 } /dev/dvb/adapter0/ca0 // ca device
#F: { 22 } /dev/dvb/adapter0/dvr0 // dvr device
#F: { 23 } /dev/dvb/adapter0/demux0 // demux device
#F: { 31 } /dev/dvb/adapter0/ca1 // second ca device to write cw's (recording)
#F: { 41 } /dev/sci0 // STB04xxx slot1
#F: { 42 } /dev/sci1 // STB04xxx slot1
#F: { 43 } /dev/tts/0 // rs232 com1
#F: { 44 } /dev/tts/1 // rs232 com2
# For overclocking freaks, Clocking internal STB04xxx slots with:
# 1=7.80MHz 2=6.30MHz 3=5.25MHz 4=4.50MHz 5=3.94MHz 6=3.50MHz 7=3.15MHz
# Irdeto works fine on 7.8MHz, all other fine on 6.30MHz or 5.25MHz
# The Dream has not a clean clock signal, some cards that are sensitive will
# refuse to work even on 3.5MHz, thats why 3.15MHz is the default value there.
# On other STB04xxx recievers the same cards work with 6.30MHz
#
#F: { 51 } 02 // irdeto
#F: { 52 } 03 // seca
#F: { 53 } 03 // viaccess
#F: { 54 } 03 // nagra
#F: { 55 } 03 // crypto
#F: { 57 } 03 // conax
#F: { 58 } 03 // nds
EUCardsharing
Gbox Tutorial
http://www.eucardsharing.com
Before I start to write the How to I decided to describe first the necessarily steps to build a gbox server. So don't except How to with all Details. The questions about gbox server will show which details will be needed.
1. Get the files
2. Put the files in the right folders
3. Make the needed configuration
4. add and exchange dlines
5. control your gbox
6. possible errors and reasons
1. First download all files from the following link
Gbox2.1b
2.Extract the files and you will see also the path where the files should be put
//var/bin => gbox
//var/keys => cwshare.cfg,gbox.cfg,softcam.cfg
//var/script => gbox_cam.sh
//var/tuxbox/plugins => egboxcenter.cfg,egboxcenter.so,gboxsuite.cfg, egboxsuite.so, gbv.cfg,gbv.ident,gbv.so
Use a Ftp program to put the files in the folders. I prefer flashfxp. After you had put the files in the folders. Make CHMOD changes for the following files. You can make the CHMOD changes by using the right mouse button (FLASHFXP) on the file and selecting Attribute (CHMOD).
//var/bin/gbox => CHMOD 755
//var/keys => cwshare.cfg => 644
//var/keys => gbox_cfg => 644
//var/scripts => gbox_cam.sh => 755
3. Coniguration
You must made only individual changes to cwshare.cfg and gbox_cfg
CWSHARE:
This file is responsbile for communication between the peers.
Following lines should be inside this files
M: => Adress of your gbox
I: => Configuration about till which distance cards you allows to get
X: => Configuration abotu how many of the same card you allows to get
D: => Communication line between the peers
N: =>
W: =>
How should the lines be set:
M-LIne
M: { your.dyndns.org { Password }}
=> Password: You can only use 0-9 and A-F for setting password. My suggestion is don't use a very very easy password like 12345678 or AABBCCDD or ABCD1234, so a lot of people makes that and this can be a reason for an error, if you start the gbox. More details at the end.
I-Line
I: { 03 }
This is the selected value most gbox user set for their I-Line. Because with this configuration you only accept cards till Dist3. Cards with Dist4 and Dist5 are not good for sharing and gettings keys. If you have later more peers you can set the value to 02.
X-Line
X: { 10 }
This is a value should experiment a little bit which value is the best for your gbox server. As you know with this value you set a limit to the number of same cards. 0A, 10, 08 this are the most used values.
N-Line
N: { 00 01 03 3F 4000 6000 }
I will write more details to this line. Use the N-Line given above ( its my N-Line)
W-Line
W: { 01 01 01 } 1FFF
I will write more details to this line. Use the N-Line given above ( its my N-Line)
D-Line
This is the most importan Line
D: { other.dyndns.org { Port1 Port2 { Password { A5 A5 }}}}
other.dyndns.org => the dyndns of your share peer
port1 => your port number using for gbox
port2 => port number of you peer
Password => password of your peer
A5 A5 => Share Level for Local and Virtual Cards
You will get this dline every time for your peer. So the only thing you had to do is, to put your port number instead of port1 and add it in your cwshare.cfg. The Dline you give to your peer is the the same but with your dyndns, password and your port number is port2.
D: { own.dyndns.org { Port1 ownport { own password { A5 A5 }
GBOX_CFG
In your gbox_cfg file you have following lines
Z: { 01 12 } dream ip 8024
G: { 03 }
C: { 01 }
M: { 01 }
A: { 00 }
U: { 01 }
H: { 01 }
T: { 00 }
O: { 03 } dream ip
L: { 00 } dream ip 8029
W: { 00 00 } 9600
V: { F0 35 } => configurations for reading slot and com-ports
V: { F0 00 } nothing
V: { F0 10 } slot 1
V: { F0 20 } slot 2
V: { F0 30 } both slots
V: { F0 35 } both slots + com ports
V: { F0 05 } only com ports
V: { F0 31 } Sc8in1
V: { 00 05 } Dbox2 multicam
I will made later a detailed description for this file. The informations above are taken from my gbox_cfg
4. Add and exchange Dlines
After ending configuration you can now exchange dlines
M: { own.dyndns.org { password }}
# Internet Friends port range password cod
I: { 2 }
X: { 0A }
N: { 00 01 03 3F 4000 6000 }
W: { 01 01 01 } 1FFF
D: { other.dyndns.org { yourport otherport { otherpassword { A5 A5 }}}}
Be carefull if you add dlines it must the same like above. No more spaces or less spaces
5. Control Gbox and peers
Gbox Center and Gbox Suite are plugins to have Informations about your peers, Cards, Distance and Level Share and how many cards do you have for each provider
You can access to this plugins
Blue Panel => Plugins => Gbox Center or Gbox Suite
6. Error and Reasons
If your gbox is not working ( you will see it if you go to: Blue Panel => Plugins => Gbox Center => Gbox Share Center => Peer Status => Message that share is not found, check if gbox is running )
Then check following
1. Internet Connection
2. Correct format of dlines ( Spaces, password (0-9,A-F) )
3. Passwords of the dline ( so if two peers use the same password they will get the same Box ID and two same Box ID in one Gbox Server is not working)
4. Some Cards needs special configuration to share them ( Sky Uk, Nova etc)
http://www.eucardsharing.com
Before I start to write the How to I decided to describe first the necessarily steps to build a gbox server. So don't except How to with all Details. The questions about gbox server will show which details will be needed.
1. Get the files
2. Put the files in the right folders
3. Make the needed configuration
4. add and exchange dlines
5. control your gbox
6. possible errors and reasons
1. First download all files from the following link
Gbox2.1b
2.Extract the files and you will see also the path where the files should be put
//var/bin => gbox
//var/keys => cwshare.cfg,gbox.cfg,softcam.cfg
//var/script => gbox_cam.sh
//var/tuxbox/plugins => egboxcenter.cfg,egboxcenter.so,gboxsuite.cfg, egboxsuite.so, gbv.cfg,gbv.ident,gbv.so
Use a Ftp program to put the files in the folders. I prefer flashfxp. After you had put the files in the folders. Make CHMOD changes for the following files. You can make the CHMOD changes by using the right mouse button (FLASHFXP) on the file and selecting Attribute (CHMOD).
//var/bin/gbox => CHMOD 755
//var/keys => cwshare.cfg => 644
//var/keys => gbox_cfg => 644
//var/scripts => gbox_cam.sh => 755
3. Coniguration
You must made only individual changes to cwshare.cfg and gbox_cfg
CWSHARE:
This file is responsbile for communication between the peers.
Following lines should be inside this files
M: => Adress of your gbox
I: => Configuration about till which distance cards you allows to get
X: => Configuration abotu how many of the same card you allows to get
D: => Communication line between the peers
N: =>
W: =>
How should the lines be set:
M-LIne
M: { your.dyndns.org { Password }}
=> Password: You can only use 0-9 and A-F for setting password. My suggestion is don't use a very very easy password like 12345678 or AABBCCDD or ABCD1234, so a lot of people makes that and this can be a reason for an error, if you start the gbox. More details at the end.
I-Line
I: { 03 }
This is the selected value most gbox user set for their I-Line. Because with this configuration you only accept cards till Dist3. Cards with Dist4 and Dist5 are not good for sharing and gettings keys. If you have later more peers you can set the value to 02.
X-Line
X: { 10 }
This is a value should experiment a little bit which value is the best for your gbox server. As you know with this value you set a limit to the number of same cards. 0A, 10, 08 this are the most used values.
N-Line
N: { 00 01 03 3F 4000 6000 }
I will write more details to this line. Use the N-Line given above ( its my N-Line)
W-Line
W: { 01 01 01 } 1FFF
I will write more details to this line. Use the N-Line given above ( its my N-Line)
D-Line
This is the most importan Line
D: { other.dyndns.org { Port1 Port2 { Password { A5 A5 }}}}
other.dyndns.org => the dyndns of your share peer
port1 => your port number using for gbox
port2 => port number of you peer
Password => password of your peer
A5 A5 => Share Level for Local and Virtual Cards
You will get this dline every time for your peer. So the only thing you had to do is, to put your port number instead of port1 and add it in your cwshare.cfg. The Dline you give to your peer is the the same but with your dyndns, password and your port number is port2.
D: { own.dyndns.org { Port1 ownport { own password { A5 A5 }
GBOX_CFG
In your gbox_cfg file you have following lines
Z: { 01 12 } dream ip 8024
G: { 03 }
C: { 01 }
M: { 01 }
A: { 00 }
U: { 01 }
H: { 01 }
T: { 00 }
O: { 03 } dream ip
L: { 00 } dream ip 8029
W: { 00 00 } 9600
V: { F0 35 } => configurations for reading slot and com-ports
V: { F0 00 } nothing
V: { F0 10 } slot 1
V: { F0 20 } slot 2
V: { F0 30 } both slots
V: { F0 35 } both slots + com ports
V: { F0 05 } only com ports
V: { F0 31 } Sc8in1
V: { 00 05 } Dbox2 multicam
I will made later a detailed description for this file. The informations above are taken from my gbox_cfg
4. Add and exchange Dlines
After ending configuration you can now exchange dlines
M: { own.dyndns.org { password }}
# Internet Friends port range password cod
I: { 2 }
X: { 0A }
N: { 00 01 03 3F 4000 6000 }
W: { 01 01 01 } 1FFF
D: { other.dyndns.org { yourport otherport { otherpassword { A5 A5 }}}}
Be carefull if you add dlines it must the same like above. No more spaces or less spaces
5. Control Gbox and peers
Gbox Center and Gbox Suite are plugins to have Informations about your peers, Cards, Distance and Level Share and how many cards do you have for each provider
You can access to this plugins
Blue Panel => Plugins => Gbox Center or Gbox Suite
6. Error and Reasons
If your gbox is not working ( you will see it if you go to: Blue Panel => Plugins => Gbox Center => Gbox Share Center => Peer Status => Message that share is not found, check if gbox is running )
Then check following
1. Internet Connection
2. Correct format of dlines ( Spaces, password (0-9,A-F) )
3. Passwords of the dline ( so if two peers use the same password they will get the same Box ID and two same Box ID in one Gbox Server is not working)
4. Some Cards needs special configuration to share them ( Sky Uk, Nova etc)
http://www.eucardsharing.com
How to install Gbox on a Windows PC
Here are som info on how to install Gbox on a Windows PC.
Download GBox 2.1B her:
LINK
On the PC make following folders
\var
\var\bin
\var\keys
\var\tmp
Copy files from the zip file folder \gbox\x86\windows to folder
\var\bin
Copy files from the zip file \gbox\keys to
\var\keys
Edit \var\keys\cwshare.cfg and \var\keys\gbox_cfg to fit your configuration.
Run \var\bin\gboxx86.exe
EUCardsharing
Download GBox 2.1B her:
LINK
On the PC make following folders
\var
\var\bin
\var\keys
\var\tmp
Copy files from the zip file folder \gbox\x86\windows to folder
\var\bin
Copy files from the zip file \gbox\keys to
\var\keys
Edit \var\keys\cwshare.cfg and \var\keys\gbox_cfg to fit your configuration.
Run \var\bin\gboxx86.exe
EUCardsharing
Thursday, September 11, 2008
How to install a CCcam server on Windows XP
In this tutorial, we are going to install and run a CCcam server on Windows XP, and as we know CCcam is programmed to run on Linux, well, it's still the case here and in order to install our server, we have to run CCcam on a Virtual Machine (VM) that has a Linux OS installed on it
The trick is not installing Linux on Windows XP and running it as a VM, many do that already using VMware Player or Microsoft Virtual PC,the trick is to make this VM be fully recognized by Windows XP and it self as a server that has it's own physical MAC-address and thereby it's own IP in the router.
To sum it all, we are going to trick the router that we are running a physical PC somewhere and that PC is physically connected to that router, in order to obtain an IP in the router so the Virtual Linux OS (OS means Operating System such as Windows XP, Vista, Ubunto, Opensuse..etc), can send and receive data over that router, and in this tutorial we are going to use Clarkconnect as a Virtual Linux OS.
I choose Clarkconnect as a Virtual server because it's secure, small, fast, stable and does not require much of disk space or RAM, don't be surprised if we used 2GB of hard disk space along with only 512MB RAM and our Clarkconnect Virtual server will actually only uses less than half of the disk space and about 250 MB of the RAM we are going to allocate for this Virtual Server.
If that have given an idea of what we are going to do then lets get started...we need tools do so...
The tools:
1: Clarkconnect Community Edition 4.2 SP1 as Virtual OS
http://www.clarkconnect.com/downloads/isos.php
2: VMware Player as our VM ( Requires a small registration )
http://www.vmware.com/download/player/
3: Pre-configured Clarkconnect VMware Virtual disk and configuration files (32-bit)
http://rapidshare.com/files/135584513/Clarkconnect_VMX_pre_configured.zip.html
Specifications:
32Bit Guest VM
One CPU and 512MB of RAM
One Hard disk of 2GB space
One physical CD/DVD-ROM
One virtual CD/DVD-ROM
One Bridged network adapter ( bridged to VMnet0 )
One Serial Port ( COM1 )
One USB controller
( MD5 checksum = 7c54a3017fcd173f4495e0116db61f2f *Clarkconnect_VMX_pre_configured.zip )
4: VMXBuilder as a VMware Virtual disk and configuration file builder
http://rapidshare.com/files/135584738/VMXBuilderSetup.zip.html
( MD5 checksum = ffb73f78b9fd1cf444c8232719d872de *VMXBuilderSetup.zip )
5: CCcam CS program
http://www.eucardsharing.com/index.php?action=tpmod;dl=item5
6: An FTP client program
http://www.filezilla.com
7: Putty to configure and start our CCcam server
http://rapidshare.com/files/130837134/putty.zip.html
Optional
1: TrayIt!, the program sends any running program on taskbar to the system tray
Download
2: USB development package V.0.1.12
Download
( MD5 checksum = caf182cbc7565dac0fd72155919672e6 *libusb-0.1.12.tar.gz )
3: Nftytool for Infinity USB Phoenix Card-reader V.1.1
Download
P.S. The MD5 checksums for the archives above are not passwords, they are to are there to confirm that the archives are uploaded by me and if an archive doesn't carry that hash-number I have provided here for it then the archive is not mine and have been modified by someone else, you can use MD5summer (Home of the MD5summer) to make sure of that.
Before we start:
I would like to inform a little about Clarkconnect VMware Virtual disk and configuration files provided for download above:
These are made using VMXBuilder, the easyvmx site that I have linked to in the earlier version in this tutorial is actually using VMXBuilder to generate the VMware configuration files without mentioning this program at all and I thought, as all of you, that they stood behind the development of the VMware configuration files but they are not.
I found about that when I started searching the internet to see if any others are facing the same problem as we have due to the COM-port in the Virtual Server created does not work at all, and that means that the there is something wrong with the VMware configuration for the COM-port, however, I found the authors homepage after much searching and along with that, I found out that they have been working on VMXBuilder since 11/05/2005.
LINK
After using this program to generate the configuration files I have no problem using the COM-port which now works flawlessly, and as you can see, the credit should go for the guys that stand behind this project and not for easyvmx.
Later on, I'm going to guide you through VMXBuilder and you can then make your own configurations using VMBuilder if you decide to use another OS than Clarkconnect or you have another Host OS than Windows XP.
Let's get started....
1. Configuring Network adapters:
*These steps are very important*
1. Install VMware Player on your system, when done, head over to Network Connections in Control Panel,right-click your physical network adapter and choose Properties...make sure that VMware Bridge Protocol is checked, if not, check it and hit OK as shown below..
2. Brows to : Program Files\VMware\VMware Player folder and click on vmnetcfg, when it starts choose the tab Host Virtual Network Mapping and change VMnet0 from Briged to an automaticlly chosen adapter to your own physical network adapter, hit Apply and OK..
3.Create a folder on drive C:\ and name it Clarkconnect, then extract the archive Clarkconnect_VMX_pre_configured.zip and copy the content of the folder to the Clarkconnect folder we created earlier on drive C:\, when done copy "community-4.2.SP1.iso" to the the same folder and rename the iso-image to Clarkconnect.
* You can burn the community-4.2.SP1.iso to a CD and install from your CD/DVD Drive if you want, but I have chosen to use the VMwares own virtual CD-ROM drive because it's faster, and that's why I choose to copy community-4.2.SP1.iso to the Clarkconnect folder on drive C:\.
2. Configuring and making the VMware configuration file:
Install VMXBuilder and run the program
The porgram should place a shortcut on your Desktop, otherwise, the program is located on Start ->All Programs ->RDPSoftware ->VMware ->VMXBuilder
Choose Create New Virtual Machine
Choose the location you want to save the configurations files to
*It will be easier to save them to your Desktop now and move them later, otherwise, you should save them to the location of your Guest-OS installation directory, it's C:\Clarkconnect in this tutorial.
Choose a name for you Virtual Machine
As showen below on the Options-Tab on General options, I changed the VM and VMX-file names to the name of the ISO-image that I'm using.
It's important that the Target Platform is : Workstation and the Version is : 5.5 , that will make the configuration flexible, it's still targeted at VMware Workstation version but we will still be able to use it with the VMware Player. The Guest-OS should be Linux.
The Kernel version of the Clarkconnect I'm installing is 2.6 , if you are installing an other Linux Guest-OS then you should follow your Guest-OS Kernel.
The Working Directory should be the location of your Guest-OS installation directory.
Change to the Hardware-Tab, I'm naming the Virtual Motherboard here.
As we are using the Player version of VMware and not the Workstation version, we should choose to have only one processor.
Choose the size of the Memory, I know 512 is enough for Clarkconnect.
Floppy configuration, I like to connect it manually.
No need for SCSI controller for me.
I like my Virtual OS to use the defaults of my Windows XP for the monitor confoguration, and 16MB of RAM is plenty.
We need to add our hardware to the configuration, starting with the Hard disk, Choose Add and highlight the Hard Disk and hit OK.
When the Hard Disk is added click on Create New in the field Disk file, you only need to choose a location for the Disk file ( Clarkconnect folder in this tutorial ) by clicking Select Folder and choosing the location...I suggest that you leave everything at it's default unless you need more Disk space, then change the parameters on the field Disk Size.
Disk file is created and saved to the Guest-OS installation directory, hit OK to move on.
We need a CD/DVD-ROM linked to the physical DVD-ROM on our PC, Click Add and highlight the DVD-ROM icon and then hit OK.
I like to use this CD/DVD-ROM when I need it, so I will activate it when needed, so I unchecked the Connected at Boot, and Auto Detect is fine, unless you need to link it to a specific CD/DVD-ROM if you more than one of them.
Click on Add again to create another CD/DVD-ROM, this one is virtual and it will be linked to the Clarkconnect.iso image, click on the small button near the field Use ISO Image to brows to the location of the ISO-image.
*This part is optional, do it only if you need the VM to read from the ISO-image itself.
Still no need to be Connected at Boot for me.
We need a Network adapter, click on Add, highlight the Network adapter and hit OK.
I need it to be Connected at Boot, and I'm choosing the Intel E 1000 Network adapter and I make sure that it's bridged and VMnet0 is the link, if not then you have missed Part 1 on this tutorial. You can choose your own MAC-address or leave the VMware generate it, I suggest that you leave it at Automatically Generated unless you know what you are doing.
Hit Add, choose the Serial Port Icon and hit OK to install a COM-port
*If your PC have more than one COM-port, then you can repeat this step again to install another Serial Port.
I choose to activate it when needed and as I only have one COM-port, then I need it to be locked at COM1 when activated.
Installing a USB Controller can be done the same way, hit Add and choose the USB-Controller icon and OK to confirm,here is the result.
When you have done adding the hardware for your Virtual OS, then you need to save the configuration...hit the button Save above as shown below.
And then hit OK.
3. Installing Clarkconnect:
If you have done all the steps above, then click the Clarkconnect file and VMware Player should start, if your are using the virtual CD-ROM drive VMware will not detect the .iso file just yet, so we need to enable the virtual CD-ROM drive next.
A. If you click on VMware Player window then your mouse and keyboard will be enabled ONLY in the VMware Player window, to release them hold Ctrl and Alt on your keyboard.
B. If you are using MAC-address filtering in your routers, then you need to pick the MAC-address shown at this part and enter it in your router, it's the blured text in the picture below.
*Enabled physical hardware such as CD/DVD-ROM drives, sound card and COM-port, will be unavailable for your Windows XP if they are enabled on the VMware Player window, you need to disable them for VMware Player in order to make them available for your Windows.
The physical CD/DVD drive of your PC is "CD-ROM (IDE 1:0)" and the virtual CD-ROM drive is "CD-ROM (IDE 1:1)".
Enable the virtual CD-ROM drive by clicking on it's button as shown.
Check if your virtual network adapter is connected and bridged
Connect your COM-port ( if needed ).
Restart VMware by clicking on VMware window and holding the buttons Ctrl+Alt+Insert on your keyboard ( Insert not Delete ),Insert button is next to F12, hit Enter to start the installation
1. To Navigate in the installation window, you need to use your keyboards buttons Tab and/or keyboard arrows
2. Space to Mark
3. Enter to Confirm
Choose Installation Language
Choose Keyboard Type
Choose Installation Source
Choose Installation Type
Confirm Installation, you need to write linux here
Choose System, Standalone-Mode here for your server
Choose DHCP for easy installation
Ignore the field for Nameserver and choose OK
Choose the Name of your server
Select your TimeZone
Choose the root password
Choose the Modules you need to install, you need only FTP for now, you can add any desired modules later on
Confirm your server settings to start installation
The server is being installed, that will take about 1 minut, I'm not kidding!
Reboot your server, installation is done!
Your server is starting
Type the root password you have chosen earlier during installation
Choose Launch Text-mode Console hit Enter, we don't know what IP have been assigned for the server in our router yet, we need to know that.
Type the root password and hit Enter twice
There it is, the IP assigned by the router is the one assigned to the external adapter eth0, write it down because we are going to use it a lot later.
As you can see, our server is a StandaloneMode - No Firewall server with no firewall activated, leave it as that, we need to log on the server, so we can leave the firewall off for now and we will enable it later when we choose which ports to be open.
Hit Q and then Y to quit Text-mode Console, choose Logout to leave the server.
4. Configuring the server:
As of now, our server is installed and we are going to log on our server now to configure it
Let us say that the IP that is assigned to your eth0 is ( example ): 192.168.23.108
Then, start your Internet Explorer and type: https://192.168.23.108:81 and hit Enter
*Writting the IP address alone or http://192.168.23.108:81 will result nothing, the "s" in the "https" means that your are requsting a secure connection to port 81 on your server in order to log on .
A Security Alert will appear, you need to accept the secure-connection certificate to logon, hit Yes to accept
Write root as user and type your root password to log on the server
When you have logged on the server, choose Account Manager and click on Users
Click on Continue
Create a user, all fields need to be filled and make sure that FTP is checked, click on Add when done
Choose Software and choose FTP Server
Click on Start to start running your FTP Server and click on Automatic to make it automatically start when/if you restart your server
*I recommend that you change the FTP portnumber here from the default TCP 21
Choose Network and click on IP Settings, here you can turn the firewall on and off by changing between Standalone-Mode and Standalone Mode-No Firewall and if you choose to turn the firewall on, then you need to open the TCP ports for your CCcam server, FTP and Webinfo...etc..click on Continue to confirm the changes.
In case you wonder, the DNS Server-IP here is the IP you type in your browser to log on your router ( your routers IP ).
If we choose to turn the firewall on then we need to open the ports for the services we would like to use, so choose Network and click on Incoming from the sub-menu...here you can open ports to services you would like to use, it's simple:
1. Write the name of the service in the field Nickname/port, like CCcam, FTP, PuTTy..etc..
2. Choose the TCP or UDP port for the service ( CCcam and PuTTy uses TCP-ports )
3. Choose the portnumber
4. Click Add to open the port
*Important: You need to register your copy of Clarkconnect to get updates, the registration takes about 2 minutes and truly painless, they only need a user name and a password and you can register while you are on Dashboard, to register choose "System" and click on Register System.*
5. Uploading CCcam to our FTP server:
I have used FlashFXP in this tutorial but any FTP client program will do...if you are more on the free software side, the I recommend that you use CoreFTP Lite, it's similar to FlashFXP.
1. Extract the archive CCcam-2.0.9.zip or CCcam-2.0.8.zip.
2. Install and start the FTP client program of your choice, the left panel is for your PC and the right panel is for the FTP you want to connect to, use the left panel to brows to the location of the extracted CCcam folder.
3. Cick on Connect and choose Quick Connect.
Fill the Quick Connect panel with the IP of your server, the port you have chosen (port 21 is default if you have not changed it), the username for the user we have created earlier and the password for that username, and hit Connect.
Choose the files CCcam.x86 and CCcam.cfg from the left panel to upload them to your FTP folder on the server on the right panel, when done, right-click on one of the files and choose Transfer.
*To upload more than one file on a single upload, click on one of them and hold the button Ctrl on your keyboard, and left-click on the other files to select them for upload.
The file are uploaded to the FTP folder on the server as shown, you can now close your FTP client program
6. Installing and configuring CCcam:
Extract the putty.zip that you have downloaded from the link provided, and start PUTTY,write the IP number of the port number for your PUTTY and hit Open.
*Default TCP port is 22 if you have not changed it and need to be open in your servers fierwall.
You will be met with a security warning, hit Yes to move on
*You need to logon as root ( not a user ) and use the root password, just as you did log on the server earlier in the part Configuring the server.
From now on, you are on your own....just kidding! Just head over to this wonderfull tutorial How to setup Linux PC CCcam server under 1 hour with ClarkConnect written by kapzas and follow his lead, as I find no point in re-writting what kapzas has in his tutorial, but I can provide some screenshots of the configuring process.
Just remember:
1. Linux is sensative to capital and small letters
2. nano = edit
3. Hitting Ctrl and O = save (That is an O not a zero) you need to hit Enter to confirm the changes
4. Hitting Ctrl and X = exit
Installing and configuring CCcam with kapzas' tutorial in the background
Editting rc.local to add CCcam.x86 to startup
Editting CCcam.cfg
Saving changes to CCcam.cfg
7. Installing the USB drivers and Nftytool( Optional ):
The USB drivers are not installed in Clarkconnect by default, and that's why you need to install them first...to install them you need to register your copy by choosing Services and then Register System on Clarkconnect's Dashboard.
Log on using Putty and when logged in copy these commands from here and right-click in Putty to execute the following commands ( if you don't like to write much ) :
1. apt-get install libusb-devel
*write y and hit Enter when prompted to download and install.
2. apt-get install gcc
*write y and hit Enter when prompted to download and install.
*If Clarkconnects update-server is down, then the USB drivers are provided for download above, but you need gcc anyway.
Download ntfytool (v1.1) and extract it at your desktop, rename the folder nftytool-1.1 inside the extracted archive to nftytool and upload it to your server's FTP folder using your FTP client program as you did with CCcam.x86 and CCcam.cfg when you have installed them.
Write in Putty:
cd /home/the_name_of_your FTP folder
cp -r nftytool /var
*You can copy it to the folder of your choice, I just like to have it with the other directories.
cd /var/nftytool
chmod 755 configure
./configure
make
Now the installation is done, you need to execute a command to start the program:
./nftytool -p phoenix -- -p phoenix -f 3.58 -e
*For 3.58MHz
./nftytool -p phoenix -- -p phoenix -f 3.68 -e
*For 3.68MHz
./nftytool -p phoenix -- -p phoenix -f 6.00 -e
*For 6.00MHz
You need to execute the command of the desired speed for your card in the nftytool folder once when you start it and again if you shutdown your your system ( not the Virtual Machine ) and start it later, not when rebooting.
*As long as the Infinity USB Phoenix gets power through the USB cable, then it will still function as it configured, only when it loose the power, then the command need to be executed to configure it again.
So if you shutdown your system and start it again later you need to execute these lines again in Putty:
cd /var/nftytool
./nftytool -p phoenix -- -p phoenix -f x.xx -e
*x.xx are the desired speed of your card
By the way, the path for the COM-port in the CCcam.cfg is:
PHOENIX READER PATH : /dev/ttyS0
8. Running the server in the background ( optional ):
VMware Player will run on taskbar, I don't know about you, but I like to run the programs that don't use all the time in the background, but like to see them in the System Tray ( Notification Area ), so I know what's running and if the program is still running in the background.
To that purpose I used a free software called TrayIt!, it's very simple to use and I must say that it did the job very well, and the server kept running in the System Tray without a crash when I have minimized the VMware Player window...the program is a standalone and don't need to be installed on Windows, all you have to do is run the program from it's folder.
I extracted it from archive and copied the folder to my Clarkconnect folder so I remember to start it when I start the server.
Configuring it is simple as you can see below
The summary:
At the end of this tutorial, we have made and successfully configured our server,and you might think that it took a long time to install, in fact I have installed it several times to check how long it will take to install, it actually took around 40 minutes to be fully functional and online!.
Some might say that I keep repeating the word Server not CCcam-Server, well, that is what it is actually...Running CCcam on it is only the tip of the iceberg, what we have now is a fully functional server, it could be an FTP server or a Mail server or any server that need to do a certain job, and what is most amazing about this server is :
1. Does not require a separate PC to run on.
2. Does not require much resources such as RAM and Disk space.
3. Can run in the background of your Windows that you have on your PC just like any other program.
4. Very secure.
5. Very fast.
6. Very reliable.
7. Does not need to be re-installed and re-configured every time you need to re-install your Windows or to format the drive you have your Virtual Server folder on, simply copy the Virtual-OS-folder ( in this tutorial it's the whole Clarkconnect folder that we have created on drive C:, around 1.6GB !!) to another drive, reinstall your windows or format the drive you want to format, install VMware Player and configure the network adapter if you have re-installed Windows as in part 1 in this tutorial, copy your Clarkconnect folder back to it's location and hit the file Clarkconnect to start the server and see the magic.
On the other side, the only downside I can see is that you need to keep the PC you have installed your Clarkconnect server on turned on all the time.
I hope that you have enjoyed this tutorial, and that you can make use of it...and if you think that this tutorial has been useful, please use the thanks button, thank you.
Special thanks to forum members davklaud, skippie and storm for there big help testing the server in the last 4 days
Updated 7/8/2008:
1. Added link to VMXBuilder
2. Added link to CCcam 2.0.8
3. Added link to Pre-configured Clarkconnect VMware Virtual disk and configuration files (32-bit)
4. Added link to USB development package V.0.1.12
5. Added link to Nftytool for Infinity USB Phoenix Card-reader V.1.1
6. Added a procedure for using VMXBuilder
7. Added a procedure for installing USB drivers and Nftytool.
All the best
http://www.eucardsharing.com
The trick is not installing Linux on Windows XP and running it as a VM, many do that already using VMware Player or Microsoft Virtual PC,the trick is to make this VM be fully recognized by Windows XP and it self as a server that has it's own physical MAC-address and thereby it's own IP in the router.
To sum it all, we are going to trick the router that we are running a physical PC somewhere and that PC is physically connected to that router, in order to obtain an IP in the router so the Virtual Linux OS (OS means Operating System such as Windows XP, Vista, Ubunto, Opensuse..etc), can send and receive data over that router, and in this tutorial we are going to use Clarkconnect as a Virtual Linux OS.
I choose Clarkconnect as a Virtual server because it's secure, small, fast, stable and does not require much of disk space or RAM, don't be surprised if we used 2GB of hard disk space along with only 512MB RAM and our Clarkconnect Virtual server will actually only uses less than half of the disk space and about 250 MB of the RAM we are going to allocate for this Virtual Server.
If that have given an idea of what we are going to do then lets get started...we need tools do so...
The tools:
1: Clarkconnect Community Edition 4.2 SP1 as Virtual OS
http://www.clarkconnect.com/downloads/isos.php
2: VMware Player as our VM ( Requires a small registration )
http://www.vmware.com/download/player/
3: Pre-configured Clarkconnect VMware Virtual disk and configuration files (32-bit)
http://rapidshare.com/files/135584513/Clarkconnect_VMX_pre_configured.zip.html
Specifications:
32Bit Guest VM
One CPU and 512MB of RAM
One Hard disk of 2GB space
One physical CD/DVD-ROM
One virtual CD/DVD-ROM
One Bridged network adapter ( bridged to VMnet0 )
One Serial Port ( COM1 )
One USB controller
( MD5 checksum = 7c54a3017fcd173f4495e0116db61f2f *Clarkconnect_VMX_pre_configured.zip )
4: VMXBuilder as a VMware Virtual disk and configuration file builder
http://rapidshare.com/files/135584738/VMXBuilderSetup.zip.html
( MD5 checksum = ffb73f78b9fd1cf444c8232719d872de *VMXBuilderSetup.zip )
5: CCcam CS program
http://www.eucardsharing.com/index.php?action=tpmod;dl=item5
6: An FTP client program
http://www.filezilla.com
7: Putty to configure and start our CCcam server
http://rapidshare.com/files/130837134/putty.zip.html
Optional
1: TrayIt!, the program sends any running program on taskbar to the system tray
Download
2: USB development package V.0.1.12
Download
( MD5 checksum = caf182cbc7565dac0fd72155919672e6 *libusb-0.1.12.tar.gz )
3: Nftytool for Infinity USB Phoenix Card-reader V.1.1
Download
P.S. The MD5 checksums for the archives above are not passwords, they are to are there to confirm that the archives are uploaded by me and if an archive doesn't carry that hash-number I have provided here for it then the archive is not mine and have been modified by someone else, you can use MD5summer (Home of the MD5summer) to make sure of that.
Before we start:
I would like to inform a little about Clarkconnect VMware Virtual disk and configuration files provided for download above:
These are made using VMXBuilder, the easyvmx site that I have linked to in the earlier version in this tutorial is actually using VMXBuilder to generate the VMware configuration files without mentioning this program at all and I thought, as all of you, that they stood behind the development of the VMware configuration files but they are not.
I found about that when I started searching the internet to see if any others are facing the same problem as we have due to the COM-port in the Virtual Server created does not work at all, and that means that the there is something wrong with the VMware configuration for the COM-port, however, I found the authors homepage after much searching and along with that, I found out that they have been working on VMXBuilder since 11/05/2005.
LINK
After using this program to generate the configuration files I have no problem using the COM-port which now works flawlessly, and as you can see, the credit should go for the guys that stand behind this project and not for easyvmx.
Later on, I'm going to guide you through VMXBuilder and you can then make your own configurations using VMBuilder if you decide to use another OS than Clarkconnect or you have another Host OS than Windows XP.
Let's get started....
1. Configuring Network adapters:
*These steps are very important*
1. Install VMware Player on your system, when done, head over to Network Connections in Control Panel,right-click your physical network adapter and choose Properties...make sure that VMware Bridge Protocol is checked, if not, check it and hit OK as shown below..
2. Brows to : Program Files\VMware\VMware Player folder and click on vmnetcfg, when it starts choose the tab Host Virtual Network Mapping and change VMnet0 from Briged to an automaticlly chosen adapter to your own physical network adapter, hit Apply and OK..
3.Create a folder on drive C:\ and name it Clarkconnect, then extract the archive Clarkconnect_VMX_pre_configured.zip and copy the content of the folder to the Clarkconnect folder we created earlier on drive C:\, when done copy "community-4.2.SP1.iso" to the the same folder and rename the iso-image to Clarkconnect.
* You can burn the community-4.2.SP1.iso to a CD and install from your CD/DVD Drive if you want, but I have chosen to use the VMwares own virtual CD-ROM drive because it's faster, and that's why I choose to copy community-4.2.SP1.iso to the Clarkconnect folder on drive C:\.
2. Configuring and making the VMware configuration file:
Install VMXBuilder and run the program
The porgram should place a shortcut on your Desktop, otherwise, the program is located on Start ->All Programs ->RDPSoftware ->VMware ->VMXBuilder
Choose Create New Virtual Machine
Choose the location you want to save the configurations files to
*It will be easier to save them to your Desktop now and move them later, otherwise, you should save them to the location of your Guest-OS installation directory, it's C:\Clarkconnect in this tutorial.
Choose a name for you Virtual Machine
As showen below on the Options-Tab on General options, I changed the VM and VMX-file names to the name of the ISO-image that I'm using.
It's important that the Target Platform is : Workstation and the Version is : 5.5 , that will make the configuration flexible, it's still targeted at VMware Workstation version but we will still be able to use it with the VMware Player. The Guest-OS should be Linux.
The Kernel version of the Clarkconnect I'm installing is 2.6 , if you are installing an other Linux Guest-OS then you should follow your Guest-OS Kernel.
The Working Directory should be the location of your Guest-OS installation directory.
Change to the Hardware-Tab, I'm naming the Virtual Motherboard here.
As we are using the Player version of VMware and not the Workstation version, we should choose to have only one processor.
Choose the size of the Memory, I know 512 is enough for Clarkconnect.
Floppy configuration, I like to connect it manually.
No need for SCSI controller for me.
I like my Virtual OS to use the defaults of my Windows XP for the monitor confoguration, and 16MB of RAM is plenty.
We need to add our hardware to the configuration, starting with the Hard disk, Choose Add and highlight the Hard Disk and hit OK.
When the Hard Disk is added click on Create New in the field Disk file, you only need to choose a location for the Disk file ( Clarkconnect folder in this tutorial ) by clicking Select Folder and choosing the location...I suggest that you leave everything at it's default unless you need more Disk space, then change the parameters on the field Disk Size.
Disk file is created and saved to the Guest-OS installation directory, hit OK to move on.
We need a CD/DVD-ROM linked to the physical DVD-ROM on our PC, Click Add and highlight the DVD-ROM icon and then hit OK.
I like to use this CD/DVD-ROM when I need it, so I will activate it when needed, so I unchecked the Connected at Boot, and Auto Detect is fine, unless you need to link it to a specific CD/DVD-ROM if you more than one of them.
Click on Add again to create another CD/DVD-ROM, this one is virtual and it will be linked to the Clarkconnect.iso image, click on the small button near the field Use ISO Image to brows to the location of the ISO-image.
*This part is optional, do it only if you need the VM to read from the ISO-image itself.
Still no need to be Connected at Boot for me.
We need a Network adapter, click on Add, highlight the Network adapter and hit OK.
I need it to be Connected at Boot, and I'm choosing the Intel E 1000 Network adapter and I make sure that it's bridged and VMnet0 is the link, if not then you have missed Part 1 on this tutorial. You can choose your own MAC-address or leave the VMware generate it, I suggest that you leave it at Automatically Generated unless you know what you are doing.
Hit Add, choose the Serial Port Icon and hit OK to install a COM-port
*If your PC have more than one COM-port, then you can repeat this step again to install another Serial Port.
I choose to activate it when needed and as I only have one COM-port, then I need it to be locked at COM1 when activated.
Installing a USB Controller can be done the same way, hit Add and choose the USB-Controller icon and OK to confirm,here is the result.
When you have done adding the hardware for your Virtual OS, then you need to save the configuration...hit the button Save above as shown below.
And then hit OK.
3. Installing Clarkconnect:
If you have done all the steps above, then click the Clarkconnect file and VMware Player should start, if your are using the virtual CD-ROM drive VMware will not detect the .iso file just yet, so we need to enable the virtual CD-ROM drive next.
A. If you click on VMware Player window then your mouse and keyboard will be enabled ONLY in the VMware Player window, to release them hold Ctrl and Alt on your keyboard.
B. If you are using MAC-address filtering in your routers, then you need to pick the MAC-address shown at this part and enter it in your router, it's the blured text in the picture below.
*Enabled physical hardware such as CD/DVD-ROM drives, sound card and COM-port, will be unavailable for your Windows XP if they are enabled on the VMware Player window, you need to disable them for VMware Player in order to make them available for your Windows.
The physical CD/DVD drive of your PC is "CD-ROM (IDE 1:0)" and the virtual CD-ROM drive is "CD-ROM (IDE 1:1)".
Enable the virtual CD-ROM drive by clicking on it's button as shown.
Check if your virtual network adapter is connected and bridged
Connect your COM-port ( if needed ).
Restart VMware by clicking on VMware window and holding the buttons Ctrl+Alt+Insert on your keyboard ( Insert not Delete ),Insert button is next to F12, hit Enter to start the installation
1. To Navigate in the installation window, you need to use your keyboards buttons Tab and/or keyboard arrows
2. Space to Mark
3. Enter to Confirm
Choose Installation Language
Choose Keyboard Type
Choose Installation Source
Choose Installation Type
Confirm Installation, you need to write linux here
Choose System, Standalone-Mode here for your server
Choose DHCP for easy installation
Ignore the field for Nameserver and choose OK
Choose the Name of your server
Select your TimeZone
Choose the root password
Choose the Modules you need to install, you need only FTP for now, you can add any desired modules later on
Confirm your server settings to start installation
The server is being installed, that will take about 1 minut, I'm not kidding!
Reboot your server, installation is done!
Your server is starting
Type the root password you have chosen earlier during installation
Choose Launch Text-mode Console hit Enter, we don't know what IP have been assigned for the server in our router yet, we need to know that.
Type the root password and hit Enter twice
There it is, the IP assigned by the router is the one assigned to the external adapter eth0, write it down because we are going to use it a lot later.
As you can see, our server is a StandaloneMode - No Firewall server with no firewall activated, leave it as that, we need to log on the server, so we can leave the firewall off for now and we will enable it later when we choose which ports to be open.
Hit Q and then Y to quit Text-mode Console, choose Logout to leave the server.
4. Configuring the server:
As of now, our server is installed and we are going to log on our server now to configure it
Let us say that the IP that is assigned to your eth0 is ( example ): 192.168.23.108
Then, start your Internet Explorer and type: https://192.168.23.108:81 and hit Enter
*Writting the IP address alone or http://192.168.23.108:81 will result nothing, the "s" in the "https" means that your are requsting a secure connection to port 81 on your server in order to log on .
A Security Alert will appear, you need to accept the secure-connection certificate to logon, hit Yes to accept
Write root as user and type your root password to log on the server
When you have logged on the server, choose Account Manager and click on Users
Click on Continue
Create a user, all fields need to be filled and make sure that FTP is checked, click on Add when done
Choose Software and choose FTP Server
Click on Start to start running your FTP Server and click on Automatic to make it automatically start when/if you restart your server
*I recommend that you change the FTP portnumber here from the default TCP 21
Choose Network and click on IP Settings, here you can turn the firewall on and off by changing between Standalone-Mode and Standalone Mode-No Firewall and if you choose to turn the firewall on, then you need to open the TCP ports for your CCcam server, FTP and Webinfo...etc..click on Continue to confirm the changes.
In case you wonder, the DNS Server-IP here is the IP you type in your browser to log on your router ( your routers IP ).
If we choose to turn the firewall on then we need to open the ports for the services we would like to use, so choose Network and click on Incoming from the sub-menu...here you can open ports to services you would like to use, it's simple:
1. Write the name of the service in the field Nickname/port, like CCcam, FTP, PuTTy..etc..
2. Choose the TCP or UDP port for the service ( CCcam and PuTTy uses TCP-ports )
3. Choose the portnumber
4. Click Add to open the port
*Important: You need to register your copy of Clarkconnect to get updates, the registration takes about 2 minutes and truly painless, they only need a user name and a password and you can register while you are on Dashboard, to register choose "System" and click on Register System.*
5. Uploading CCcam to our FTP server:
I have used FlashFXP in this tutorial but any FTP client program will do...if you are more on the free software side, the I recommend that you use CoreFTP Lite, it's similar to FlashFXP.
1. Extract the archive CCcam-2.0.9.zip or CCcam-2.0.8.zip.
2. Install and start the FTP client program of your choice, the left panel is for your PC and the right panel is for the FTP you want to connect to, use the left panel to brows to the location of the extracted CCcam folder.
3. Cick on Connect and choose Quick Connect.
Fill the Quick Connect panel with the IP of your server, the port you have chosen (port 21 is default if you have not changed it), the username for the user we have created earlier and the password for that username, and hit Connect.
Choose the files CCcam.x86 and CCcam.cfg from the left panel to upload them to your FTP folder on the server on the right panel, when done, right-click on one of the files and choose Transfer.
*To upload more than one file on a single upload, click on one of them and hold the button Ctrl on your keyboard, and left-click on the other files to select them for upload.
The file are uploaded to the FTP folder on the server as shown, you can now close your FTP client program
6. Installing and configuring CCcam:
Extract the putty.zip that you have downloaded from the link provided, and start PUTTY,write the IP number of the port number for your PUTTY and hit Open.
*Default TCP port is 22 if you have not changed it and need to be open in your servers fierwall.
You will be met with a security warning, hit Yes to move on
*You need to logon as root ( not a user ) and use the root password, just as you did log on the server earlier in the part Configuring the server.
From now on, you are on your own....just kidding! Just head over to this wonderfull tutorial How to setup Linux PC CCcam server under 1 hour with ClarkConnect written by kapzas and follow his lead, as I find no point in re-writting what kapzas has in his tutorial, but I can provide some screenshots of the configuring process.
Just remember:
1. Linux is sensative to capital and small letters
2. nano = edit
3. Hitting Ctrl and O = save (That is an O not a zero) you need to hit Enter to confirm the changes
4. Hitting Ctrl and X = exit
Installing and configuring CCcam with kapzas' tutorial in the background
Editting rc.local to add CCcam.x86 to startup
Editting CCcam.cfg
Saving changes to CCcam.cfg
7. Installing the USB drivers and Nftytool( Optional ):
The USB drivers are not installed in Clarkconnect by default, and that's why you need to install them first...to install them you need to register your copy by choosing Services and then Register System on Clarkconnect's Dashboard.
Log on using Putty and when logged in copy these commands from here and right-click in Putty to execute the following commands ( if you don't like to write much ) :
1. apt-get install libusb-devel
*write y and hit Enter when prompted to download and install.
2. apt-get install gcc
*write y and hit Enter when prompted to download and install.
*If Clarkconnects update-server is down, then the USB drivers are provided for download above, but you need gcc anyway.
Download ntfytool (v1.1) and extract it at your desktop, rename the folder nftytool-1.1 inside the extracted archive to nftytool and upload it to your server's FTP folder using your FTP client program as you did with CCcam.x86 and CCcam.cfg when you have installed them.
Write in Putty:
cd /home/the_name_of_your FTP folder
cp -r nftytool /var
*You can copy it to the folder of your choice, I just like to have it with the other directories.
cd /var/nftytool
chmod 755 configure
./configure
make
Now the installation is done, you need to execute a command to start the program:
./nftytool -p phoenix -- -p phoenix -f 3.58 -e
*For 3.58MHz
./nftytool -p phoenix -- -p phoenix -f 3.68 -e
*For 3.68MHz
./nftytool -p phoenix -- -p phoenix -f 6.00 -e
*For 6.00MHz
You need to execute the command of the desired speed for your card in the nftytool folder once when you start it and again if you shutdown your your system ( not the Virtual Machine ) and start it later, not when rebooting.
*As long as the Infinity USB Phoenix gets power through the USB cable, then it will still function as it configured, only when it loose the power, then the command need to be executed to configure it again.
So if you shutdown your system and start it again later you need to execute these lines again in Putty:
cd /var/nftytool
./nftytool -p phoenix -- -p phoenix -f x.xx -e
*x.xx are the desired speed of your card
By the way, the path for the COM-port in the CCcam.cfg is:
PHOENIX READER PATH : /dev/ttyS0
8. Running the server in the background ( optional ):
VMware Player will run on taskbar, I don't know about you, but I like to run the programs that don't use all the time in the background, but like to see them in the System Tray ( Notification Area ), so I know what's running and if the program is still running in the background.
To that purpose I used a free software called TrayIt!, it's very simple to use and I must say that it did the job very well, and the server kept running in the System Tray without a crash when I have minimized the VMware Player window...the program is a standalone and don't need to be installed on Windows, all you have to do is run the program from it's folder.
I extracted it from archive and copied the folder to my Clarkconnect folder so I remember to start it when I start the server.
Configuring it is simple as you can see below
The summary:
At the end of this tutorial, we have made and successfully configured our server,and you might think that it took a long time to install, in fact I have installed it several times to check how long it will take to install, it actually took around 40 minutes to be fully functional and online!.
Some might say that I keep repeating the word Server not CCcam-Server, well, that is what it is actually...Running CCcam on it is only the tip of the iceberg, what we have now is a fully functional server, it could be an FTP server or a Mail server or any server that need to do a certain job, and what is most amazing about this server is :
1. Does not require a separate PC to run on.
2. Does not require much resources such as RAM and Disk space.
3. Can run in the background of your Windows that you have on your PC just like any other program.
4. Very secure.
5. Very fast.
6. Very reliable.
7. Does not need to be re-installed and re-configured every time you need to re-install your Windows or to format the drive you have your Virtual Server folder on, simply copy the Virtual-OS-folder ( in this tutorial it's the whole Clarkconnect folder that we have created on drive C:, around 1.6GB !!) to another drive, reinstall your windows or format the drive you want to format, install VMware Player and configure the network adapter if you have re-installed Windows as in part 1 in this tutorial, copy your Clarkconnect folder back to it's location and hit the file Clarkconnect to start the server and see the magic.
On the other side, the only downside I can see is that you need to keep the PC you have installed your Clarkconnect server on turned on all the time.
I hope that you have enjoyed this tutorial, and that you can make use of it...and if you think that this tutorial has been useful, please use the thanks button, thank you.
Special thanks to forum members davklaud, skippie and storm for there big help testing the server in the last 4 days
Updated 7/8/2008:
1. Added link to VMXBuilder
2. Added link to CCcam 2.0.8
3. Added link to Pre-configured Clarkconnect VMware Virtual disk and configuration files (32-bit)
4. Added link to USB development package V.0.1.12
5. Added link to Nftytool for Infinity USB Phoenix Card-reader V.1.1
6. Added a procedure for using VMXBuilder
7. Added a procedure for installing USB drivers and Nftytool.
All the best
http://www.eucardsharing.com
Subscribe to:
Posts (Atom)