justintime

Tom, This is an OEM DELL disc, Windows 7 Professional SP1. I have done it both ways, but this last time I did it using the PORTABLE version. I just had another go at it (reformatted everything and reinstalled). This time I ONLY selected the "replace shell" option and nothing else and it worked. I then added a few other optionsand it failed with the "background image access error" of before. Maybe this will help you track it down, I think it's a minor thing honestly since the app seems to work except when accessing the desktop images? -J

So thinking, maybe this was a problem with my windows installation, I went ahead, reformatted my hard drive, reinstalled from the original Windows disk from scratch, and it failed again, the exact same way from a fresh windows copy. I have an admin account without passwords or anything. Couldn't be a more simpler setup so I don't think the issue is with my Windows install or set up. Any ideas? Instant Sheller is a most critical aspect of my make cabinet setup! thanks!

I think my problem is due to access rights. Not sure why as I am using an administrative account with full rights. I believe I triple checked that correctly. I even ran the instant sheller app by right clicking and using the "run as administrator" option at the time. Also, this is a Dell oem windows install. But I don't think that is an issue. It's not light or anything. Win7 pro 64 bit.

I'm sorry but I am not sure what you mean by "if I skipped through the exceptions" the first time. I appreciate you trying to help here. I know I'm on my own as this is a risky kind of app to be messing with, but still thanks for your help! I never had an issue in the 16 years using it under XP!

Thanks Tom. I needed 64 bit for various reasons. And required a hardware upgrade. Before I reboot, can you tell me where in registry to look to ensure at least explorer.exe will be my shell? I looked where I thought it would be (winlogon) but I found no registry entry for "shell". Heck, now I'm thinking that since the undo process fails perhaps after reboot I'm with no cursor or who knows what else. Hopefully a restore point was saved by windows. Fun times! Edit: file is there and I have full rights. Weird.

Hi Tom, Im very experienced with Instant Sheller, in Windows XP. Today Ive been setting up a new MAME cab PC based on WIndows 7, and whilst logged in with an administrative account I tried applying the Instant Sheller (using latest version downloaded today 2/8/2023) and it gave me an error as soon as it tried to (apparently) access the desktop background jpg file. I hit continue etc but it seemed to have failed. SO now it shows UNDO but when I click it it gives me a long error again too, which Im attaching here. Every time I open the app it shows UNDO button but it will not work. Im terrified (LOL) of rebooting at this point because who know what will happen Any help appreciated please! ERROR FOLLOWS: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.UnauthorizedAccessException: Access to the path 'C:\Windows\system32\oobe\info\backgrounds\backgrounddefault.jpg' is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) at System.IO.File.Copy(String sourceFileName, String destFileName, Boolean overwrite) at f.a() at f.h(Object A_0, EventArgs A_1) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8806 (QFE.050727-8800) CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll ---------------------------------------- InstantSheller Assembly Version: 1.0.8337.12295 Win32 Version: 1.0.8337.12295 CodeBase: file:///C:/Program%20Files%20(x86)/instantsheller/InstantSheller.exe ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8653 (QFE.050727-8600) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8806 (QFE.050727-8800) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8681 (QFE.050727-8600) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- Microsoft.VisualBasic Assembly Version: 8.0.0.0 Win32 Version: 8.0.50727.7057 (QFE.050727-7000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System.Management Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.8766 (QFE.050727-8700) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.