Author |
Topic: Files not visible when created in MIDIOX\syx (Read 1264 times) |
|
stevensrmiller
New Member
MIDI-OX Rules!
Posts: 2
|
 |
Files not visible when created in MIDIOX\syx
« on: Sep 28th, 2017, 12:58pm » |
 Quote  Modify
|
This isn't quite a MIDI question, but MIDIOX is doing something I don't understand and have never seen before. I'm using Windows 10.
If I use the SysEx View and do a Receive Manual Dump, my BCF2000's output appears in the Display Window. If I then do a Save As, and store the file into the default MIDIOX\syx directory, I can load that file into the Command Window with a Load File operation. When I pick "Load File," I get a typical Windows "Open" dialog box, which lists the seven .syx files that MIDI-OX put there when I installed it, and I also see the file I just created.
But, if I browse to that directory in the Windows File Explorer, my new file isn't visible. The other seven files are visible, but not mine. I know I'm looking at the same directory, because if I change the name of a file in either the Explorer or the Open dialog, the change appears in both windows.
If I save my data to my own user directory, I can see it in the File Explorer. But, if I cut and paste it to MIDIOX\syx, I can again only see it in MIDI-OX's Open dialog, not with the File Explorer. I can use the Open dialog to cut and paste it back to my user directory, but I cannot cut the file with the MIDI-OX Open dialog and then paste with the File Explorer. If I try, the paste operation shows a dialog saying "Could not find this item."
Somehow, files I create with MIDI-OX are invisible to me outside of MIDI-OX if I put them into MIDIOX\syx, even though the files already there after a fresh install of MIDI-OX are visible. I've tried changing permissions, logging in as Administrator, and a bunch of other things, none of which have any effect.
Does anyone know why files MIDI-OX creates are invisible outside of MIDI-OX when they reside in MIDIOX\syx?
|
|
 IP Logged |
|
|
|
Breath
Administrator
Gender: 
Posts: 1031
|
|
Re: Files not visible when created in MIDIOX\syx
« Reply #1 on: Sep 28th, 2017, 9:03pm » |
Quote Modify
|
The Windows installer will allow MidiOx to be loaded in the "Program Files (x86)" directory, but after WinXP you couldn't save there.
MS moved to files to a "Safer" area. Have a look in C:\Users\%Username%\AppData\Local\VirtualStore
All the best
Royce
|
|
IP Logged |
|
|
|
stevensrmiller
New Member
MIDI-OX Rules!
Posts: 2
|
|
Re: Files not visible when created in MIDIOX\syx
« Reply #2 on: Sep 29th, 2017, 4:22pm » |
Quote Modify
|
By golly, you're right! That explains everything. Thanks!
Here's a cut-and-paste with a bit more detail, for anyone else who finds this discussion:
VirtualStore is a UAC feature. If you turn off UAC or run a program as Administrator then VirtualStore will not be used to store data. Virtual Store folders are only used when the application doesn't contain the manifest which controls the UAC prompts. Legacy applications don't have this manifest and that's why it automatically stores data in VirtualStore folder. To even go more in detail User Account Control (UAC) virtualization covers 2 things based on what I have found:
- File System Virtualization
- Windows Registry Virtualization
File System Virtualization is UAC's File Virtualization Filter Driver
(%SystemRoot%\System32\Drivers\Luafv.sys) which implements file system virtualization.
So even windows registry has VirtualStore keys under HKEY_CLASSES_ROOT to store data from legacy software
that run with user access and not admin unless you specify to run as Administrator.
So in conclusion the UAC is responsible for VirtualStore and I think it's a good thing to keep the OS safe. Some users don't understand it and they think it's bad. I hope I explained enough to make it easy to understand what is it for and why it's there.
(Above from this forum.)
|
|
IP Logged |
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print