Windows (programmer's issue?)


Discussion Topic

Return to Forum List
Post a Reply
Messages 41 - 60 of total 187 in this topic << First  |  < Previous  |  Show All  |  Next >  |  Last >>

Ice climber
the ghost
Apr 10, 2010 - 02:45pm PT
Step 9 implies you are not logged in as root; which is reinforced by the $ in step 1. Root usually has a # as a prompt.

Try the tar xvf as root.

City of Orange, CA.
Topic Author's Reply - Apr 10, 2010 - 02:52pm PT
I did with sudo and verification as root with su using tar?
Knoppix is different than Red Hat with login and passwords.
At least the knoppix I have is. I still need a book.

No time to go back now. I'm re-arranging the C. As far as I
know there is no Linux wifi driver for some companies USB devices.
It should be worth some money if I can get it to work, but it is a lot
of work.

Mountain climber
Apr 10, 2010 - 03:10pm PT
Knoppix is a small device Linux that does not have much support. If you are trying to port it to an embedded device its great. If your trying to run your desktop it is less than great.

If you are looking for a specific driver then look at the companies website and see what drivers they have. Odds are, as you are finding out, Knoppix is most likely not among them.

Really, Ubuntu has the most drivers out there because it is fast becoming the Linux of choice for the masses. Wifi drivers being among the most sought after.

I would start there.

My 2 cents.


Apr 10, 2010 - 03:10pm PT
"Knoppix automatically logs you in as the restricted user "knoppix" -- not "root"! Therefore, you cannot perform functions that require root privileges, including many operations in the File Systems and User Account Management lab exercises."


Scroll down to "Getting a Root Shell Command Prompt"

City of Orange, CA.
Topic Author's Reply - Apr 10, 2010 - 03:28pm PT
I do not recommend dual boot systems. I used cfdisk and mkfs assigning
ext.2 for the format. It takes a lot of time though you know it's being
formatted close to a low level format. I then sliced the partions with
a somewhat different format.

Knoppix Gparted and or default install seems to default to a DOS file
system which Linux/Unix is not. Windows moved away from fdisk (I don't
know why?) and chkdsk I think predates fdisk though it is probably not
as complete.

Run cfdisk(Linux) with Knoppix instead of fdisk(MS DOS) and see how much
more complete it seems. cfdisk can be run and exited from easily even after
install. MSDOS reads sectors UNIX reads blocks. One of the reasons it was
more powerful than DOS with Windows.

Apr 10, 2010 - 03:34pm PT

I was giving you information how to extract and install the driver with root privileges to get running, ..... not how to make a dual boot.

City of Orange, CA.
Topic Author's Reply - Apr 10, 2010 - 04:17pm PT
step 10 shows they are extracted. :-)

What are they taking UNIX classes for? .bat files?
We use shell language not dos.bat's over here.

In the past I had a lot of time on Red Hat this knoppix
is a bit different and it appears they are adding scripts
and small programs. Linux admittedly has been known in the
past for breaking UNIX rules. In college that is what we
checked and .bat files were kept to assembly language class
on windows machines in a different computer "science class".
Seems a lot history->"a"rts folks are writing C"S" books today
that are sold in the stores?


Apr 10, 2010 - 11:40pm PT
So now compile it ....

City of Orange, CA.
Topic Author's Reply - Apr 10, 2010 - 11:45pm PT
It requires 5 code files that I see so far.

There are 2 other packages I am unsure about as pump
with ifup may do it with what I see so far. These 2 are
not part of this archive.

sfdisk -s will show partition blocks and is more complete than cfdisk.
Also see parted. All work with sectors prior to blocks.

All decompressed files were decompressed with tar in record
size of 8 blocks which is good. Enlarge 1st image to see.

btw, in OC next to where I bought a lap top is a small
business with just a couple employees. It is AEGIS Inc.

Trad climber
Apr 11, 2010 - 06:51am PT
Copy the tarballs into your home and half of this BS is avoided making the only privileged code to execute the `make install` as it writes to the system directories. something like this

