Re: A83: Help


[Prev][Next][Index][Thread]

Re: A83: Help




Take over apple?!?  Why don't we just reverse engineer an Apple ROM!  I've
done it to the plus...  try it!

>P.S. While you are taking over Apple, could you also get rid of Microsoft??
>;-)
>
>Robert Caldwell wrote:
>
>> actually i am a dedicated hacker and i have found no way around my own
>> system.  it isn't symbolised the way you said, it's more like you can
>> put anything in the toaster that YOU want (recording your presence), and
>> only YOU can get it out, anyone else touching the toaster will get
>> zapped (not killed, just a tingle).  the toaster can make poptarts too.
>> you can put something in one end of the toaster and someone else put
>> something in the other end, and only you two can access your own stuff
>> (of course you can tell it for other people to be able to touch it like
>> wife/husband).
>>
>> -Rob
>> ICQ:9188921 "No Sol to kill"
>> e-mail1:rc_ware@hotmail.com
>> e-mail2:rc_ware@yahoo.com
>> e-mail3:rc_ware@geocities.com
>> webpage:http://www.geocities.com/SiliconValley/Haven/4049/index.html
>>
>> {{True, for every scenario you thought of you found a solution,
>> but...for the
>> "dedicated" hacker, there is always a way. There is always a way around
>> any
>> possible protection scheme, no matter how elaborate! I really wouldn't
>> want
>> a system with such limited access, anyways.It's like buying a toaster
>> that
>> only lets you put toast in and never pops it out, and you can only make
>> toast on thursdays, unless there is a full moon, of course. Here's a
>> thought, if you really want the system to be read-only, dish out the
>> apps
>> on ROM cards! ;-)
>>
>> More later,
>> Nick
>>
>> Robert Caldwell wrote:
>>
>> > this seems like a good response, but not correct.  the system i
>> propose
>> > will contain an OS that only enables itself the ability to delete or
>> > rearrange file.  this means that you have to have a password to use
>> the
>> > deletion tool, and you also cannot at all costs use the HardDrive like
>> > the RAM (meaning no more looking up FATs or actually byte allocations
>> in
>> > memory).  this does bring down a lot of possible programs, but i
>> haven't
>> > seen a great game yet that needs to delete files on the harddrive.  i
>> > know saved games need to be cleaned out once in awhile, but that's why
>> i
>> > am putting a password protection on it, maybe i'll make a "deletable"
>> > file attribute that will allow that file to be deleted without
>> > confirmation.  virii were made by huge corporations in the first place
>> > in order for them to clean out their harddrive (deltree c:\*.* /y is
>> > usually used).  this isn't a hightech virus but it still gets the job
>> > done.  now the ability to delete massive amounts of files is gone (if
>> > the computer i propose is built).  since you can't send commands out
>> of
>> > the cpu like an OUT statement (unless you have priveladge of 0 which
>> you
>> > can't since that'll be my system only).
>> >
>> > this may sound stupid now, but until you see it you can't dis it
>> > (patience--spelling?).  for every hacker/cracker/virii scenario i came
>> > up with, i've also come up with a way to stop it.
>> >
>> > i can't say much more until i actually build the system and show you,
>> > but please feel free to criticize somemore.
>> >
>> > -Rob
>> > ICQ:9188921 "No Sol to kill"
>> > e-mail1:rc_ware@hotmail.com
>> > e-mail2:rc_ware@yahoo.com
>> > e-mail3:rc_ware@geocities.com
>> > webpage:http://www.geocities.com/SiliconValley/Haven/4049/index.html
>> >
>> > {{virii and hacking is ALWAYS possible no matter how tight you think
>> > your
>> > system is. if you want ppl to buy your system you gotta make it able
>> to
>> > do
>> > stuff, that would bring down the security so you will most definately
>> > have
>> > virii and hacking done on your system.
>> >
>> > >5)  anti-virii--the program will contain levels built in, the
>> > >multi-tasking system is built in also (windows isn't the built in
>> > >feature).  this means that if a file starts deleting or messing with
>> > >other files it will contact you about it and ask for a key
>> confirmation
>> > >that you are positive you want the files messed with.  if you delete
>> a
>> > >file, it is usually sent to the "recycling bin" but now its' name is
>> > >stored in a "temp" file where you can "empty your recycling bin" and
>> > >it'll ask you for confirmation.  this is the only way you can delete
>> > >files.  and for the case of saving over a file, it's simple, the
>> > program
>> > >can't have a file open without it having a header file saying that
>> that
>> > >file is used by the program.  (technical jargon)...just say that it
>> > >works, i've done some testing (trying to write virii in my mind) and
>> > >came up with deadend results (meaning the virii didn't work).
>> > >6)  unhackable--the cpu is unhackable, the privaledge (spelling?)
>> > levels
>> > >of each program don't allow it to read other programs' stuff (meaning
>> > no
>> > >"add-ons" allowed unless the company making the add-on gives me the
>> > code
>> > >and i'll place extra stuff in it to cross the system).  this doesn't
>> > >mean the cpu is hackable...it's just for add-ons.  it has a built in
>> > >hex/code/etc. editor that is upgradeable also (but only by me or my
>> > >company--when it's operational), this means that this is the only way
>> > to
>> > >view a file in hex, also meaning that you can't disassemble a program
>> > if
>> > >it is "sealed" (another new feature).  a "sealed" program is like an
>> > >uninstallable/not read-able at all type feature.  whenever a program
>> > >that is "sealed" is installed in the system the filename is stored in
>> > an
>> > >"uninstall" list, in which the user can only delete the file using
>> the
>> > >uninstall program (which is also built in.}}
>> >
>> > ______________________________________________________
>> > Get Your Private, Free Email at http://www.hotmail.com}}
>>
>> ______________________________________________________
>> Get Your Private, Free Email at http://www.hotmail.com
>
>
>
><HTML>
>Whenever you do accomplish this feat (correction, <B><I>if</I></B> you
>accomplish this) I'll be amazed!
>
><P>More later,
><BR>Nick
>
><P>P.S. While you are taking over Apple, could you also get rid of Microsoft??
>;-)
>
><P>Robert Caldwell wrote:
><BLOCKQUOTE TYPE=CITE>actually i am a dedicated hacker and i have found
>no way around my own
><BR>system.&nbsp; it isn't symbolised the way you said, it's more like
>you can
><BR>put anything in the toaster that YOU want (recording your presence),
>and
><BR>only YOU can get it out, anyone else touching the toaster will get
><BR>zapped (not killed, just a tingle).&nbsp; the toaster can make poptarts
>too.
><BR>you can put something in one end of the toaster and someone else put
><BR>something in the other end, and only you two can access your own stuff
><BR>(of course you can tell it for other people to be able to touch it
>like
><BR>wife/husband).
>
><P>-Rob
><BR>ICQ:9188921 "No Sol to kill"
><BR>e-mail1:rc_ware@hotmail.com
><BR>e-mail2:rc_ware@yahoo.com
><BR>e-mail3:rc_ware@geocities.com
><BR>webpage:<A
>HREF="http://www.geocities.com/SiliconValley/Haven/4049/index.html">http://
>www.geocities.com/SiliconValley/Haven/4049/index.html</A>
>
><P>{{True, for every scenario you thought of you found a solution,
><BR>but...for the
><BR>"dedicated" hacker, there is always a way. There is always a way around
><BR>any
><BR>possible protection scheme, no matter how elaborate! I really wouldn't
><BR>want
><BR>a system with such limited access, anyways.It's like buying a toaster
><BR>that
><BR>only lets you put toast in and never pops it out, and you can only
>make
><BR>toast on thursdays, unless there is a full moon, of course. Here's
>a
><BR>thought, if you really want the system to be read-only, dish out the
><BR>apps
><BR>on ROM cards! ;-)
>
><P>More later,
><BR>Nick
>
><P>Robert Caldwell wrote:
>
><P>> this seems like a good response, but not correct.&nbsp; the system
>i
><BR>propose
><BR>> will contain an OS that only enables itself the ability to delete
>or
><BR>> rearrange file.&nbsp; this means that you have to have a password
>to use
><BR>the
><BR>> deletion tool, and you also cannot at all costs use the HardDrive
>like
><BR>> the RAM (meaning no more looking up FATs or actually byte allocations
><BR>in
><BR>> memory).&nbsp; this does bring down a lot of possible programs, but
>i
><BR>haven't
><BR>> seen a great game yet that needs to delete files on the harddrive.&nbsp;
>i
><BR>> know saved games need to be cleaned out once in awhile, but that's
>why
><BR>i
><BR>> am putting a password protection on it, maybe i'll make a "deletable"
><BR>> file attribute that will allow that file to be deleted without
><BR>> confirmation.&nbsp; virii were made by huge corporations in the first
>place
><BR>> in order for them to clean out their harddrive (deltree c:\*.* /y
>is
><BR>> usually used).&nbsp; this isn't a hightech virus but it still gets
>the job
><BR>> done.&nbsp; now the ability to delete massive amounts of files is
>gone (if
><BR>> the computer i propose is built).&nbsp; since you can't send commands
>out
><BR>of
><BR>> the cpu like an OUT statement (unless you have priveladge of 0 which
><BR>you
><BR>> can't since that'll be my system only).
><BR>>
><BR>> this may sound stupid now, but until you see it you can't dis it
><BR>> (patience--spelling?).&nbsp; for every hacker/cracker/virii scenario
>i came
><BR>> up with, i've also come up with a way to stop it.
><BR>>
><BR>> i can't say much more until i actually build the system and show
>you,
><BR>> but please feel free to criticize somemore.
><BR>>
><BR>> -Rob
><BR>> ICQ:9188921 "No Sol to kill"
><BR>> e-mail1:rc_ware@hotmail.com
><BR>> e-mail2:rc_ware@yahoo.com
><BR>> e-mail3:rc_ware@geocities.com
><BR>> webpage:<A
>HREF="http://www.geocities.com/SiliconValley/Haven/4049/index.html">http://
>www.geocities.com/SiliconValley/Haven/4049/index.html</A>
><BR>>
><BR>> {{virii and hacking is ALWAYS possible no matter how tight you think
><BR>> your
><BR>> system is. if you want ppl to buy your system you gotta make it able
><BR>to
><BR>> do
><BR>> stuff, that would bring down the security so you will most definately
><BR>> have
><BR>> virii and hacking done on your system.
><BR>>
><BR>> >5)&nbsp; anti-virii--the program will contain levels built in, the
><BR>> >multi-tasking system is built in also (windows isn't the built in
><BR>> >feature).&nbsp; this means that if a file starts deleting or messing
>with
><BR>> >other files it will contact you about it and ask for a key
><BR>confirmation
><BR>> >that you are positive you want the files messed with.&nbsp; if you
>delete
><BR>a
><BR>> >file, it is usually sent to the "recycling bin" but now its' name
>is
><BR>> >stored in a "temp" file where you can "empty your recycling bin"
>and
><BR>> >it'll ask you for confirmation.&nbsp; this is the only way you can
>delete
><BR>> >files.&nbsp; and for the case of saving over a file, it's simple,
>the
><BR>> program
><BR>> >can't have a file open without it having a header file saying that
><BR>that
><BR>> >file is used by the program.&nbsp; (technical jargon)...just say
>that it
><BR>> >works, i've done some testing (trying to write virii in my mind)
>and
><BR>> >came up with deadend results (meaning the virii didn't work).
><BR>> >6)&nbsp; unhackable--the cpu is unhackable, the privaledge (spelling?)
><BR>> levels
><BR>> >of each program don't allow it to read other programs' stuff (meaning
><BR>> no
><BR>> >"add-ons" allowed unless the company making the add-on gives me
>the
><BR>> code
><BR>> >and i'll place extra stuff in it to cross the system).&nbsp; this
>doesn't
><BR>> >mean the cpu is hackable...it's just for add-ons.&nbsp; it has a
>built in
><BR>> >hex/code/etc. editor that is upgradeable also (but only by me or
>my
><BR>> >company--when it's operational), this means that this is the only
>way
><BR>> to
><BR>> >view a file in hex, also meaning that you can't disassemble a program
><BR>> if
><BR>> >it is "sealed" (another new feature).&nbsp; a "sealed" program is
>like an
><BR>> >uninstallable/not read-able at all type feature.&nbsp; whenever
>a program
><BR>> >that is "sealed" is installed in the system the filename is stored
>in
><BR>> an
><BR>> >"uninstall" list, in which the user can only delete the file using
><BR>the
><BR>> >uninstall program (which is also built in.}}
><BR>>
><BR>> ______________________________________________________
><BR>> Get Your Private, Free Email at <A
>HREF="http://www.hotmail.com">http://www.hotmail.com</A>}}
>
><P>______________________________________________________
><BR>Get Your Private, Free Email at <A
>HREF="http://www.hotmail.com">http://www.hotmail.com</A></BLOCKQUOTE>
>&nbsp;</HTML>



Follow-Ups: