vim (gVim 8.0+ on Windows) configuration notes and settings

1. In Windows, drag and drop OLE (:drop) functionality will be disabled if the program is launched as an Administrator. So remember to NOT set launch as administrator in the app's properties dialog box so drag and drop will continue to work. This also allows the right click context menu to work for 'edit with vim' and 'edit with vim (existing)' commands to open files properly. Windows won't allow drag and dropped files to escalated programs or at least it didn't work with vim.

2. As a side effect of #1, not launching as admin, means the program might not have write rights to the vimrc config file (c:\Program Files (x86)\Vim\_vimrc) so even doing :w! didn't work. E212 Can't open file for writing was the error.

Also,
cmap w!! w !sudo tee % >/dev/nul
didn't work. What DID work was going to the _vimrc file in Windows file properties security dialog and change the file permissions to allow users full access.

3. colorscheme (filename without .vim) only read from c:\Program File (x86)\Vim\Vimfiles\colors and not the default %HOME%\vimfiles\colors folder. Solution: copy the filename.vim to the program files folder.

4. Airline not showing patched font properly. Out of the prepatched fonts available the OTF fonts didn't seem to work. One font that did work that I like is Inconsolata-g.

set guifont=Inconsolata-g_for_Powerline:h11

with
set guioptions-=e "guitabs off

and

let g:airline#extensions#tabline#enabled = 1

let g:airline_powerline_fonts = 1

turned on it worked fine. I had to make sure the following WASN'T set as this killed the special symbols.

"if !exists('g:airline_symbols')

"  let g:airline_symbols = {}

"endif

" unicode symbols

"let g:airline_left_sep = '»'

"let g:airline_left_sep = '▶'

"let g:airline_right_sep = '«'

"let g:airline_right_sep = '◀'

"let g:airline_symbols.linenr = '␊'

"let g:airline_symbols.linenr = '␤'

"let g:airline_symbols.linenr = '¶'

"let g:airline_symbols.branch = '⎇'

"let g:airline_symbols.paste = 'ρ'

"let g:airline_symbols.paste = 'Þ'

"let g:airline_symbols.paste = '∥'

"let g:airline_symbols.whitespace = 'Ξ'

and to have it show properly with airline updating the status line and tab line upon starting gvim:

autocmd VimEnter * silent AirlineRefresh | wincmd p | wincmd p

That seemed to fix it to get working right at startup.

Disable UAC prompts on Windows 10 and still have metro apps working

Not from me but from http://www.tenforums.com/software-apps/12065-cant-open-any-windows-app-uac-disabled-2.html#post557465

04 Feb 2016 #11
Greg R

This fix worked for me

Hello,
I disabled UAC and when I try to open Edge, Calculator, etc I get a window message that says that I cant open it with UAC disabled, I find it something very annoying that makes me think about going back to Windows 7, is there any around this?
In Windows 7 for example, I was able to open the calculator with UAC disabled.
Thanks!
I have a fix that will allow you to still keep UAC enabled, provide no prompting for a user, while still being able to run all Metro apps - calculator, Edge, weather, news, calendar, etc
Either through Group Policy or Local Security Policy
Computer Configuration\Policies\Windows Settings\SecuritySettings\Local Policies\Security Options
User Account Control: Admin Approval Mode for the Built-in Administrator account = Enabled

User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode = Prompt for Credentials
Next, make some registry changes ....
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Make the following changes
ConsentPromptBehaviorAdmin 0x00000003 becomes 0x00000000

ConsentPromptBehaviorUser 0x00000003 becomes 0x00000000

EnableLUA 0x00000001 stays at 0x00000001
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\UIPI
Change (Default) from the (value not set) to 0x00000001(1)
Reboot your Windows 10 machine and enjoy all the metro apps that require UAC/escalation without the nags

 Remember to reboot first!

Seatools for Windows 1.2.0.5 and DOS 2.20, 2.23 and Nvidia's older nForce 4 (ultra amd) chipset SMART error with Nvidia SW IDE driver

