Re: Backwards Message Hack

Article: 7344 of alt.hackers
From: mjhaisma@eos.ncsu.edu (Michael John Haisma)
Newsgroups: alt.hackers
Subject: Re: Backwards Message Hack
Date: 12 Feb 1995 16:19:16 GMT
Organization: North Carolina State University, Project Eos
Lines: 45
Approved: What do I have to do, beg?
Distribution: world
Message-ID: 3hlce4$37u@taco.cc.ncsu.edu
Reply-To: mjhaisma@eos.ncsu.edu (Michael John Haisma)
NNTP-Posting-Host: c00100-100lez.eos.ncsu.edu
Keywords: kibo, drugs, satanism, clinton
Originator: mjhaisma@c00100-100lez.eos.ncsu.edu
Status: RO

In article <jm7FlSk4g9gE078yn@sky.net>, muralynd@sky.net (Muralynd)
writes:
> OBhackneedhelp!!! I have NO battery on my motherboard, that's no
>problem, I can just solder a new battery connection.... BUT I don't
>know which side is negative. I don't have a voltmeter... How can I
>figure this out (No manuals either).
>

Hook up a LED to the battery connection. Since the LED will only light when
current goes from positive to negative, it should be no problem determining
which side is which.

BTW, that doesn't look like you posted an

Obhack: Using a hex editor to make windoze display my name on the window bars.
Just kidding, I hate when people post crap like that :)

Obreallymyhack: Writing a "multitasking" copy program for the old
1541 drive
for the C64(actually, I had a 128).  Basically, the copy program sat in the
limited RAM on the drive, while I whiled away my time on the modem.  How did I
get both to programs to execute simultaneously?  By using the built-in monitor
on the 128, I manually changed the code of my terminal program so that instead
of changing the color options (something I used once, then never again) it
vectored to the code that loaded my copy program onto the drive. Needless
to say
it took a long time to do this and I felt really stupid for not just using a
file editor.  Plus, it's a million times easier to use an assembler that allows
macros and labels.  I guess the only real benefit I gained was the fact
that now
I have to use a monitor in the lab to write all my programs for an assembly
language class, and I have no trouble with it at all(unlike the other
students).

Unix Question: Yet again I prove my incompetence with the Unix environment.  I
can't figure out why the command(s)

ps -aux|grep <process name>|grep -v grep|cut -f2 -d" "|kill

Won't kill the process(es) with that name.  If I leave off the kill, the
command returns the pid(s) correctly, but kill says "too few
arguments".
What am I doing wrong with this line?  I have circumvented the problem by
using a temp variable, but that's not a very pretty hack.

Mike
--
Michael J. Haisma              | Any questions, comments, or flames?
email: mjhaisma@eos.ncsu.edu   | Please send email to president@whitehouse.gov

Child Child Child Child Child Child Child Child

Back to index