So far I have only filedisk booted from the PE_10圆4_US_M-WB.vhd, and also made other builds from it. I want to comment I have being making (intentionally) all my tests in a PC with only 2 GB of Ram, it usually runs Win10x86, but booting from a Win10圆4 PE, Mini-10圆4.vhd LZX compresed or WImboot installed your Make_WinPE program runs very fine, also from a PE_10圆4_US_M.wim the program runs fine, and additionally from any of the mentioned also VHD_WIMBOOT runs fine, and I was able to make a 500 MB PE_10圆4_US_M-WB.vhd that consumes less than 500 MB of Ram, just after filedisk booting, even SVBus_INST_Trusted installed fine the SVBus driver in it. I f you how to do it, please share the info. I made first a pair of commands, but latter decided to better make 2 shortcuts including required parameters, and this let me change the icons to make them look better, and it worked flawlessly, but it has to be done every boot just as selecting keyboard layout, or screen resolution, by the way MultiMonitorTool is not really required in MEDIUM version as the screen resolution can be selected manually in the Windows program for that task, and it works perfectly fine.īut if the volume control in shown in Task Bar before selecting the desired audio output, then the trick don't work.ĭuring one of my tests I did something and the volume control closed, and not present in Task bar anymoe, and then I was able to do the change, as it was shown after I ran the volume control again, but so far I'm not able to make disapear that icon from task bar to my willd. Test it by loading and unloading it: launchctl load ~/Library/LaunchAgents/ fact I didn't take that solution from 10XPE, googling I found a comment about a command using nircmd.exe to switch the audio device, and I decided to adapt it to this case, when I was going to add nircmd.exe to System32, to test if this works in this case, I noticed it was already there but never saw it before. Touch "$flagLocation/.metadata_never_index"Ĭreate a plist file ~/Library/LaunchAgents/ Mv "$flagLocation/$flagRemoved" "$flagLocation/.metadata_never_index" Script on the OS that wants to index the drive #!/bin/bash Mv "$flagLocation/.metadata_never_index" "$flagLocation/$flagRemoved" Script for OS that wants to hide a drive from spotlight #!/bin/bashįlagRemoved=".ney_the_index" # a new name Make sure it's executable chmod +x ~/script.sh Here are some ways to add a script that will launch at login : Įdit : Method using bash scripts and plist filesįirst create a startup script. The linked post also lists other ways to programatically alter the spotlight exclusions. When booting from external DriveB and you want to re-enable spotlight perhaps you could have your startup script execute: rm /Volumes/DriveB/.metadata_never_index When booting from DriveA (when you want to disable spotlight indexing for External DriveB) you could execute : touch /Volumes/DriveB/.metadata_never_index You could have a script that runs at startup that employs the technique suggested in this post Is there a way to make Spotlight index only the drive which is currently booted? In this way when I'm booted off my external drive I'll get results only from the external drive, and same with the internal drive. It seems as though the Spotlight exclusions are per drive, which is not ideal in this scenario. However, this also prevents me from searching for files on my internal drive, when I'm booted off my internal drive! Clearly this is something that I don't want. This prevented files and apps from my internal drive from showing up. I tried circumventing this issue while on my external drive by creating a Spotlight exception for internal drive. However, I am only interested in running the application from the drive I've booted off of. I find it annoying that, whenever I search for something (such as an application) when I'm in either OS when the external drive is connected, I get results from both my external and internal drive. This is in conjunction to my current internal drive which also is running macOS. Sometimes I use an external drive with macOS on it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |