kickenchicken57

I am having trouble clearing the event logs in Vista using Visual Basic. I can not wait to use the new .NET framework and this code must be done in VB. I am trying to use the Windows Event Log functions from "wevtapi.lib" in Visual basic. The functions are: EVT_HANDLE WINAPI EvtOpenChannelEnum( EVT_HANDLE Session, DWORD Flags ); http://msdn2.microsoft.com/en-us/library/aa385437.aspx BOOL WINAPI EvtNextChannelPath( EVT_HANDLE ChannelEnum, DWORD ChannelPathBufferSize, LPWSTR ChannelPathBuffer, PDWORD ChannelPathBufferUsed ); http://msdn2.microsoft.com/en-us/library/aa385412.aspx BOOL WINAPI EvtClearLog( EVT_HANDLE Session, LPCWSTR ChannelPath, LPCWSTR TargetFilePath, DWORD Flags ); http://msdn2.microsoft.com/en-us/library/aa385340.aspx Can someone please show me how to declare these functions and their types in VB?

Here is another thing about ImageX for all of those who are interested: "Although the ImageX.exe tool may appear to be a mechanism to create an image of a computer for backup, there are several issues that prevent using the ImageX.exe tool as a supported backup mechanism. The following are the issues when you use the ImageX.exe tool as a backup mechanism: • Extended attributes are lost. • The ImageX.exe tool only applies reparse points that are symbolic links or junctions. • Sparse files on the system are captured and applied. However, the sparse files are no longer sparse after they have been applied. • Object IDs on files are lost in the capture process or in the apply process." You can read the full article here: http://support.microsoft.com/kb/935467 EDIT: If anyone is interested in a method of scanning the hard drive for these NTFS features feel free to give me a PM

Bad news....Microsoft said to copy all of the split wims onto my target device and apply them from there. I am about finished with a utility that does the process automatically, but i would rather do it the right way, and apply directly from disk and wait between disks. Hopefully they release a solution in the near future.

Turns out this is an issue that microsoft is aware about and I should be hearing back with some sort of solution. I have already created a cutom splitter to allow for different sizes (ex. 400mb on the first CD and 650 on the rest). I dont like the idea of counting the files within the splitter because applying the split files would rely on the custom splitter creating a file that says how many files each SWM holds. This means that split files created with imageX will not be compatible with the new applying program Plus, the WIM_MSG_SPLIT message provides no way of knowing how many files where processed in that swm. It is only fired when one part has been created and holds this info: wParam = (LPWSTR *) lplpszPartPath; lParam = (LARGE_INTEGER *) pliPartSize; Which does not help much. Hopefully I will hear back about this soon.

when using the WIMGAPI to apply a split WIM file, you will get an error when it reaches a file that it cannot find in the file. In the callback method you get a WIM_MSG_INFO message before the error. I have been able to wait for this info and then call cin.get() to wait on the user to switch CD's than call WIMSetReferenceFile to set the reference to my next split WIM file on the next CD. Then when the WIM_MSG_ERROR case gets fired I return WIM_MSG_SKIP_ERROR and my program continues to extract the rest of the resources in the new WIM file. The only problem with that is when I return WIM_MSG_SKIP_ERROR the file that it gave me the error on does not get extracted. What I need is some way to force the WIMApplyImage function to retry a file after I set the reference to the new WIM file on the next CD. Any Ideas? EDIT: Here is another Idea. I was able to pause and wait for the next CD with no errors by pausing in the WIM_MSG_PROCESS case of the callback function. I found out how many files where in the first split WIM file by counting what had extracted before the error happened. By pausing after X amount of files in the WIM_MSG_PROCESS case, I was able to call WIMSetReferenceFile with the next WIM file and continue with no problmes. The only problem with this method is there currently no way to tell how many files are in a split WIM file. If you pass any part of a split WIM file to the WIMGetImageInformation function, It will only return the number of files in the WIM as a whole. The only semi-useful info that is returned is how many parts the WIM is split into, and what part number for the wim file you currently have open What I need to complete this is some more info on the WIMGAPI. 1) How to retry extracting a file after an error OR..... 2) How to tell how many files are in a split WIM file. With either one of those pieces of information, I should be able to finish a commandline tool to apply split wim files from across spanned CD's

It is possible to apply split wim files from the WIMGAPI but when the callback for the apply method tells me that it could not extract a file, I need to be able to swap the disc then and foce a retry. Does anyone have an idea on how to force the wimapplyimage function to retry?

It seems that there is no way to apply a split WIM (swm) file from multiple CD's. The WIMGAPI also seems to be lacking a method to detect when the last file of the first split WIM has been reached to allow you to swap CD's and continue from the next split WIM file from the set.