Billing "Jendela" jalan di Linux (Client)

Alhamdulillah...
Subuh 1 Juli kemaren... iseng iseng download wine untuk Ubuntu lewat cermin http://komo.vlsm.org salah satu cermin yg dipunyai putra Indonesia
yaitu :

libwine_0.0.20050310-1.1_i386.deb
wine_0.0.20050310-1.1_i386.deb
wine-utils_0.0.20050310-1.1_i386.deb
winesetuptk_0.7-1_i386.deb

yah mumpung 'libur' :) iseng iseng ajah...setelah experiment dengan CCL, Zeiberbude dan Cyborg.
Yah itung itung penasaran dan ingin memanfaatkan yg sebagain dari kita sudah mempunyainya.

==============================
Spesifikasi
==============================
Server : Jendela original (sementara experiment baru sebatas client, karena memang server billing kita pakai original)
Client : Ubuntu dan Kubuntu
Billing Name : Billing Explorer (Original)
-------------------------------

Langkah I
login mode admin/root access
#dpkg -i libwine_xxx.deb
#dpkg -i wine_xxx.deb
#dpkg -i wine-util_xxx.deb
#dpkg -i winesetuptk_xxx.deb

Langkah II
Konfigurasi wine
#winesetup

Silahkan konfigurasi wine
Langkah awal sebaiknya menggunakan mode "Desktop"
jalankan program setup billing anda, misal
#wine /home/admin/clienbilling/SETUP.EXE

maka proses instalasi akan berjalan
selesai

jalankan program billing anda, untuk testing bisa lewat konsole :
#wine /home/admin/.wine/fake_windows/Program\ Files/Clien008/client008.exe

konfigurasi akhir sepertihalnya ketika anda menginstall pada jendela

done

jika sudah yakin jalan, anda bisa experiment dengan mengubah mode tampilan jendela, dengan option Managed atau UnManaged

Selamat mencoba

-----------------
Ainul Hakim
SmartIKON.or.id
-----------------

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

re :billing linux

Jika Ada yang belum jelas mengenai cara setting diatas, ataupun cara setting billing original "Billing Explorer" pada family slackware misal vector soho dll bisa dialamatkan ke tonieee@gmail.com ataupun ke alamat
GrandNet
Jl Sirajudin 5 sebelah Kantor Pos Tembalang Semarang

www.grandnetstudio.com

Client Billing Explorer..Re: AinulHakim

He..he...Kalo client billing explorer emang ada versi linuxnya mas.
Jadi ga usah pake wine segala. Trus kalo server billing juga make jendela (biar original juga..lagian sombong banget bisa beli original) mah tidak aneh.
Saya juga sudah tanya via email yang ada di billing.expoler.com tidak ada jawaban tuh. Emang kayanya server billing tidak jalan di linux.Weee

Hidup linux...anti jendala biar original biar bajakan juga

Sekali linux tetap linux

re: Client

memang client BE ada yg versi linux, tapi bayar.. dan harganya minta ampun, dan lagian yg versi itu servernya juga masih under jendela.
So bagi yg tadinya udah punya BE versi Jendela bisa manfaatin yg udah mereka beli dengan menggunakan wine.

seep

ok

Install Billing Explore di Linux Pake "Wine / Crossover"

Mas, saya udah coba Nginstall Billing Explore (versi asli) di Linux Mandrake 10 dan Fedora core 3 pake Wine & crossover trial tapi nggak mau jalan, malah keluarnya " System Error H800040005 (-2147467259) " , mas yang ganteng-ganteng mohon bantuannya ya... Soalnya saya ama temen-temen di lab Kampus pengen migrasi ke Linux,.. Semua komp di lab kampus udah dual boot_tinggal soal billingnya. Minta tolong ya.... 8-) by...thanks

re BE under Crossover

wah lab kampus yaa.... terusin ajah mas experimennya.. siapa tahu nanti berhasil... never giveup, nanti klo dah bisa di share yaa.
untuk RH base .. bisa pakai OpenKIosK (detail instalasi bisa search di linux.or.id ini)

???>>>> Billing "Jendela" jalan di Linux

