Windows 10: Exporting files from a web viewer

I regularly export .tiff files from prizm viewer thru internet explorer (i have to use IE as the large corporation i'm pulling these blueprints from has it set up to only work in IE). I was recently upgraded to windows 10 pro and when i export a file i'm always at the same starting point. so each page of a print that i export i have to navigate thru the maze of folders to get to where i want to put the file. Windows 7 would always go back to the previous folder you had exported to(like save as does for a document). Is there any way to change this setting? Also, slightly less important but still annoying - when exporting a file the view settings i want (list- no details) always go back to default. Anyone have any ideas?

:)

 

Export All Administrative Events to Excel


To analyze events, from the Windows Event Viewer, there is a simple way to export all Administrative Events to Excel, with PowerShell.

Exporting all Administrative Events to Excel is a simple two Step process, as described here:

Step 1 - Create the Administrative Events View .xml file

1. Open Eventviewer (%windir%\system32\eventvwr.msc)
2. Navigate to: Event Viewer (Local) > Custom Views > Administrative Events
3. In the “Actions” pane select “Filter Current Custom View”.
4. Select the the XML tab.
5. Press Ctrl+A to select all the XML code of the Custom View.
6. Open a notepad, paste the selected code and save the file to your Desktop as AdmEvtView.xml

Step 2 - Create the csv file with the events

1. Download the ExportEvtCSV.zip file, which contains the script ExportEvtCSV.ps1 and unzip it, on your Desktop.
   It's not a fancy script, just basic PowerShell commands to create a csv file on the Desktop.
2. In Windows Search, type “ISE” (without the quotes) to open “Windows PowerShell ISE” and Run as administrator
   
3. To allow running the script, change the ExecutionPolicy, for this session. To do that, in the Console pane type:
   Code:
   
   Code:

   Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass -force

4. In the Windows PowerShell ISE, open and run the script: ExportEvtCSV.ps1
   The script will create a csv file with a name YYYYMMDD.HHMM.csv on the Desktop
5. When done, open the newly created .csv file, format the columns as needed and optionally save it as .xlsx, if you wish.

That’s it! You now have all the Administrative Events in Excel for filtering and further analysis.

Now to the more technical hard stuff... *Confused

There is a reason for running the script from within PowerShell ISE!

It would be great if everything was also working perfectly, when running the script from an elevated PowerShell too.

We can run it from an elevated PowerShell, which means that you just follow the Step 1, as above but for the Step 2 instead of the ISE you run the script from an elevated PowerShell.

The problem is that it will work only for anybody who has en-US format for the dates. Everyone else, who has another format (i.e. en-GB, fr-FR, el-GR etc.), the dates are not translated properly by Excel (although the script uses the –UseCulture switch) and remain as text in the en-US format.

I'm not sure if this a bug of the "export-csv" cmdlet, but although it runs the way it supposed to from within the ISE, from PowerShell there is a problem with the dates format.
As I haven’t found a way to overcome this obstacle, any suggestion from the PowerShell gurus of the forum (like my good friend Shawn @Brink, for instance), is welcome.

 

Changing file viewer in File Explorer

If that's the case, kindly try the following steps below:

• Reset to the Microsoft recommended settings.
• Choose default apps by file type.

We also suggest you to uninstall and reinstall your preferred photo viewer, you may want to try the 64 bit version of the app if you are using a 64 bit version of Windows 10.

 

Vulkan Hardware Capability Viewer 1.4 released

A new version of the Vulkan Hardware Capability Viewer is now available for all platforms (Windows, Linux, Android)...

New features

• Added support for new features and properties provided via VK_KHR_GET_PHYSICAL_DEVICE_PROPERTIES_2
  • Currently supported:
    • VK_KHR_push_descriptor
    • VK_EXT_discard_rectangles
    • VK_KHX_multiview
    • VK_NVX_multiview_per_view_attributes
• Reports can now be saved to disk via command line using the -s argument (without invoking the UI)
  • Example : vulkanCapsViewer -s my_device.json
• Added pipeline cache UUID
• Exported JSON is now compatible with vkjson_info from LunarG SDK
• Added Android platform info
  • Device model and manufacturer
  • Build information
• UI improvements
  • Updated layout and UI scaling
  • Support for high DPI scaling
  • Touch scrolling for mobile devices (Android)