The MASM Forum Archive 2004 to 2012

General Forums => The Campus => Topic started by: anuradha on June 03, 2007, 03:25:53 AM

Title: risk
Post by: anuradha on June 03, 2007, 03:25:53 AM
hi guys
i just want to know that is there any risk in assembly???
i'm talking about hardware
if some programe crashes is it possiable to damege hardware???
Title: Re: risk
Post by: hutch-- on June 03, 2007, 04:23:42 AM
A very long time ago you could damage a monitor in DOS if you did something really bad with video that was not supported by the monitor but in modern operating systems its much harder to damage anything much as most true low level access is difficult to do in a protected mode operating system. In 32 bit Windows, just write good clean code and you will have few problems.
Title: Re: risk
Post by: Vortex on June 03, 2007, 08:18:24 AM
anuradha,

It can happen that your application coded with Masm freezes if there is a serious problem but you can kill easily the process using the task manager.
Title: Re: risk
Post by: daydreamer on June 03, 2007, 11:24:22 AM
don't worry, in that case you must be very skilled to write a driver, that either messes with overclock GPU or accesses one of the modern motherboards that can overclock cpu/memory and pci/agp clock freq so it damages stuff
not cooled modern harddrive and constantly write/read for hours and hours without downtime and it burned
Title: Re: risk
Post by: anuradha on June 03, 2007, 12:00:37 PM
thank you all  :U :U :U
Title: Re: risk
Post by: evlncrn8 on June 03, 2007, 12:53:45 PM
language probably doesnt matter, c/asm/delphi whatever, all can be bad
if the code is bad.... hardware damage is rare, you could damage cd/dvd drives
by sending ioctl's too many times (invalidating the region etc), but to do so
'randomly' (ie: sending a random / bad packet) would be quite rare...

most likely you'll crash your program or bsod the os...
Title: Re: risk
Post by: drhowarddrfine on June 03, 2007, 01:06:00 PM
Well, apparently some of your have forgotten HACF and BCF. (http://www.kettering.edu/~jhuggins/humor/opcodes.html)
Title: Re: risk
Post by: anuradha on June 05, 2007, 11:10:45 PM
hey  drhowarddrfine
what is  this HACF AND BCF
Title: Re: risk
Post by: u on June 05, 2007, 11:46:25 PM
 :green2 he linked to it...  ::) . And maybe I should explain that it is a joke.  :P
Title: Re: risk
Post by: CoR on June 08, 2007, 10:27:54 AM
 :green2 :green2 :green2

CMD = CPU Melt down - warning: if CPU is fast enough IP will never be incremented  :cheekygreen:
Title: Re: risk
Post by: anuradha on June 08, 2007, 06:11:11 PM
once again thak you all  :U  :U  :U  :U
Title: Re: risk
Post by: donkey on June 09, 2007, 12:36:58 AM
Quote from: drhowarddrfine on June 03, 2007, 01:06:00 PM
Well, apparently some of your have forgotten HACF and BCF. (http://www.kettering.edu/~jhuggins/humor/opcodes.html)

Hey Doc,

That's hilarious :) The IAI (Inquire and ignore) instruction reminds me of my boss.

Donkey