:(( sudah coba juga di Ubuntu, tapi masih saja error. kalo ada temen yang sudah terlanjur beli BE Versi Linux (emang Servernya pake Win) kirimkan ke e-mial yieyie22@yahoo.com, ntar biar temen ku crack kan, abis beli BE Versi Linux juga muahalllllllll

:D

itu juga Ubuntu

Tutorial ini juga ubuntu kok mas... errornya bisa di jelaskan ??
jangan lupa wine-nya di konfig dulu dengan
#winesetup
trus di set dulu ke mode desktop

Client sih udah tahu. servernya ini lho

kalo yang client udah coba sih, tapi kalau yang server emang nggak bisa kayaknya. sama tuh errornya kayak yang dibilang rian_188

server BE... ? mudah mudahan...

mas... kita di sini mo share... yg udah tahu ada baiknya kan di share... biar yg belum tahu bisa ikutan tahu... itu ajah kok prinsip saya.
Masalah server... hmmm kayanya masih butuh riset yg panjang... coz dari developer aslinya ajah nda ngeluarin versi yg jendela utk server BE-nya... walopun dia ngeluarin NextBitz (linux-clien jendela-server) why..? developnya (kang wahyu) yg mungkin tahu jawabannya.
jika ada rekan yg malah udah berhasil utk server BE run under linux tolong di share juga.

saran : untuk yg pakai Vector SoHo ada bainya gunakan ajah CCL, running stable under SOHO kok

Billing "Jendela" jalan di Linux (Client)

Mas Ainul Hakim

Minta petunjuk install BE client nya, soalnya aku coba di ubuntu masih saja error

root@DenBaguse:~ # wine /home/clientwnet/Windows/BEClient/SETUP.EXE
fixme:ole:MSFT_ReadValue BSTR length = -1?
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:MSFT_ReadValue BSTR length = -1?
fixme:ole:MSFT_ReadValue BSTR length = -1?
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:OLEPRO32_DllRegisterServer not implemented (olepro32.dll)
fixme:ver:VERSION_GetLinkedDllVersion Unknown EXE OS version 4.0, please report !!
fixme:ole:CoRegisterMessageFilter stub
fixme:ole:OLEPictureImpl_SaveAsFile (0x77c50dd0)->(0x77c55f80, 0, (nil)), hacked stub.
fixme:ole:OLEPictureImpl_get_hPal (0x77c5b488)->(0x7797f5a8): stub
fixme:ole:OLEPictureImpl_SaveAsFile (0x77c55928)->(0x77c5d598, 0, (nil)), hacked stub.
fixme:ole:OLEPictureImpl_Render Not quite correct implementation of rendering icons...
fixme:ole:MSFT_ReadValue BSTR length = -1?
fixme:ole:OLEPictureImpl_get_hPal (0x77c7b600)->(0x7797f528): stub
fixme:ole:OLEPictureImpl_SaveAsFile (0x77c5b118)->(0x77c7d6d0, 0, (nil)), hacked stub.
fixme:ole:OLEPictureImpl_get_hPal (0x77c7b600)->(0x7797e0c0): stub
fixme:ntdll:TIME_GetTZAsStr Can't match system time zone name "WIT", bias=-420 and dst=0 to an entry in TZ_INFO. Please add appropriate entry to TZ_INFO and submit as patch to wine-patches
fixme:ole:OLEPictureImpl_get_hPal (0x77c7aec0)->(0x7797f478): stub
fixme:ole:OLEPictureImpl_SaveAsFile (0x77c7bfe8)->(0x77c7e518, 0, (nil)), hacked stub.
fixme:ole:OLEPictureImpl_Render Not quite correct implementation of rendering icons...
fixme:ole:OLEPictureImpl_SaveAsFile (0x77c7b008)->(0x77c813e8, 0, (nil)), hacked stub.
fixme:ole:OLEPictureImpl_get_hPal (0x77c82dd0)->(0x7797f478): stub
fixme:ole:OLEPictureImpl_SaveAsFile (0x77c7af90)->(0x77c81398, 0, (nil)), hacked stub.
fixme:ole:OLEPictureImpl_Render Not quite correct implementation of rendering icons...
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:RegisterTypeLib Registering non-oleautomation interface!
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:OLEPictureImpl_Render Not quite correct implementation of rendering icons...
fixme:ole:OLEPictureImpl_Render Not quite correct implementation of rendering icons...
fixme:shell:SHELL32_DllCanUnloadNow stub
fixme:ole:CoRegisterMessageFilter stub
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
fixme:shell:SHELL32_DllCanUnloadNow stub
err:heap:HEAP_GetPtr Invalid heap (nil)!
Wine exited with a successful status

re: error BE Client di UBUNTU

ini sudah diinstall semua ?

libwine_0.0.20050310-1.1_i386.deb
wine_0.0.20050310-1.1_i386.deb
wine-utils_0.0.20050310-1.1_i386.deb
winesetuptk_0.7-1_i386.deb

trus jalankan winesetup
#winesetup
maka akan tampil gui winesetup>look and feel, pilih win98
trus klik windows mode (panel kiri)
Integration of Wine with X >> pilih Desktop (nanti klo udah berhasil semua silahkan diganti ganti....menurut selera :) )
periksa pula drives dan paths
klik >> Finish

coba jalankan setup lagi.. mudah mudahan jalan

Ainul Hakim
SmartIKON.or.id

Review BE Client u/ Linux

1. Mode Desktop :
a. Setelah login akan muncul permasalahan seperti mas rian
"login ke server dari client kok malah keluar tulisan "run_time 5 error", pas keluar trus BE (Client mati). Setelah mati aq idupin lagi baru bisa connest ke server. Kok bisa gitu ya ?"
yaa memang saya-pun masih mengalami hal yg serupa.. dan masih dicari penyebabnya.

b. Mode desktop mempunyai kelemahan yaitu poin a ditambah klo user iseng menyelundup billing akan mudah di minimize :)

