Coded zone

The place where all the coded stuffs reside.

Wednesday, January 03, 2007

Oops 16bit assembly

I tried to mess with some executables. I have
been using a Desktop manager and it is a trial version. So I tried to mess with their codes. And before
I could do anything I needed Assembly language to be run in my computer. I wanted to run some hello world
stuffs, those codes I had done previously, and which were familiar to me before
I used windows XP service pack2 .

I used to  run those codes in win98 and winxp(sp1).

Now after 1-2 years , I can't run TASM .
While I tried to compile and link using TLINK to  a "hello world" assembly
program in Windows, it gives an error like :

"16 bit MS-DOS Subsystem
c:\windows\system\cmd.exe -tlink ara.obj
X#=0D,CS=01B7 IP=00000231. The NTVDM CPU has encountered an unhandled exception.
Choose 'close' to terminate the application."




Then it gives a "Close" and "Ignore" options over a dialog button.
At both cases I can't link the obj file with the linker. This is a bullshit.
Windows takes all the control over the Operating System and what am I . Nothing.
A user who can't level up . Damn!!.


 I searched over the internet all around but everyone says: use 32 bit programming codes. and use TASM32 and TLINK32.

 Nah I don't wanna do that. I need TASM and TLINK cuzz I like playing with 16 bits. They are easier and give more control to me. 32 bits !! why 32 bits. If I am the programmer I need all the controls. Computers are for me , I am not for computers. Humans modify computers .. If computers start modifying humans thats unfair.
If I don't find a solution I have the solution, I will go back to windows98 and the service pack1 windows. Have the job done and return back. Thanks God I kept backup of all these.


Sources that I was using : 

Assembly Language for NewBies

0 Comments:

Post a Comment

<< Home