Monday, December 11, 2017

Create a Windows file that starts with dot

To create a file that starts with a "." in Windows, you just need to add a trailing ".". Name your file ".htaccess."

Wednesday, August 23, 2017

The Programmer's Basic crop image with border instructions - Paint.net

I needed to crop and image and make it looks a little better than the raw image. So I added a border using this instructions:
https://forums.getpaint.net/topic/31582-how-to-crop-an-image-to-be-rounded-corner/
1. Import your picture into PDN, which will be on its own layer.
2. Make a new Layer and, using the Shapes Tool, draw a line where you want to crop it.
3. With the magic wand, select inside the rounded rectangle, go to your picture layer, use Ctrl and I on your computer (to invert the selection) and then hit delete on your computer.
4. Save pdn and then save and flatten image.

Thursday, July 13, 2017

Visual Studio 2013 Web Install Block Compatibility Mode

If you receive an error when installing Visual Studio 2013 (or possibly any version), you may come across several solutions. One says to right-click and select the Compatibility, the others may say to rename the exe file to the original file name and another may say to change some settings on the ISO files to be 'compatible'.
You may do all these things and it still does not want to install. Ever.
Here are the steps you can try that worked for me on Windows 10. Not sure which one finally triggered it to work because after doing 100 things to get it to install you never know.
1. I had previously installed VS2015 before 2013, this may have triggered the problem. I uninstalled VS2015 and then I found a post that recommended clear my %temp% folders. So that is what I did and I did notice there were some 2015 files in there.
open temp folder -> clicking on start and type: %temp% delete files in temp folder
2. Rename the file to the original file name, right click the executable file, go to to the Details tab, see "Original File Name". Rename it to this.
3. I was running the exe from the D: and E: drive this could have been an issue as well, so I copied the exe to the C: drive and ran the exe as Admin. INSTALL RUNNING :)

...UPDATE: I continued to have trouble on a laptop I had purchased. Same problem. But after trying all the same steps, I could not get the install running. I decided to take a break for a few weeks, when I returned to it and used the previous steps, it got past the error. I did a system cleanup, deleted the temp folder again, renamed the file and ran as Admin and that seemed to work.

Tuesday, May 2, 2017

Microsoft office encountered an error during setup. {Where there's a will there's a way}

Microsoft office encountered an error during setup. [yuck, just yuck].
I purchased a new ASUS desktop (Windows 10 Home) with a primary SSD drive and secondary regular hard-drive. I ran the Office 2013 Professional Plus install and it said it 'Microsoft office encountered an error during setup.'.
I spent multiple days, and many hours, trying many solutions. I contacted MS Support they remoted into my PC and did everything I had done and could not install this as well. They suggested I go with higher up support but I wanted to quit wasting my time.
I don't actually know what combination of actions resulted in it finally installing. But if any of these steps helps someone else, I feel I am a better citizen in life. The Task Scheduler deletion of the Office folder was the final step before the install finally worked. I executed the following steps over many days.
1. Ran the MS Office fix that completely un-installs all versions to the MS Office. The PC came installed with 2016, but I had to use 2013. I ran this uninstall many times after trying many fixes.
2. I found a problem with the install complaining about the OSE not being able to run as a standalone [stated somewhere in the install log file found in %temp%]. A post had mentioned copying the OSE.exe file either from the install disk or from another working PC. I copied it from my working PC, but I am pretty sure it was the same version and the one in the install files.
Copied the file to: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
I also copied the regedit entry from my working PC to the new PC and installed the regedit entry so that it would run as a service.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ose]
"DisplayName"="Office Source Engine"
"Description"="Saves installation files used for updates and repairs and is required for the downloading of Setup updates and Watson error reports."
"Type"=dword:00000010
"Start"=dword:00000003
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):22,00,43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,\ 6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,20,00,28,00,78,00,38,00,36,00,29,\ 00,5c,00,43,00,6f,00,6d,00,6d,00,6f,00,6e,00,20,00,46,00,69,00,6c,00,65,00,\ 73,00,5c,00,4d,00,69,00,63,00,72,00,6f,00,73,00,6f,00,66,00,74,00,20,00,53,\ 00,68,00,61,00,72,00,65,00,64,00,5c,00,53,00,6f,00,75,00,72,00,63,00,65,00,\ 20,00,45,00,6e,00,67,00,69,00,6e,00,65,00,5c,00,4f,00,53,00,45,00,2e,00,45,\ 00,58,00,45,00,22,00,00,00
"ObjectName"="LocalSystem"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ose\Security]
"Security"=hex:01,00,14,80,8c,00,00,00,98,00,00,00,14,00,00,00,30,00,00,00,02,\ 00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\ 00,00,02,00,5c,00,04,00,00,00,00,00,14,00,9d,01,00,00,01,01,00,00,00,00,00,\ 05,04,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,\ 00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,00,\ 00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,06,00,00,00,01,01,00,00,00,00,\ 00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00
I restarted the computer, saw the Office Source Engine was an installed service, and started the service so it would be running when I ran the install.
I am not sure if this was necessary or not. But throwing it out there because it worked for someone else...In the end, after the sucessful install of the 64-bit Office, I see I have an 'Office 64 Source Engine' service installed so I am guessing the install tries to install this whole Source Engine itself.
3. Copied the ISO files from the mounted image to a regular folder on the D drive. [I had originally copied the files from the 32-bit ISO that was provided to me by my client but eventually used the ISO that I downloaded myself from the Microsoft site and that was the copy that finally worked which was the 64-bit version]
4. Unregistered and re-registered the Windows installer. Start run msiexec /unregister and then msiexec /regserver
5. Go to c:/windows/tasks and delete the contents of the folder, if you have a lot of tasks then take a backup first.
6. [THIS IS THE LAST STEP THAT I DID JUST BEFORE SUCCESSFULLY INSTALLED] Open up the Task Scheduler, go to Microsoft Folder, Delete the Office folder. https://community.spiceworks.com/topic/1872788-office-2013-install-error-on-windows-10-anniversary-update
7. Restarted the PC in a Clean Boot.
8. Ran the install again.
I truly feel like I deserve a trophy or something. I seriously spent over 16 hours working on this problem.
UPDATE: I had to un-install the 64-bit due to needing the 32-bit for Access. I was worried about un-installing and re-installing due to all the issues I encountered. I ran the FixIt that deleted the previous install, deleted the Task Scheduler - Office folder, restarted (not even a clean boot), and then re-installed. And it ran in minutes.
I did not do anything with the Office Source Engine, no clean boot, nothing. So there you go.