How to guarantee so...
 
Notifications
Clear all

How to guarantee something everybody accepts

3 Posts
2 Users
0 Likes
217 Views
iruiper
(@iruiper)
Posts: 145
Estimable Member
Topic starter
 

Hello everybody,

I have been lately involved in a report relating the most valuable and most famous Link Files.

The most important conclussions I have come to are based on the internal structure of these files, and although everybody in the community uses this information, does anyone know any official Microsoft webpage that guarantees this internal structure? I would be interested in referencing some "official-stamped" document with the structure I have parsed by myself.

Thanks in advance for your thougths!

 
Posted : 02/03/2009 5:58 pm
(@bithead)
Posts: 1206
Noble Member
 

Does THIS un-official document jive with what you have found?

Which is also posted HERE. (Is that "our" JimmyW?)

Per the AIR programming sites

As you'd expect, it being a Microsoft format, there's no official documentation on the file format itself. Microsoft expect you to use their COM objects and APIs to both read and write these files. Unfortunately we've got no way to get at these APIs from AIR.

However, some people - notably Jesse Hager - have reverse-engineered the binary format, at least well enough to read shortcut information from a .lnk file.

But having spent a day creating an AIR class that would write .lnk files according to Jesse's spec, I discovered that the minor errors and handful of unknown byte strings in Jesse's document really, really mattered. Despite doing a number of tests (comparing AIR-generated files to Windows-generated files, fixing byte alignment, adding Unicode support) nothing I did resulted in a working shortcut, at least on Vista. Eventually I was forced to throw in the towel, as it was proving more effort than reward.

 
Posted : 02/03/2009 6:30 pm
iruiper
(@iruiper)
Posts: 145
Estimable Member
Topic starter
 

Thank you BitHead.The reference you point out is very useful for practical purposes, but I think I will finally 'put the blame on an EnCase EnScript' and I hope that mentioning a so much accepted tool will do.

 
Posted : 03/03/2009 4:02 am
Share: