createsymboliclinka broken vista beta 2

HI,
CreateSymbolicLinkA is broken on Vista Beta 2. It uses the first parameter twice and ignores the second.
CreateSymbolicLinkW operates correctly.
- Faber

so? everybody should be using unicode in their programs now, anyway.
"Faber" wrote:

HI,
CreateSymbolicLinkA is broken on Vista Beta 2. It uses the first parameter twice and ignores the second.
CreateSymbolicLinkW operates correctly.
- Faber

Hi,
CreateSymbolicLinkA is broken on Vista Beta 2. It uses the first parameter twice and ignores the second parameter.
CreateSymbolicLinkB operates correctly
- Faber

Hi,
CreateSymbolicLinkA is broken on Vista Beta 2. It uses the first parameter twice and ignores the second parameter.
CreateSymbolicLinkB operates correctly
- Faber

See step number 4 and step number 10:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windows.vista.general&tid=85baaee2-adb8-455e-b81e-17de55b4b4f0&cat=en_US_9CA88DDB-D18D-FA0E-A366-6E527B0FBA67&lang=en&cr=US&p=1
"faber" wrote:

Hi,
CreateSymbolicLinkA is broken on Vista Beta 2. It uses the first parameter twice and ignores the second parameter.
CreateSymbolicLinkB operates correctly
- Faber

Sorry for posting 3 times. The MS newsgroup website claimed it could not post although it it.
I realize this is beta, i was not complaining, i was reporting. I can woukd around the issue easily. I did search groups and web, and there was not any report like this. If this is not the right forum to post this finding, what is ?
- Faber
"Mark D. VandenBerg" schrieb im Newsbeitrag

See step number 4 and step number 10:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windows.vista.general&tid=85baaee2-adb8-455e-b81e-17de55b4b4f0&cat=en_US_9CA88DDB-D18D-FA0E-A366-6E527B0FBA67&lang=en&cr=US&p=1
"faber" wrote:
Hi,
CreateSymbolicLinkA is broken on Vista Beta 2. It uses the first parameter twice and ignores the second parameter.
CreateSymbolicLinkB operates correctly
- Faber

My point was:
Shouldn't you be asking the software manufacturer why their software does not work with Windows Vista (an operating system that does not exist yet)?
"faber" wrote:

Sorry for posting 3 times. The MS newsgroup website claimed it could not post although it it.
I realize this is beta, i was not complaining, i was reporting. I can woukd around the issue easily. I did search groups and web, and there was not any report like this. If this is not the right forum to post this finding, what is ?
- Faber

Mark,
The API I reported to be errorneous was called by a small test programm i wrote myself. There is only the c++ source and the win32 api CreateSymbolicLink involved.
The c++ source contains just the single line CreateSymbolicLinkA("name1","name2",0), which errorneously creates a symlink "name1" pointing to itself, and CreateSymbolicLinkW(L"name1",L"name2",0), which successfully creates a symlink "name1" pointing to "name2".
I figure that MS would want to fix it and I am really puzzled that this was not even discussed anywhere.
- Faber
"Mark D. VandenBerg" schrieb im Newsbeitrag

My point was:
Shouldn't you be asking the software manufacturer why their software does not work with Windows Vista (an operating system that does not exist yet)?
"faber" wrote:
Sorry for posting 3 times. The MS newsgroup website claimed it could not post although it it.
I realize this is beta, i was not complaining, i was reporting. I can woukd around the issue easily. I did search groups and web, and there was not any report like this. If this is not the right forum to post this finding, what is ?
- Faber

Sounds like something you should report as a bug, I guess. However, MSFT does not use this discussion forum for official bug reports.
"faber" wrote:

Mark,
The API I reported to be errorneous was called by a small test programm i wrote myself. There is only the c++ source and the win32 api CreateSymbolicLink involved.
The c++ source contains just the single line CreateSymbolicLinkA("name1","name2",0), which errorneously creates a symlink "name1" pointing to itself, and CreateSymbolicLinkW(L"name1",L"name2",0), which successfully creates a symlink "name1" pointing to "name2".
I figure that MS would want to fix it and I am really puzzled that this was not even discussed anywhere.
- Faber

"faber" wrote:

CreateSymbolicLinkA is broken on Vista Beta 2. It uses the first parameter twice and ignores the second parameter.
CreateSymbolicLink[W] operates correctly

I recall seeing at least one discussion thread where this issue was known September 2005, but no feedback, follow-up or confirmation that it was even reported as a bug.
For what its worth, developer-related Vista discussion groups are listed at http://msdn.microsoft.com/windowsvista/support/forums/. Although other Vista-related development groups such as WinFX are NNTP accessible, these particular Vista-specific developer groups are web-based or read-only RSS access only, last I knew.
Reporting a bug starts with the "Feedback" link on the Vista desktop. I honestly don't know what your experience will be with trying to use the "reporting a problem" section there; I've only seen its operation in context of Vista beta testers.
Because its an SDK issue, you might also use the "Send comments about this topic to Microsoft" link in the CreateSymbolicLink documentation. http://msdn.microsoft.com/library/en-us/fileio/fs/createsymboliclink.asp
Alan Adams

Thank you for your helpfuil post. I tried both the msdn feedbar as well as the web-only vista general development msdn forum. I hope the message reaches the right individual now :)
- Faber
"Alan Adams" schrieb im Newsbeitrag

"faber" wrote:
CreateSymbolicLinkA is broken on Vista Beta 2. It uses the first parameter twice and ignores the second parameter.
CreateSymbolicLink[W] operates correctly
I recall seeing at least one discussion thread where this issue was known September 2005, but no feedback, follow-up or confirmation that it was even reported as a bug.
For what its worth, developer-related Vista discussion groups are listed at http://msdn.microsoft.com/windowsvista/support/forums/. Although other Vista-related development groups such as WinFX are NNTP accessible, these particular Vista-specific developer groups are web-based or read-only RSS access only, last I knew.
Reporting a bug starts with the "Feedback" link on the Vista desktop. I honestly don't know what your experience will be with trying to use the "reporting a problem" section there; I've only seen its operation in context of Vista beta testers.
Because its an SDK issue, you might also use the "Send comments about this topic to Microsoft" link in the CreateSymbolicLink documentation. http://msdn.microsoft.com/library/en-us/fileio/fs/createsymboliclink.asp
Alan Adams

"faber" wrote:

Thank you for your helpfuil post. I tried both the msdn feedbar as well as the web-only vista general development msdn forum. I hope the message reaches the right individual now :)

No problem; you're welcome. I've not had to use the SDK feedback myself, but I've seen good things said about them typically being responsive and getting the issue appropriately routed.
For what it's worth, when looking at the kernel32!CreateSymbolicLinkA function under the debugger, I would assert its actually the /second/ parameter being "duplicated". i.e. The string with the symbolic link name is ignored and the target string is used twice.
(It's using kernel32!Basep8BitStringToStaticUnicodeString to perform the conversion, and this routine re-uses the same thread-local string memory location each time you call it. Perhaps appropriate for an API where there is only one input string to convert, but not appropriate for kernel32!CreateSymbolicLinkA.)
Alan Adams