cd ~
cp /mnt/medie/wireless-compat.tar.gz .
tar -xvzf wireless-compat.tar.gz
cd wireless-compat
./configure --with-desired-options
make install

That really should work for you without all this rando chown'ing of files just to get around directory perms....

City of Orange, CA.
Topic Author's Reply - Apr 11, 2010 - 11:21am PT
thanks for that, i'll try it but there is no driver only
a group inside that package? I had to take off the .tar.other.
Just .tar works fine.

here it is and i'm removing the above. Gary see blocks proceeding

Credit: BES1'st

Credit: BES1'st

Credit: BES1'st

Credit: BES1'st

Credit: BES1'st

Credit: BES1'st

Credit: BES1'st

Credit: BES1'st

Credit: BES1'st

Trad climber
Apr 11, 2010 - 11:34am PT

I'm happy to help you a bit. I used to port drivers from Linux to OpenBSD systems and I also used to write a driver here and there as well. You are def correct that there are chipsets that do not have working drivers. Sometimes the changes to existing drivers are as minimal as adding a #define and test for the chipset name (assuming it is a clone) and sometimes as dificult as getting a white paper for the chipset or *gack* reverse engineering one (NEVER FUN!).

Drivers in Linux are a special beast in that they are acutally parts of (or additions to) the kernel. All interface between the metal and the system must take place at a relatively low level in order for latency and inner-kernel communication to occur. When a person builds a custom kernel they specify various drivers and components to be built staticly into the kernel itself or built and loaded on demand as modules (man lsmod, insmod, rmmod). During the build process no elevated privilege is required. It is the writing/copying of the binary object files into the kernels module directories that require privilege.

As a sysadmin for over 12 years (uggggg :-\ ) I can tell you that figuring out how to do as much as possible as a regular user and only using su and sudo when needed can save you a lot of re-installing and headaches while you conquer the learning curve.

Anyway man email me and we can maybe talk a bit on IM and work through whatever problem you are having and it will probably be much easier than doing this on the taco.

