Some Lame assembler prog

Hey ppl,

I have some code that you could use in fooling your friends on DOS / Win9x / Me boxes.
And it is *not* a copy/paste work, altough I'am sure this is writen elsewhere before me (perhaps in some assembler tutorial or so)

This is, in the wrong hands, script kiddie nfo. I know it.
But it can also be a fun tool.

-a 100
mov ax,40
mov dx,ax
mov ax,1234
mov [0072],ax
jmp f000:e05b

-r cx
:10
-n thename.com
-w

-q

This little prog, the last 5 lines are used to give it the name and write it to the disk, is only 10 bytes long and extremly fast.

It does a reset of your computer.

so you assemble this, type thename.com [Enter] and your computer reboots. If you put this in an autoexec.bat you can have some fun with a looping PC. (thats the lame part of this prog.)

Fun prog.

Ohh... nobody replies to this little, short, simple post.
I will keep it at top.

:)

thnx

I hab better chosen another title for this thread?
Or is the nfo useless / worthless / stupid ?

Quote:

---

Originally posted by VictorKaum
Hey ppl,

I have some code that you could use in fooling your friends on DOS / Win9x / Me boxes.
And it is *not* a copy/paste work, altough I'am sure this is writen elsewhere before me (perhaps in some assembler tutorial or so)

This is, in the wrong hands, script kiddie nfo. I know it.
But it can also be a fun tool.

-a 100
mov ax,40
mov dx,ax
mov ax,1234
mov [0072],ax
jmp f000:e05b

-r cx
:10
-n thename.com
-w

-q

This little prog, the last 5 lines are used to give it the name and write it to the disk, is only 10 bytes long and extremly fast.

It does a reset of your computer.

so you assemble this, type thename.com [Enter] and your computer reboots. If you put this in an autoexec.bat you can have some fun with a looping PC. (thats the lame part of this prog.)

---

I saw aprogram similar to this a few years back by scott meiner author of complete computer maint. This one does a hardware reset . He has another that will do a cold boot.
I do not think it exacly the same as VictorKaums though...good post Vic.

Here are some more useful debug scripts:

Testing ports:

The following debug routine will check the ports of the computer to allow you to know if ports are being detected or not.

Type debug to get to the "-"

Type D40:0

You should get several lines however the first line is the only important line which should read the following:

0040:0000 F8 03 F8 02 E8 03 E8 02 - 78 03 78 02 BC 03

F8 03 F8 02 E8 03 E8 02 78 03 78 02 BC 03
COM1 COM2 COM3 COM4 LPT1 LPT2 LPT3

The above graph shows you what the feed back means as far as port so if you se F8 03 this would be an indication that COM1 is being detected if you see 00 00 this is an indication that it is not being detect which could mean that hardware is bad or that it is disabled in CMOS.

Once you have finished looking at the information type Q and press enter to get out of Debug.

clearing Cmos:

A <ENTER>
MOV AX,0 <ENTER>
MOV AX,CX <ENTER>
OUT 70,AL <ENTER>
MOV AX,0 <ENTER>
OUT 71,AL <ENTER>
INC CX <ENTER>
CMP CX,100 <ENTER>
JB 103 <ENTER>
INT 20 <ENTER>
<ENTER> Note: Nothing is typed on this line
G <ENTER>
Q <ENTER>

Checking a joystick:


This test will test to see if you Joystick is present or not.

Type debug from the DOS prompt once at the "-".

Type i201

If you get a FF response attempt hold one of the main buttons on your joystick, and while holding the button down type i201 and see if a different response is given, each button on the joystick should return a different response. However some special joysticks such as the Microsoft Sidewinder which has more then 4-5 buttons may not return a response for all extra buttons because these buttons are generally controlled through software.

If a FF is still given on each of the buttons on the game paddle or joystick it is a good possibility that either the Joystick and or the Joystick port is bad. If possible attempt these steps with another known working joystick.

However if you are receiving different responses when pressing and holding the keys on the joystick, the computer hardware is working properly.



Type q and press enter to quit out of debug


erasing thr harddrive AND clearing cmos at the same time:

A:\>debug <enter>
-fcs:200 400 0 <enter>
-acs:100 <enter>
-xxxx:0100 mov ax, 0 <enter>
-xxxx:0103 mov ax, cx <enter>
-xxxx:0105 out 70, al <enter>
-xxxx:0107 mov ax, 0 <enter>
-xxxx:010a out 71,al <enter>
-xxxx:010c inc cx <enter>
-xxxx:010d cmp cx,100 <enter>
-xxxx:0111 jb 103 <enter>
-xxxx:0113 mov ax,302 <enter>
-xxxx:0116 mov bx,200 <enter>
-xxxx:0119 mov cx,1 <enter>
-xxxx:011c mov dx,80 <enter>
-xxxx:011f int 13 <enter>
-xxxx:012l int 20 <enter>
-xxxx:0123 <enter> (without typing anything.)
-g <enter>
program terminated normally
If you are doing this debug routine to clear out a possible virus turn off your computer and wait and turn back on.
-q <enter>

The above script will require you to fdisk and format the harddrive
It is a virus KILLER.

Hey antionline..you stole my joystick test! just kiddin. Good post

HaHa larryjs...bye the way did you see oblio's response to the java code I posted? check it out its very amusing!