c. keuntungannya : user bisa login sendiri dan diskonek sendiri dan bisa kirim message ke op/server

2. Mode Managed :
a. tampilan gui kurang sempurna sehinga banyak tulisan yg ngga bisa terbaca
b. bisa di minimize
c. klo bisa login akan minimize dan langsung ke system tray tapi sayang freze... :( sehingga user tidak bisa memantau billingnya

3. Mode UnManaged
a. User tidak bisa login sendiri karena client tidak bisa mengetik sendiri (keybpard mode off) , kita juga belum tahu apa penyebabnya ??
b. Billing tidak bisa di close (ALt+F4) dan tidak bisa di minimize sehingga user penyelundup bisa diatasi.
c. Login user dari Billing server dengan model move.

Nah... dari keuntungan dan kerugiannya silahkan pilih yg sesuai dengan kebutuhan saudara :)
yg namanya emulasi sesuatu yg bukan di desain yaa pasti ada kelemahannya... :)

semoga tetap bisa berguna dari apa yg sudah pernah kita beli :((

disamping ada alternatif distro IGOS keluaran gunadarma yg ada billingnya sekaligus

salam

Ainul Hakim
smartIKON.or.id

Thanks to "Mas Ainul"

Terima kasih buat Mas Ainul, atas bantuannya. Mungkin untuk billing aq akan coba yang lain. Dari hasil yang tadi aq dapat menurutku lebih banyak kelemahannya daripada kelebihannya. Mungkin aq akan coba cari billing yang lain "for linux".
Thanks.

UPKFE UNDIP

biling linux ubuntu

masss saya minta bantuan nya bagai mana cara menjalan kan biling di linux ubuntu, dan bagai mana cara menjalankan web kamera di yahoo cat nya, saya mohon bantuan nya mas.mas saya bagidong sofwer biling nya ya mas

Billing

kebetulan yg di bahas di blog ini billing BE-Client-Win yg diemulasikan ke linux.
Untuk billing lainnya bisa pakai OpenKIosK atau Zeiberbude yg ada di packages.debian
Untuk YM-Webcam silahkan gunakan Gyach dan turorialnya sudah ada tinggal search di linux.or.id ini.