All Things Microsoft > Microsoft Software
SHORTCUT VORTEX
Gooseberry Clock:
It's not really a bug, seeing as you had to use a hex editor to do it. If any idiot could do it, then that would be the time for concern.
caustic:
But the point is that this *could* :rolleyes: be distributed widespread through emails for example, and lamers (and even us) worldwide would unzip the shortcuts to their desktop and then stare in confusement at their screen as explorer crashes. It has the potential to wreak quite some havoc as nothing needs to be executed. Although it would be way more potent if I could get it to work in any directory, as I can only seem to get it to work in specific paths ('C:\windows\desktop\' useful) even by using variables like %CD% and . , if anyone has any suggestions and if anyone else has recreated this phenomena i'd like to hear from you.
Master of Reality:
quote:Originally posted by caustic:
Quite easy, but sounds confusing. Make a file eg.123.txt and make a shortcut to it and then make a copy of this shortcut, open the first shortcut in a hex editor (i recommend winhex) and change the second reference to the oringinal filename (should be chracter-spaced unicode style) to the filename of the second shortcut (make sure the the shortcut has the same number of characters as the first file) and then hexedit the second shortcut so that it points to the first (*stops for air*). Press save and enjoy the fireworks. (use dos prompt to rename or delete the files when youre done)
--- End quote ---
huh?, i made an empty notepad file (named 123.txt), made a shortcut to it, copied the shortcut (renamed it 123a. Then i opened the first shortcut (just named 123) and there is no coding in the hex editor (hex workshop). so, what am i suppoed to do now?
[ March 24, 2002: Message edited by: Druaga ]
caustic:
Re :D ruaga
You should keep the copied shortcut to three characters (try 321.lnk). Open the first shortcut (123.lnk) in the hex editor (make sure it is the shortcut and not what it points to) and you should see something like (in ASCII view):
...\123.txt...
........3.9...
0.i....1.2.3..
.t.x.t........
its the second one you need to edit (1.2.3...t.x.t --> 3.2.1...l.n.k) and then do the same for the other one making it point to this one. Hope you understood, its a little awkward. www.winhex.com
Master of Reality:
it keeps opening what the shortcut points to (123.txt) instead of the actual shortcut (123.lnk). so how do i get it to edit the shortcut , not the file??
[ March 26, 2002: Message edited by: Druaga ]
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version