GetOpenFileName() Questions.
in [Win32 API]
|
From: Ulrich Eckhardt on 15 Jul 2008 05:21 Larry Lindstrom wrote: > But specifying my DVD burner, D:, that happens to have a > blank CD-RW in it, and a non-existent filename, returns either > "C:\xxxx" or "G:\xxxx" for the filename, whichever drive was > specified prior to the attempt to select D:. There is no filesystem on device D:, so you obviously can't select a path on it. I agree that it's ugly that it doesn't give you a proper error message. > I can copy files into the D: drive directory, though I didn't > try to burn them today. You can use the Explorer to drag files to the visual representation of the D drive, but I bet that you can't CopyFile() anything there. The point is that the Explorer(!) displays this drive as directory, just as it does with "My Computer" or the "System Control" (just guessing the name in English) or as it provides the ability to use symbolic links. However, at the filesystem level these directories don't exist and the symbolic links are just normal files - all this is implemented by the shell instead of the OS kernel! Now, what you can possibly do is go through the shell, too, but I haven't actually tried that. In order to write a file, that would be SHCreateStreamOnFile() or something similar, just browse the docs a bit. good luck Uli -- Sator Laser GmbH Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
From: Larry Lindstrom on 15 Jul 2008 16:50 Ulrich Eckhardt wrote: > Larry Lindstrom wrote: >> But specifying my DVD burner, D:, that happens to have a >> blank CD-RW in it, and a non-existent filename, returns either >> "C:\xxxx" or "G:\xxxx" for the filename, whichever drive was >> specified prior to the attempt to select D:. > > There is no filesystem on device D:, so you obviously can't select a path on > it. I agree that it's ugly that it doesn't give you a proper error message. > >> I can copy files into the D: drive directory, though I didn't >> try to burn them today. > > You can use the Explorer to drag files to the visual representation of the D > drive, but I bet that you can't CopyFile() anything there. The point is > that the Explorer(!) displays this drive as directory, just as it does > with "My Computer" or the "System Control" (just guessing the name in > English) or as it provides the ability to use symbolic links. However, at > the filesystem level these directories don't exist and the symbolic links > are just normal files - all this is implemented by the shell instead of the > OS kernel! > > Now, what you can possibly do is go through the shell, too, but I haven't > actually tried that. In order to write a file, that would be > SHCreateStreamOnFile() or something similar, just browse the docs a bit. > > good luck Thanks Uli: That's disappointing. I have an example of using the shell functions for this sort of thing. I'll look into it. I appreciate your input. Thanks Larry
From: Stefan Pendl on 15 Jul 2008 20:05 On Tue, 15 Jul 2008 13:50:53 -0700, Larry Lindstrom <nobody(a)nowhere.com> wrote: >Ulrich Eckhardt wrote: >> Larry Lindstrom wrote: >>> But specifying my DVD burner, D:, that happens to have a >>> blank CD-RW in it, and a non-existent filename, returns either >>> "C:\xxxx" or "G:\xxxx" for the filename, whichever drive was >>> specified prior to the attempt to select D:. >> >> You can use the Explorer to drag files to the visual representation of the D >> drive, but I bet that you can't CopyFile() anything there. The point is >> that the Explorer(!) displays this drive as directory, just as it does >> with "My Computer" or the "System Control" (just guessing the name in >> English) or as it provides the ability to use symbolic links. However, at >> the filesystem level these directories don't exist and the symbolic links >> are just normal files - all this is implemented by the shell instead of the >> OS kernel! >> The displayed folder is CSIDL_CDBURN_AREA ... 0x003b ... USERPROFILE\Local Settings\Application Data\Microsoft\CD Burning You should be able to place the file there. This will only work for Windows XP and higher. You will still need to search for a way to start the burn process through your application. --- Stefan Pendl Windows XP Pro SP 3 Celeron M 1.3 GHz 752 MB DDR RAM
From: Jerry Coffin on 15 Jul 2008 20:34 In article <rieq74t77m2dqiuo9cqcnik6vtgfe4dpd9(a)4ax.com>, stefan.pendl(a)nospam.com says... [ ... ] > You should be able to place the file there. > This will only work for Windows XP and higher. > You will still need to search for a way to start the burn process > through your application. http://msdn.microsoft.com/en-us/library/aa366450(VS.85).aspx -- Later, Jerry. The universe is a figment of its own imagination.
From: Larry Lindstrom on 16 Jul 2008 20:49 Jerry Coffin wrote: > In article <rieq74t77m2dqiuo9cqcnik6vtgfe4dpd9(a)4ax.com>, > stefan.pendl(a)nospam.com says... > > [ ... ] > >> You should be able to place the file there. >> This will only work for Windows XP and higher. >> You will still need to search for a way to start the burn process >> through your application. > > http://msdn.microsoft.com/en-us/library/aa366450(VS.85).aspx > Thanks Stefan, Jerry and Christian and Uni: I'm being called away to another project, but I think you have given me what I need to finish this up. I'll get back to you if I have more questions. Thanks Larry
|
Pages: 1 Prev: outputting a vertical bar on the commandline Next: Make a *.lib in VS2008 |