Tuesday, December 09, 2008

Extremly Lame

After aching my head with winedump/winebuild to figure out a way to add dynamic-libraries to Wine I found that I can add whatever dll directly to wine simulated windows directory.
/home/[user]/.wine/drive_c/windows/system32
Where [users] substitued by by user name of the system.
Just copying the dll to that path and you got it working or putting the required dll in the same directory of that program which needs it.

Labels: ,

Smilar pages

Tuesday, April 08, 2008

Repairing Grub

Ever installed linux, then had to install windows or fix windows by reinstalling it, only to see that the Grub menu u used to log into linux from has disappeared?
This has happened to me all too many times, therefore i put the instructions here for future reference, as a friend has advised me to do...
The removal of the grub boot menu happens because it resides on Master boot Record(MBR) part of the harddrive, a portion that windows deletes and installs it boot loader instead, which is called NTLDR or NT bootloader...
wat u have to do to install grub back is to boot from a live linux cd and run the command grub in a root konsole, then type the following assuming that (hd0) where u installed ur grub or u could issue the command "find /boot/grub/stage1" in the grub prompt to find where is the linux boot loader is residing and use the result in lieu of (hd0).
or as a last resort u can try changing the no. after hd followed by a comma and another no. till the grub reports the linux filesystem...
root (hd0,0)
setyp (hd0)
exit [or quit since some report exit not working]


should u not find ur windows entry in grub menu then type in a root konsole

nano /boot/grub/menu.lst

scroll down till u see the line starting with a pound sign (#) saying #title Windows 95/98/NT/2000 and uncomment the lines including #chainloader +1 by removing the leading pound symbol.
also besure where ur windows parition resides and adjust the windows root entry accordingly since the default in the menu.lst file is (hd0,0)

Goodluck!

Labels:

Smilar pages

Thursday, May 03, 2007

Creating a Wireless Accesspoint in Five Simple Steps

If u wanted to create a simple accesspoint to make ur own accesspoint-based wireless network for watever purpose then this is for u...however by no means accesspoints are the only way to make wireless networks, an ad-hoc network is a wireless network that doesnt have a central accesspoint but is based on a peer-to-peer communication...

Creating the AP can be done on different OSs, on the linux side where this task is more reliable and widespread...i will discuss the madwifi (madwifi.org) way which should work for almost at atheros-chipset based wireless NIC...u can check ur card at madwifi's website (http://madwifi.org/wiki/Compatibility) and see whether it works well (or at all) with this driver.

1. U first have to install madwifi NG on ur favourite linux distro, which might require installing the build headers and kernel/modules headers, ie. read ur distros docs...
2. Then if u dont restart ur system then u'd have to load the modue (fdshe# insmod ath_pci) as root ofcourse...(actually, everything from hereafter is done as root)
3. u can create mutliple instances of ur physical card (NIC)..not more than one can be a client, and the other can be an accesspoint but this seemed unstable for me, therefore one instance per NIC is used here...to destroy an instance (ath0, ath1, ath2 ...etc) type
fdshe# wlanconfig ath0 destroy
4. to create a new instance type
fdshe# wlanconfig ath0 create wlandev wifi0 wlanmode ap
this will create an AP...u could set bssid by appending bssid ((watever bssid u want)), u can also set whether u want the AP to beacon or not.
5. u can set the ssid by iwconfig ath0 essid "ur essid"
ofcourse ur access point must have an address this can be done by ifconfig ath0 192.168.0.1 netmask 255.255.255.0 (or watever u choose it to be)
now u can connect to this network from ur clients...

* u can see ur connected clients using the command
fdshe# wlanconfig ath0 list
if u want to specify wat type of band ur ap should use u can use the iwpriv command in the following manner:
fdshe# iwpriv ath0 mode 1 for 802.11a
fdshe# iwpriv ath0 mode 2 for 802.11b
fdshe# iwpriv ath0 mode 3 for 802.11g
fdshe# iwpriv ath0 mode 0 autoselect 802.11a/b/g (default)

Labels: ,

Smilar pages