Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Pk King X11

Member
  • Content Count

    3
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Pk King X11

  • Birthday 05/03/1994

Profile Information

  • OS
    Windows 10 x64
  1. To help prevent irreversible damage, this program is designed to be non-invasive. This program is solely reliant upon itself in terms of functionality hence why you can't rename, move nor delete the file while in use.. A similar effect can be done using other means but, this program isn't designed to be deployed in such a fashion. Especially with Windows 10, M$ has interwoven so many aspects of OS to the point where only soft changes are safe. If you were to get any more abrasive than that, you can potentially brick your OS.. That being said, by automated integration, do you mean like a custom .wim file? If so, that would be very counterproductive for the aforementioned reasons. You see, any soft (non-permanent) or hard (permanent) change, mod or customization can lead to 1 of 2 scenarios: 1) a soft change even if in a custom .wim file can be undone by any update or patch by M$. 2) You get too deep in the coding of Windows and run the risk of permanently damaging dependent components of the OS. What I mean is command line. I would like to be able to deploy is with command line arguments. You know, in a command window. As in a bat file. How difficult is this to understand? You have two accounts? Haha. I don't know of any command line tools that will engage the necessary files and functions to achieve the same output as ONE.. There is this registry http://www.tenforums.com/tutorials/6015-pc-folders-add-remove-windows-10-a.html trick that I use in conjunction with ONE on Windows 10 as ONE seems to have trouble keeping the "This PC" folders out of explorer. A few months ago I've scoured the net looking for the same you're looking for but, haven't found anything. ONE & the link I've posted are the only solutions I can find.. I am a different person, I do not know dhjons. But I believe our interests are very similar. Anyway, I have finally found a way (no thanks to you). All that you need to do is register those DLL's which can be done using RegSvr32.exe To register DLL: RegSvr32.exe "PathToDLL\OldNewExplorer64.dll" To unregister DLL:RegSvr32.exe /U "PathToDLL\OldNewExplorer64.dll" I recommend you register both the 64 and 32-bit dll's (or just the 32-bit one if you're running 32-bit OS) and place them in somewhere like %SystemRoot%\System32 and then register them. Now the only thing is to find out is where OldNewExplorer is storing those settings per user. Found it! It stores the settings in the registry: HKEY_CURRENT_USER\Software\Tihiy\OldNewExplorer One could use the UI to customize the settings then export the key. To use in custom WIM, simply mount the DEFAULT user key and make changes to it. Any new user will inherit those settings.
  2. To help prevent irreversible damage, this program is designed to be non-invasive. This program is solely reliant upon itself in terms of functionality hence why you can't rename, move nor delete the file while in use.. A similar effect can be done using other means but, this program isn't designed to be deployed in such a fashion. Especially with Windows 10, M$ has interwoven so many aspects of OS to the point where only soft changes are safe. If you were to get any more abrasive than that, you can potentially brick your OS.. That being said, by automated integration, do you mean like a custom .wim file? If so, that would be very counterproductive for the aforementioned reasons. You see, any soft (non-permanent) or hard (permanent) change, mod or customization can lead to 1 of 2 scenarios: 1) a soft change even if in a custom .wim file can be undone by any update or patch by M$. 2) You get too deep in the coding of Windows and run the risk of permanently damaging dependent components of the OS. What I mean is command line. I would like to be able to deploy is with command line arguments. You know, in a command window. As in a bat file. How difficult is this to understand? You have two accounts? Haha. I don't know of any command line tools that will engage the necessary files and functions to achieve the same output as ONE.. There is this registry http://www.tenforums.com/tutorials/6015-pc-folders-add-remove-windows-10-a.html trick that I use in conjunction with ONE on Windows 10 as ONE seems to have trouble keeping the "This PC" folders out of explorer. A few months ago I've scoured the net looking for the same you're looking for but, haven't found anything. ONE & the link I've posted are the only solutions I can find.. I am a different person, I do not know dhjons. But I believe our interests are very similar. Anyway, I have finally found a way (no thanks to you). All that you need to do is register those DLL's which can be done using RegSvr32.exe To register DLL: RegSvr32.exe "PathToDLL\OldNewExplorer64.dll" To unregister DLL:RegSvr32.exe /U "PathToDLL\OldNewExplorer64.dll" I recommend you register both the 64 and 32-bit dll's (or just the 32-bit one if you're running 32-bit OS) and place them in somewhere like %SystemRoot%\System32 and then register them. Now the only thing is to find out is where OldNewExplorer is storing those settings per user.
  3. Hi, does anyone know how to automate the integration of this useful tweak? Command line arguments perhaps or maybe a way to manually register the DLL's? Also, where does it store the settings for each user?
×
×
  • Create New...