I purchased a new Seagate 1TB 3.5" SATA hard drive and wanted to ensure it was good before using it as my main new hard drive in my most used computer.

Problem:

Seatools in Windows reports SMART error and my chipset is nForce 4 ultra AMD using Nvidia's IDE driver. The IDE driver is the problem for the SMART fail in Seatools for Windows and poor coding is the reason for Seatools in DOS (and Seagate's software not understanding the Nvidia IDE driver's response to the SMART test in the Windows version).

Solution:

For the SMART error appearing in Seatools under Windows: remove Nvidia's IDE driver. (Start, Control Panel, Nvidia Drivers, Check Remove only Nvidia IDE). For the DOS crashing of Seatools: use the older text based (non-crashing version) of Seatools to run a test on the drive. Version 1.09PH worked for me no problems.

Long story:

So I started Seatools for DOS 2.20 and did long tests and Seatools would crash, meaning the long test after several hours running would not report a pass or fail and the majority of the graphical interface was still visible behind the text based interface which was in the upper left corner of my screen. The graphical interface crashed and did not reset the resolution or text mode back so that the text screen would show, the one where it tells you about viewing the log or saving to floppy. If I tried to view the log it would give an error message about it being an invalid display mode. I could copy the log to a floppy drive however and view that log which only stated that the long test had started and gave no result or mention of a pass or fail for the test.

So I figured I upgrade to the latest version of Seatools for DOS which at the time of this writing in May 2011 is/was 2.23. Same results except this time for the long test in DOS it would show passed and then it would freeze at the end of the test (couldn't use alt-keys or mouse to exit Seatools). Seatools doesn't like the Nvidia nForce4 chipset it seems.

I should also mention at this point in dos versions of Seatools SMART has not been tripped is mentioned in all versions.

Now in the Windows version of Seatools 1.2.0.5, All tests would pass except SMART (basic test was the only option I had).  This would say:

SMART - FAIL 5/25/2011 6:14:46 AM
SeaTools Test Code: A9E9E24A

I couldn't find information on this test code but did find some forum thread about Segate's failing the SMART test. This is a brand new drive in fact and I do understand how brand new equipment can fail but I just wanted to point that out. Note that every other hard drive SMART monitoring program I tried reported SMART status had not been tripped (as Seatools for DOS correctly reported) and that the drive is in perfect health after running a scan with diagnostic tools other than Seatools.

Here are two such thread I found:
http://forums.seagate.com/t5/SeaTools/drive-status-SMART-FAIL-incorrect/td-p/7944
http://forums.seagate.com/t5/Barracuda-XT-Barracuda-Barracuda/SMART-FAIL-in-SeaTools-Diagnostics-and-Drive-Detect-results/td-p/18901

The latter thread points to the SMART fail as a possible driver issue. Which is what the problem was the Nvidia IDE driver in fact. Removing it and running the Seatools for Windows again did not give a fail. Instead I get:
SMART - Pass 5/26/2011 9:25:19 AM

And for a second and third opinion: I tried HD Sentinel and HDDScan for Windows and the drive is in perfect health and passed all tests including the SMART tests and none of the SMART data on the drive has exceeded any thresholds.

So Seatools for Windows...you just don't like the Nvidia's IDE driver...and Seatools for DOS (graphical version)...your coding just sucks....Seatools for DOS (text-based)....you still work with no issues.

All tests now pass once I removed this conflicting Nvidia IDE driver.

General disclaimers:

If you get a report about a SMART failure it may be a false positive from Seagate's Seatools as above with the driver conflict but you should check it out with other diagnostic tools just to be sure you don't actually have a failure.

And, as always, Have a good, verified backup before running any intensive hard drive tests or what not.

More info:
http://www.google.com/search?hl=en&biw=1390&bih=839&q=+site:forums.seagate.com+smart+fail+seatools