Good luck! UNIX/*NIX really is worth it.


Big Wall climber
Reno NV
Apr 11, 2010 - 12:24pm PT
This thread should have been titled, "Windows programmer has issues".

City of Orange, CA.
Topic Author's Reply - Apr 12, 2010 - 11:13am PT
Hi Roman,
I thought of something cool with your script. I may post it later.
I did have that full package showing installed when running off of
a CD. The wifi device still did not work. I think there are 2 other
parts to it besides the group files within, noting I still don't see
a driver out of the 1/2 dozen or so that are linked to the groups.

Mainly for others -> teacher Gary && WBraun however you maybe interested.
Checking Unix processes with "ps prior to usage of top". (Recommended)
Credit: BES1'st

This image2 displays fakekeyd running as a process after system startup.
Credit: BES1'st

This image3 displays educated guesses seen by using the command ps aux and
has been further filtered for Gary's class decision.
Credit: BES1'st

This image4 displays usage of the service command to check what services
the processes are possibly providing. The service command does not appear
to allow for filtering with grep with or without usage of "regular
expressions also filtering" with grep?
Credit: BES1'st

Image5 displays all services given by service. ifupdown is a educated
guess of a service possibly associated to fakekeyd? Image6 showing network
manager(very likely) and set key are 2 other probabilities? Image7 shows
the final services. Also very likely associated to my wifif driver
questions is wpa-ifupdown. This latter I believe may provide better
solutions for normal users of wifi than does WEP, and may also be easier
for ISP's (public utility/communications/other entity etc.) to manage as
it may time out, so they don't need to manage, nor does the normal user?
Credit: BES1'st
Credit: BES1'st
Credit: BES1'st


City of Orange, CA.
Topic Author's Reply - Apr 14, 2010 - 06:54pm PT
WBraun, Roman, Skipt, Gary etc.,
any ideas? It's not working on Linux.

Posted on the internet are the 2 rtl errors as a working driver.
I compiled them and nuked them as they say. Prior to nuking I did
try them and they do not work. Not only that it appears they were
already installed by the CD. There are 2 other steps internally
dealing with registration and compiling that, however those 2 look
to already be installed?


Mountain climber
Apr 14, 2010 - 07:01pm PT
Werner charges $7,000 per pitch.

I am pretty close to that with computer work.

I charge a lot more when someone is incapable of asking a simple question.

Best, after much research I found that OS/2 is your only hope.

Go and get em'


Social climber
down south
Apr 15, 2010 - 01:11am PT
well, to start with, your LAN.. 192.168.x.x is not going to propogate to the DNS servers. You have to registar a domain name (,, whatever) with the ip address coming into you access point... e.g. cable, dsl... whatever. as far as the DNS's are concerned, you don't exist. nslookup uses domain name servers to resolve ip addresses into domain names, so if it doesn't know anything about your (SERVER????) then don't expect domain name resolution on windows or linux on any other OS.

IT ain't gonna happen.

City of Orange, CA.
Topic Author's Reply - Apr 15, 2010 - 01:40pm PT
192.168.*.* is really not relevant to non static accounts
with classless addressing. Most eth0++ hardware devices assign
NAT without software. Read pg. 259 of the Linux system admin
book in regards to 802.11 and wifi. They admit they don't
know much.

wifi AdHoc is for normal users, wifi infrastructure is more
complex than knowing about a 192.*.*.* assignment.

Roman, it appears you get bored with this, but it's very practical.

root@Microknoppix:/compat-wireless- .tmp_versions
root@Microknoppix:/compat-wireless- chmod ug-s *.*
root@Microknoppix:/compat-wireless- rm -f *.*

Line1 changed into a directory with all the file permissions set with a
sticky bit. Root or superuser at this time could not apply changes to the

Line2 removed the sticky bit "applied also to superuser root and group
root" and to all the files. The sticky bit was set by other than root I.

Line3 removed all the files in the directory after removing all the sticky

Line4 shows all went as planned. All files in the hidden directory were

I was able to shutdown, restart and reset root password in Linux single
mode after being locked out of my system by a screensaver displaying a
fire with a password prompt in the middle of the fire. My system was
apparently set to passwords unknown by the screensaver and I?

Final notes here about changing the mode of octal permission bits.
applies no sticky bit nor user or group id#'s and applies read and
write permissions to user=6, group=6, all others=6.

<chmod 666 filename> does not account for the sticky bit. This is literal
or numeric mode being 4=read 2=write 1=execute. It's 4(read)+2(write) permissions.

<chmod ug-s filename> This is symbolic mode. user and group - sticky.

Symbolic links are internal system links usually pointed to by system
startup files. I was not dealing with these with the above problems.
Symbolic mode is not a symbolic link.


City of Orange, CA.
Topic Author's Reply - Apr 15, 2010 - 07:59pm PT
Here are the makes and uninstall. make dep and make clean seem
to have been deprecated after the 90's. The warning with -e or E
is probably the check for pre-existence prior to writing. I did
not write the make files lacking -E.

It appears a public member of a C struct is attempting to access a 802.11 C union or a OO private or protected class member within another code

Credit: BES1'st

Credit: BES1'st

Credit: BES1'st

Credit: BES1'st

Credit: BES1'st

Credit: BES1'st

Credit: BES1'st

City of Orange, CA.
Topic Author's Reply - Apr 16, 2010 - 10:58am PT
A driver for this I don't think is worth my time. I'm still checking.

ENLWI-G - Encore Electronics, Inc.... ENUWI-N - 802.11n Wireless USB Adapter,
ENUWI-N3 - 802.11n Wireless USB Adapter. Manual ENLWI-G Manual; Note: This
device does not support Linux.

What started this was the driver being removed while at Starbucks
in Santa Ana on 4'th and Broadway while connected. This device
was purchased and registered by me for a XP system which is what
it was removed from by other than I.
Messages 41 - 60 of total 187 in this topic << First  |  < Previous  |  Show All  |  Next >  |  Last >>
Return to Forum List
Post a Reply
Our Guidebooks
Check 'em out!
SuperTopo Guidebooks

Try a free sample topo!

SuperTopo on the Web

Review Categories
Recent Route Beta
Recent Gear Reviews