Killing Disconnected Terminal Server Sessions

Terminal Services (or Remote Desktop if you prefer) is a good thing. It allows you to remotely connect to a server to manage it.

However, there is a "special" breed of user out there that can't remember to log off of their sessions, opting to simply click the "X" in the upper right. Too many disconnected sessions (2), and nobody else can connect via RDP. Kill 'em quick with this process.

First, why are you using terminal services to manage your server? You should be using remote administration tools, usually via an MMC interface. All core services (AD, DHCP, DNS, etc), as well as most application services (Exchange, IIS, etc) can be administered with it. Heck, you can even use PowerShell to administer remote servers. So stop using Terminal Services to manage your servers.

Second, if you absolutely must RDP into a server, sign off correctly. Windows servers have a maximum of two RDP sessions and one console session available, unless the server has been licensed for use as a terminal server. Leaving two disconnected RDP sessions on the server effectively blocks anyone else from connecting to the server via RDP.

Normally, to clear the disconnected sessions, one would fire up the terminal services manager MMC (remote management!), connect to the server in question, and log off any disconnected sessions. It doesn't take long to do this, but can be a few minutes if you are working with a server that is on the other side of the country.

So why not try the command prompt? Windows (at least from Win7 onward, as well as server OSs) have a number of utilities built-in to manage Terminal Services remotely. The two we are interested in are:

Query Session
LogOff

The first thing you'll need to do is open a command prompt with credentials that have permissions to administer terminal services on the remote server. If you don't do this, you'll simply get "Access Denied" errors when attempting to administer the remote server.

Once you get the command prompt open, type the following command:
query session /server:
The output of the command will be something similar to the following:

C:\>query session /server:MyTestServer
SESSIONNAME       USERNAME                 ID  STATE   TYPE        DEVICE
services                                    0  Disc
console                                     1  Conn
                  MyTestUser                2  Disc
rdp-tcp                                 65536  Listen

C:\>

Ntoice the session with MyTestUser, and its current state of Disc. This means that the user did not log off the machine, but rather the connection was either disrupted, or the user simply closed the RDP window without logging off.

Just an FYI, the full syntax of the Query Session command is:

query session [{SessionName | UserName | SessionID}] [/server:ServerName] [/mode] [/flow] [/connect] [/counter]

Parameters

*SessionName*	The name of the session you want to query.
*UserName*	The name of the user whose sessions you want to query.
*SessionID*	The ID of the session you want to query.
/server:ServerName	Identifies the terminal server to query. The default is the current server.
/mode	Displays current line settings.
/flow	Displays current flow-control settings.
/connect	Displays current connect settings.
/counter	Displays current counters information, including the total number of sessions created, disconnected, and reconnected.
/?	Displays help at the command prompt.

So, now that you have a list of the sessions, including the disconnected session, you have what you need to kick that "user" off the dead RDP connection. Make note of the ID number of the disconnected session, in this case 2.

Now, at your handy-dandy super-elevated command prompt, type the following:
Logoff 2 /server:MyTestServer
One thing you'll notice immediately is that you'll get no feedback if the command was successful. You'll simply get returned to the command prompt. You can verify the connection was disconnected by running the Query command again. The whole session would look like this:

C:\>logoff 2 /server:MyTestServer

C:\>query session /server:MyTestServer
 SESSIONNAME       USERNAME                 ID  STATE   TYPE        DEVICE
 services                                    0  Disc
 console                                     1  Conn
 rdp-tcp                                 65536  Listen

C:\>

Notices the previously noted dead session, which had an ID of 2, is now missing from the list. Congratulations! You have now cleared out the blocking session.

Questions? Comments? Fire off in the comments below, or even in the forums!

Why would you pay $12.95 per month ?

There are sites out there that charge folks for answers. Yup hard to believe, right? This is incredible to me, since most of the information they provide is free, if you simple use your favorite search engine to find the answer.

What if I were to tell you that there is a not-so-top-secret place where you could find just about any answer you'd want, and any subject, and it's free for you to use, twenty four hours per day, 365 days per year? Oh, did I mention it was free?

The first thing I am going to tell you is to use this site, naturally. As the owner and webmaster, I would be remiss in not pimping my own site. That being said and done, lets move on to some ranting, shall we ?

I am currently an infrastructure architect for a large firm based in Tacoma, WA. As such, we have agreements with software and hardware vendors from which we have purchased products from.

For example, we have a Premier support agreement with Microsoft. What this means, in a nutshell, is that anyone on the team can pick up the phone and call Microsoft Support, at any time, and get support for products that we own. The case will be triaged, given a severity level, etc. I won't go into the details, but suffice to say, we pay for support for products we have purchased, and the vendor (MS) sees those support tickets through to proper resolution.

Did you know that anyone can call and get this type of support MS? Yup, for a per-case fee, you can get the same great treatment as a big enterprise. Depending on the problem, it may not be cost effective, though, so weigh your options carefully.

Any application support or system administration type person worth his salt is going to scour the internet for an answer first. They'll phone a friend, consult hardcopy manuals, etc., before placing that all important call. Basically, any sound information technology worker is going to exhaust the resources available before making the call to tech support.

So you might think, "Hey, what is this guys problem with paying for support?"

The problem as I see it is that certain websites out there (who shall remain nameless), will charge unsuspecting newbies the sum of $12.95 per month for access to information that is available free on the internet. In my eyes, this is preying on the uninformed. It's like having a telemarketer call you up and trying to sell you an extended warranty for your vehicle. (yes, I have received this call). Ninety percent of the time, it's a straight out scam (I hadn't even owned the vehicle for 3 years).

How do I know their "experts" are simply regurgitating information that is free? Let's just say that I know how to read the logs of my web server, and I notice that there is a growing number of referrals from this not-to-be-named site. In speaking with a few other webmasters of similar sites, and they have found the similar activity in their logs.

Besides fortypoundhead.com, there are literally bushels of sites were hard-working folks are willing help you find the solution to your problem. Lets run some numbers shall we ? I did some looking around, and here is what I found when comparing the not-to-be-named site with one of my favorite answers sites:

Site: not going to name here
Topics: 900+
Questions: unknown
Answers: 3 million
Users: unknown
Cost: $12.95 per month, unless you are an "Expert"
Comments: good site for folks who don't know how to work a search engine.

Site: StackExchange.com
Topics: 101 sub-sites, focused on targeted subjects
Questions: 6 million
Answers: 11+ million
Users: 3+ million
Cost: free
Comments: Heavy tech content, but covers such things as philosophy, gardening, and martial arts as well.

Wow. I had no idea that Stack Exchange was so huge! Hats off to Joel Spolsky and Jeff Atwood! Like me, these two guys are in IT to help people, not make a quick buck by shystering noobs.

This is only one comparison. There are thousands of web sites and tons of documentation out there on the internets, all neatly indexed by your favorite search engine. Most browsers available don't even require you to open a search engine - just type your keyword-laden question into the address bar, and whoosh! answers galore.

Heck, while fortypoundhead.com is no competitor to some other sites out there, we have available 6,068 tech articles and tutorials available, a Q&A section, and even forums on the way. Can't find it here? Ask for it.

So why pay for support when you don't need to? Why are you lining the pockets of someone who is just going to give you information that is free to begin with? Sounds fishy to me.

Disagree? Got something to say? Let me know in the (also free) comments section below.

Living with the Surface

About one month ago, I became the proud owner of a Microsoft Surface RT. So far, I'm loving it. This seems to be contrary to the thoughts of the majority of folks in IT, but hey, I've always been a bit different.

Having got rid of my iPad some time ago, I've been lugging around my Dell 6410 to meetings and such. The laptop does a great job, and I have no real complaints, but I really missed the portability of a tablet.

At first, I was kind of leery about letting go of the laptop, and lugged around both devices. But after awhile, I found myself leaving the laptop in the dock, and grabbing the surface for meetings, quick document or spreadsheet updates, reading documentation, or even (gasp) playing a quick puzzle-type game. Soon, it became my go-to device, however, and I the laptop now remains on my desk.

For those who have not investigated the Surface RT specifications, here are the details:

1366�768 (16:9 aspect ratio) 10.6? Cleartype display (148 PPI) and built in kickstand
274.6 x 172 x 9.4 mm (10.81 x 6.77 x 0.37 in); 680.4 g (1.50 lb)
Windows RT including Microsoft Office home and student 2013.
Nvidia Tegra 3 quad core processor clocked at 1.3Ghz
32 or 64GB memory with expandable SD card storage up to 64gb
Dual Stereo speakers, 720P front and rear facing cameras, dual Mics and dual band WiFi.
Full size USB 2.0 and a micro HDMI out.
Magnetic dock for one of Microsoft�s touch & type keyboard covers and MagSafe style proprietary charger.
Starting Price; $499 without the touch cover (32gb), $599 with the touch cover. $699 with touch cover (64gb)

My particular unit is the 64 GB model, with the touch cover. If you want to store anything on your Surface, you'll want to get the 64 GB model. Storage space on the 32 GB version is taken up mostly by Windows RT itself, along with any apps that are installed, so you'll be relying heavily on SkyDrive for document storage. This could be a bit of a detriment, in my opinion. There are going to be times you want to get something done, and don't have internet access. Without local storage, you won't be able to crack open that Word document or Excel spreadsheet that lives on SkyDrive.

That's not to say there isn't storage available on the 32 GB Surface, just not as much. And we all know that more is better right? Microsoft did give you an option, though. On either model, you do have the option of plugging in an SD card, up to 64 GB, to augment the local storage.

The hardware itself is pretty solid. While some will quibble over the 28 grams of extra weight that the Surface packs over the iPad, it's not really noticeable. If you are noticing 28 grams (or .04 pounds), you need to get out more often. Or get a job as an accurate postal scale.

Connectors abound, and this is one of the things the drove me away from the iPad. There is a full size USB port, a micro HDMI port, SD card slot, and a headphone jack to augment the on-board stereo speakers, even glorious Bluetooth connectivity. Have you tried to plug in an USB drive or upgrade the storage on an iPad? Give it a try, but be sure to find the appropriate proprietary cable for that jump drive first.

Speaking of connectors, the HDMI output of the Surface appears to have a minimum resolution limitation of 1366x768, which means if you hook up your surface to a 720p television, the signal will usually not be recognized by the TV. To get your Surface to output to the TV, the TV needs to be 1080p. Microsoft says this was done to protect the integrity of the Windows 8 interface. This is a real bummer for me. Most of my TVs are 1080p, with the exception of one, which happens to be the one that I like to watch movies on. Guess it's time to upgrade the bedroom TV!

The Surface comes with Office 2013 Student Edition, which includes Word, Excel, PowerPoint and OneNote. With the exception of PowerPoint, I have been using the suite quite a bit. Each application runs in the desktop space, and each is touch friendly. One thing I would recommend is to get the type keyboard with your purchase. The touch keyboard is usable, but takes about 3 days of use to get used to it, and until then you'll be making quite a few corrections.

OneNote is spectacular, in my humble opinion. It integrates nicely with my two desktops (work and home), as well as my Windows phone, via a connection to SkyDrive. This means I can take notes or even sketch with my finger or a stylus, within OneNote, and by the time I get back to my desk, the information is already there.

Yes, the app store is a bit thin on offerings as of now. However, I've not had a problem locating apps that I need. I'm not talking about fluff apps such as random number generators, but useful apps. More applications are being released daily, and I'm sure you won't have a problem finding what you need.

In summary, I think the Microsoft Surface is a good alternative to an iPad or an Android tablet. I've owned all three now, and I find the integration between the Surface and my other Windows devices is superb. I don't have to buy an application to view PowerPoint presentations, and all manner of data is easily synchronized between all my Windows machines.

Three Windows Command Prompt Replacements

I've been using the trusty command prompt in Windows, well, forever. Having started my life in IT as a DOS keyboard jockey, it's been a part of my life that just won't go away.

Lateley though, I've been looking to teach my command prompt some new tricks. Things like multi-tab interface, easier copy/paste within the window, things of that nature. Here, I've tested three command prompt enhancments.

Now, to be fair, there are a metric ton of replacements and enhancemants for the tired, old Windows command prompt. Some are full on shell replacements, while others are simply wrappers over the existing command prompt. In either case, new features are added.

Some of the features I look for in a replacement are:

Multi-tabbed interface
Ability to plug in multiple shells, such as CygWin or PowerShell
Confifigurability, such as colors, fonts, etc.
Windows-like line and block copy operations

Nice to have would be some sort of IDE-like interface, with features such as command completion, command history, path history, etc. Not necessary, but welcome additions. I don't go in much for feature bloat, or having switches for the sake of having switches. I like my environment clean and simple.

Of all the packages I looked at, I narrowed it down to three contenders: Console, PromptPal, and PowerCMD.

All three of these provide for each of the my requirements, with PowerCMD and PromptPal pulling out all the stops for feature sets. There are tons of features in each that I will most likely not use. Further, each of them performed pretty much equally as far as configurability and functionality.

If you're a feature hound, you'll love PromptPal. The high level of configurability will have you poking and prodding for hours. But once you get all the options set just so, you'll shouldn't have to touch them again. All three of the replacements had good configuration options, but PromptPal took it to a new level. BUT, one thing that bothered me was the application error that kept presenting itself whenever the app was closed. Boooo!

PowerCMD was a close second for configuration options. Similar flexibility is there, but takes some snooping around to find the options.

And then there is Console. It's not as configurable as the other two, but rather keeps things simple and clean. There are the basic things you'd expect, and a few other items as well. There is not even an installation program for this wrapper-type enhancement. Simply park it in a directory, add it to your path, and make a shortcut to it. If you don't know how to do those things, you don't need a shell enhancement anyway, right?

So, how to decide which of these to use. They all function pretty much the same, and all have the features I am looking for. Hmmmm... a test!

I decided to throw a seemingly simple test at each of these packages, a directory listing. Not just any directory listing, though. A recursive directory listing of my "backups" folder, containing 984,731 files in 164,789 directories. Yes, I save everything. The pertinent specs for the test system are:

Pentium dual-core CPU E5300 @ 2.6 ghz
8 GB RAM
System Drive: 10k RPM 500 GB
Data drive: 7200 RPM 1 TB
OS: Windows 8 Professional x64

A simple batch file was built to take note of the time when the directory listing started, perform the listing, then make another note of the time at the end:

echo Start Time:%time% > timing.txt
dir *.* /s /a
echo End Time:%time% >> timing.txt

Pretty straightforward, eh?

Just to make sure all was equal, I turned of all disk buffering, as well as disabling power-saving features of the data drive (where the search will take place). Further, each app will run the listing in a window of the same size, just so nobody can claim an advantage or disadvantage due to screen handling.

First things first, though. We need a baseline, gathered from the app being replaced, the Windows command prompt.

Running the listing in the default Windows command prompt (CMD.EXE) seemed to run pretty briskly, but in reality it completed the task the slowest, with a run time 26 minutes, 23 seconds.

I've build a synopsis of each package below, with the timings for each one.

Note: PowerCMD does not have a time, since it never completed the test! I tried running the same test three times, and each time it hung between 30-35% completion of the listing. It appears to be doing something (according task manager), but nothing ever presents on-screen, and the program itself goes into "not responding" mode.

Console

Of the three, Console is the simplest. It includes all the basic options such as multi-tabbed interface, multiple shells, and basic configuration options. Clean and easy to use, this shell wrapper gets the job done with no-nonsense.

Cost: $0.00 (open source)
Test Runtime: 1 minute, 50 seconds

Pros:

Free
Simple to Configure
tabbed interface
session saving
Plug in any shell, eh: CygWin, PowerShell, Visual Studio, etc.

Cons:

Choppy performance
No install package, must be manually installed.

PowerCMD

Lots of options here, but can be a bit confusing to the user, if they're not into twiddling tons of settings. PowerCMD seemed a bit dodgy when working with large datasets, as evidenced by its inability to complete the directory listing test.

Cost: $30.00 (free trial available)
Test Runtime: N/A - could not complete

Pros:

Searchable windows
tabbed interface
log-to-file functionality
auto-completion
Windows Explorer Integration
Session saving

Cons:

initial interface kind of cluttered
*very* sluggish performance when window contents go over ~10000 lines

PromptPal

PrompPal is a great package. Screen updates can be a bit sluggish if you've been working in it for a couple hours, though. This was evidenced in the directory listing test as well. One of the other niggling things that bothered me was the choice of font for the first run. For users who utlize high resolution screens, the choice of 8 point Courier makes the user have go in to the configuration, in order to simply see the text within the console.

This app also suffered from the presentation of an Application Error when closing, every time. Yikes! We don't need no steenkin' errors!

Cost: $29.99 (free trial available)
Test Runtime: 2 minutes, 17 seconds

Pros:

Highly configurable
Command Completion
Windows version of *nix TAIL command thrown in
Windows Explorer Integration
Command and path history

Cons:

*very* sluggish performance when window contents go over ~33000 - 35000 lines
Seems a bit unstable;Application Error presents when closing the app
Command history/auto-complete gets in the way sometimes

After checking out these three packages, I am kind of leaning towards Console, for a couple reasons.

Open source - can be a good thing (free!), but can be a bad thing (no real support other than community based)
Stability - consistent update of display during long operations, and no errors presented
Simplicity - Has the options that I am looking for, without a pile of options I will never use

Note that the conclusions I've reached above are based on a short amount of time working with the applications, approximately 8 hours each. I'll continue working with all three of these apps over the next 20 or so days, and will post an update below, with any new findings.

Have you replaced your shell? What do you use? What do you look for in a replacement?

Your Favorite Documentation Tool?

In my current position, it is necessary to write large amounts of technical documentation. For this, I use a variety of tools to create a "master" document, which then gets uploaded to either a SharePoint repository, or to our Wiki.

To build these documents, I use things like Word, Notepad++, OneNote, Photoshop, CamStudio, and maybe a few others, but those are the highlights. I've been playing with a new idea, and am hoping to get some input from the community about their favorite tools, what they like, and what they don't like. Let your voice be heard!

What do you look for in a documentation tool?

Favorite tool or feature? Least Favorite tool or feature?

ShellFileCopy with VB6

Copying a file with VB6 is pretty straightforward. However, giving feedback to the user during the copy process has historically been a challenge.

By leveraging the Windows API, we can utilize the same functions that Windows itself uses to copy files, and at the same time make use of the built in copy status dialog. Another VB6 post, by request.

Success or failure of the copy process will be returned as well, with a true/false value.

Example:

dim bSuccess as boolean
bSuccess = ShellFileCopy ("C:\MyFile.txt", "D:\MyFile.txt")

Option Explicit

Private Type SHFILEOPSTRUCT
        hwnd As Long
        wFunc As Long
        pFrom As String
        pTo As String
        fFlags As Integer
        fAnyOperationsAborted As Long
        hNameMappings As Long
        lpszProgressTitle As String
End Type

Private Declare Function SHFileOperation Lib "shell32.dll" _
Alias "SHFileOperationA" (lpFileOp As SHFILEOPSTRUCT) As Long

Private Const FOF_ALLOWUNDO = &H40
Private Const FOF_NOCONFIRMATION = &H10
Private Const FO_COPY = &H2

Public Function ShellFileCopy(src As String, dest As String, _
    Optional NoConfirm As Boolean = False) As Boolean

Dim WinType_SFO As SHFILEOPSTRUCT
Dim lRet As Long
Dim lflags As Long

lflags = FOF_ALLOWUNDO
If NoConfirm Then lflags = lflags & FOF_NOCONFIRMATION
With WinType_SFO
    .wFunc = FO_COPY
    .pFrom = src
    .pTo = dest
    .fFlags = lflags
End With

lRet = SHFileOperation(WinType_SFO)
ShellFileCopy = (lRet = 0)

End Function

Compare Two Files in VB6

This function will allow you to compare one file to another. It will do either a lax check (compare file lengths only) or a stringent check (a byte by byte comparison).

Pretty straightforward demonstration of string handling for Visual Basic 6, posted by request.

Public Function AreTheyTheSame(ByVal File1 As String, _
  ByVal File2 As String, Optional StringentCheck As _
  Boolean = False) As Boolean

On Error GoTo ErrorHandler

If Dir(File1) = "" Then Exit Function
If Dir(File2) = "" Then Exit Function

Dim lLen1 As Long, lLen2 As Long
Dim iFileNum1 As Integer
Dim iFileNum2 As Integer
Dim bytArr1() As Byte, bytArr2() As Byte
Dim lCtr As Long, lStart As Long
Dim bAns As Boolean

lLen1 = FileLen(File1)
lLen2 = FileLen(File2)
If lLen1 <> lLen2 Then
    Exit Function
ElseIf StringentCheck = False Then
        AreTheyTheSame = True
        Exit Function
Else
    iFileNum1 = FreeFile
    Open File1 For Binary Access Read As #iFileNum1
    iFileNum2 = FreeFile
    Open File2 For Binary Access Read As #iFileNum2

    'put contents of both into byte Array
    bytArr1() = InputB(LOF(iFileNum1), #iFileNum1)
    bytArr2() = InputB(LOF(iFileNum2), #iFileNum2)
    lLen1 = UBound(bytArr1)
    lStart = LBound(bytArr1)
    
    bAns = True
    For lCtr = lStart To lLen1
        If bytArr1(lCtr) <> bytArr2(lCtr) Then
            bAns = False
            Exit For
        End If
            
    Next
    AreTheyTheSame = bAns
       
End If
 
ErrorHandler:
If iFileNum1 > 0 Then Close #iFileNum1
If iFileNum2 > 0 Then Close #iFileNum2
End Function

Get Available Drivespace with VB6

As a developer, from time to time you are called upon to build or process large chunks of data. During this process, you can use the the local hard drive as a temporary holding area. Admittedly, with todays well-specc'd computers, you shouldn't need to do this, but back in the day, this was the norm.

By request, here is a set of API functions for use with Visual Basic 6 that will return various pieces of information about local storage, such as total space, free space, etc.

I've tried to take line wrap in to account, but watch out! I may have missed one.

Option Explicit

Private Declare Function LoadLibrary Lib "kernel32" Alias "LoadLibraryA" _
                            (ByVal lpLibFileName As String) As Long

Private Declare Function FreeLibrary Lib "kernel32" _
                            (ByVal hLibModule As Long) As Long

Private Declare Function GetProcAddress Lib "kernel32" _
                            (ByVal hModule As Long, ByVal lpProcName As String) As Long

Private Declare Function GetDiskFreeSpace Lib "kernel32" Alias "GetDiskFreeSpaceA" _
                            (ByVal lpRootPathName As String, _
                            lpSectorsPerCluster As Long, _
                            lpBytesPerSector As Long, _
                            lpNumberOfFreeClusters As Long, _
                            lpTtoalNumberOfClusters As Long) As Long 'C Bool

Private Declare Function GetDiskFreeSpaceExAsCurrency Lib "kernel32" Alias "GetDiskFreeSpaceExA" _
                            (ByVal lpDirectoryName As String, _
                             lpFreeBytesAvailableToCaller As Currency, _
                             lpTotalNumberOfBytes As Currency, _
                             lpTotalNumberOfFreeBytes As Currency) As Long 'C Bool

Private Declare Sub CopyMemory Lib "kernel32" Alias "RtlMoveMemory" _
                                                    (lpvDest As Any, _
                                                    lpvSource As Any, _
                                                    ByVal cbCopy As Long)

Public Function vbGetAvailableBytesAsString(Optional ByVal sPath As String = "") As String
    Dim lo As Long, hi As Long
    Dim sOut As String
    
    If ExistGetDiskFreeSpaceEx() Then
        sOut = vbGetAvailableBytesEx(sPath)

    Else
        sOut = CStr(vbGetAvailableBytes(sPath))
    End If
    vbGetAvailableBytesAsString = sOut
    
End Function

Public Function vbGetAvailableKBytesAsString(Optional ByVal sPath As String = "") As String
    Dim bytes As Currency, kBytes As Currency
    Dim sTmp As String
    
    sTmp = vbGetAvailableBytesAsString(sPath)
    bytes = CCur(sTmp)
    If bytes Then 'avoid divide by 0 errors
        kBytes = bytes / 1024
        kBytes = Fix(kBytes)
    Else
        kBytes = 0
    End If
    vbGetAvailableKBytesAsString = CStr(kBytes)
        
End Function

Public Function vbGetAvailableMBytesAsString(Optional ByVal sPath As String = "") As String
    Dim kBytes As Currency, mBytes As Currency
    Dim sTmp As String
    
    sTmp = vbGetAvailableKBytesAsString(sPath)
    kBytes = CCur(sTmp)
    If kBytes Then 'avoid divide by 0 errors
        mBytes = kBytes / 1024
        mBytes = Fix(mBytes)
    Else
        mBytes = 0
    End If
    vbGetAvailableMBytesAsString = CStr(mBytes)
        
End Function

Public Function vbGetTotalBytesAsString(Optional ByVal sPath As String = "") As String
    Dim lo As Long, hi As Long
    Dim sOut As String
    
    If ExistGetDiskFreeSpaceEx() Then
        sOut = vbGetTotalBytesEx(sPath)
    Else
        sOut = CStr(vbGetTotalBytes(sPath))
    End If
    vbGetTotalBytesAsString = sOut
    
End Function

Public Function vbGetTotalKBytesAsString(Optional ByVal sPath As String = "") As String
    Dim numbytes As Currency, kBytes As Currency
    Dim sTmp As String
    
    sTmp = vbGetTotalBytesAsString(sPath)
    numbytes = CCur(sTmp)
    If numbytes Then 'avoid divide by 0 errors
        kBytes = numbytes / 1024
        kBytes = Fix(kBytes)
    Else
        kBytes = 0
    End If
    vbGetTotalKBytesAsString = CStr(kBytes)
        
End Function

Public Function vbGetTotalMBytesAsString(Optional ByVal sPath As String = "") As String
    Dim kBytes As Currency, mBytes As Currency
    Dim sTmp As String
    
    sTmp = vbGetTotalKBytesAsString(sPath)
    kBytes = CCur(sTmp)
    If kBytes Then 'avoid divide by 0 errors
        mBytes = kBytes / 1024
        mBytes = Fix(mBytes)
    Else
        mBytes = 0
    End If
    vbGetTotalMBytesAsString = CStr(mBytes)
        
End Function

Public Function ExistGetDiskFreeSpaceEx() As Boolean
    Dim hInst As Long
    Dim procAddress As Long
    
    hInst = LoadLibrary("kernel32.dll")
    If hInst Then
        procAddress = GetProcAddress(hInst, "GetDiskFreeSpaceExA")
        Call FreeLibrary(hInst)
    End If
    ExistGetDiskFreeSpaceEx = CBool(procAddress)
    
End Function

Private Function vbGetAvailableBytesEx(ByVal sPath As String) As String
    Dim BytesAvailable As Currency
    Dim TotalBytes As Currency
    Dim TotalFreeBytes As Currency
    Dim tmp As Currency

    On Error GoTo APIfailed
    If "" = sPath Then
        Call GetDiskFreeSpaceExAsCurrency(vbNullString, BytesAvailable, TotalBytes, TotalFreeBytes)
    Else
        Call GetDiskFreeSpaceExAsCurrency(sPath, BytesAvailable, TotalBytes, TotalFreeBytes)
    End If

    'If BytesAvailable Then
        BytesAvailable = BytesAvailable * 10000
        vbGetAvailableBytesEx = CStr(BytesAvailable)
    'End If
    Exit Function
APIfailed:
    'returns false
    Debug.Print "GetDiskFreeSpaceEx() API Failed!"
End Function

Private Function vbGetTotalBytesEx(ByVal sPath As String) As String
    Dim BytesAvailable As Currency
    Dim TotalBytes As Currency
    Dim TotalFreeBytes As Currency
    
    On Error GoTo APIfailed
    If "" = sPath Then
        Call GetDiskFreeSpaceExAsCurrency(vbNullString, BytesAvailable, TotalBytes, TotalFreeBytes)
    Else
        Call GetDiskFreeSpaceExAsCurrency(sPath, BytesAvailable, TotalBytes, TotalFreeBytes)
    End If
    
    If TotalBytes Then
        TotalBytes = TotalBytes * 10000
    Else
        TotalBytes = 0
    End If
    vbGetTotalBytesEx = CStr(TotalBytes)
    Exit Function
APIfailed:
    'returns false
    Debug.Print "GetDiskFreeSpaceEx() API Failed!"
End Function

Private Function vbGetAvailableBytes(ByVal sPath As String) As Long
    Dim lSpc As Long 'sectors per cluster
    Dim lBps As Long 'bytes per sector
    Dim lNfc As Long 'number of free clusters
    Dim lTnc As Long 'total number of clusters
    
    
    Call GetDiskFreeSpace(sPath, lSpc, lBps, lNfc, lTnc)
    vbGetAvailableBytes = lSpc * lBps * lNfc
    
End Function

Private Function vbGetTotalBytes(ByVal sPath As String) As Long
    Dim lSpc As Long 'sectors per cluster
    Dim lBps As Long 'bytes per sector
    Dim lNfc As Long 'number of free clusters
    Dim lTnc As Long 'total number of clusters
    
    
    Call GetDiskFreeSpace(sPath, lSpc, lBps, lNfc, lTnc)
    vbGetTotalBytes = lSpc * lBps * lTnc
    
End Function

Public Function vbGetPercentAvailable(Optional ByVal sPath As String = "") As Long

	Dim freeEX As Currency
	Dim totalEX As Currency
	Dim availEX As Currency
	Dim percent As Long

	On Error Resume Next 'if API fails there will be divide by zero errors

	If ExistGetDiskFreeSpaceEx() Then
		If "" = sPath Then
			Call GetDiskFreeSpaceExAsCurrency(vbNullString, availEX, totalEX, freeEX)
		Else
			Call GetDiskFreeSpaceExAsCurrency(sPath, availEX, totalEX, freeEX)
		End If
	Else
	   totalEX = vbGetTotalBytes(sPath)
	   availEX = vbGetAvailableBytes(sPath)
		
	End If

	totalEX = totalEX * 10000
	availEX = availEX * 10000
	percent = (availEX * 100) / totalEX

	vbGetPercentAvailable = percent

End Function

Adjusting windows border width in Windows 8

Window borders are not something you usually think about. They're just there, keeping a visual cue of the current workspace. Did you could change the width of these borders? Some folks want just like small borders.

Shrinking the border provides a bit of a cleaner feel to the windows, and gains a couple of extra pixels in the workspace. In Windows 7, it was pretty easy to open the control panel and adjust to your liking. Windows 8 doesn't have this feature in the control panel, but you can adjust the border width with a straightforward registry change.

There are two settings you can adjust that affect the border width, each having a range of 0 to -1500. The default setting for the BorderWidth property is -15, while the default for PaddedBorderWidth is -60.

To make a thicker border, simply increase the integer value in these fields:

[HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics]
"BorderWidth"="-15"
"PaddedBorderWidth"="-60"

Higher numbers (for example -1000) will give you a thicker border, while lower numbers (0 or -1) will give you thinner borders.

After you have made the changes, you'll need to log out, then back in, to see the changes.

Dell XPS 12 - Worth it ?

Today, I got the opportunity to lay my hands on a Dell XPS 12. What's so special about the XPS 12? It's not sure what it is.

Seriously. The XPS doesn't know if it wants to be a laptop or a tablet. Fortunately for us, this small but powerful unit does both well. Read on for the details.

The XPS 12 is Dells latest entry in the "executive jewelry" category of ultrabooks. It's small and light, packing in a strong processor, and enough RAM to perform just about any business task.

Let's get the tech specs out of the way. The unit that I tested with was fully decked out with:

3rd Generation Intel Core� i7-3517U processor (4M Cache, up to 3.0 GHz)
8GB Dual Channel DDR3
256 GB SSD

Standard features of all XPS 12 tablets are:

Windows 8, 64-bit
12.5" FHD 1080p touch display
Intel HD 4000 video
Realtek ALC3260 soundcard (dual digital array microphones, 2-1 watt onboard speakers)
Mobile Intel QS77 Express Chipset
1.3MP webcam
Intel Centrino Advanced-N 6235 802.11 a/g/n with Intel Smart Connect Technology + Bluetooth 3.0
Intel Wireless Display (WiDi) 3.0 ready
Standard full size, backlit chiclet keyboard; spill-resistant
Glass integrated button touchpad with gesture support
Glass integrated button touchpad

As with most ultrabook-class devices, ports are not as numerous as on larger laptops, but the essentials are there:

1, 9-pin USB 3.0 port
1, 9-pin USB 3.0 port with PowerShare and Windows debugging
1, 20-pin mini-display port
1, headphone/microphone combo port

Using the device as a notebook, it's exactly what you would expect. Small, but with a punch. Boot time was quick, thanks to the roomy amount of RAM, speedy processor, and especially the solid state drive. Visibility of on screen elements was pretty good. The 1080p display has a 160 degree viewing angle, that makes sharing the screen with a friend not too cozy. Remember, it is a small screen, not your 52-inch plasma.

Operation of Windows 8 on the device was equally zippy. Moving in and out of applications, installing new items from the app store, and even playing videos was smooth and responsive. A lightweight device for road warriors to get things done while stuck on a plane for six hours.

Most of the XPS is made up of carbon fiber, on the main body and on the back of the display, with a painted magnesium palm rest. In usual Dell style, an excellent Chiclet keyboard is present. Typing was no problem, even with my big meat hooks.

Now on to the magic, the reason this is classified as a hybrid device. That aluminum bezel is not just a bezel to hold the screen in place, or to just look pretty. It's the hinge/frame for the tilting screen. Simply push the top of the screen back a bit, and it does a full 180 degree flip. then you can close the clamshell, and voila, you have a Windows 8 tablet. Nifty, eh?

This baby was made for Windows 8. The touch screen is responsive and accurate, and I never had a problem doing drag-n-drop operations, selecting tiles or menu options, or even writing with my finger. The on-board camera is still facing you, so you can have your cam-based chats and meetings, without the keyboard getting in the way.

But.

The Dell XPS is just a bit heavier than the iPad, 3.35 pounds versus 1.44 pounds. So be prepared for the extra heft. However, in my opinion (based on my brief experience with the Dell unit), the XPS 12 seems to be more "balanced", and not quite as clumsy in my hands. So in short, my hands didn't seem to be getting tired or fatigued while using the unit for a period of time.

Honestly, I think this weight difference can be forgiven, given the extra 2.4 inches of screen real estate that comes with it.

I currently utilize an iPad 2, mainly for light email, light surfing, and the occasional Angry Birds stress relief. For getting real work done while traveling, I break out my trusty Latitude 6410. There is no way that I can really do serious work on the iPad. It's a consumer device, not a business device. Hence the need to carry both a laptop and a tablet when I travel. One for work, and one for not work.

After using this device for a short period, I would defintely consider this as a purchase. It definitely has the horsepower I need to get things done for my job, and can act like a prosumer consumption device.

It might be a little spendy, for those just looking for a new device that won't get used very often. But if you are serious road warrior, who needs to cut down on the number of devices you tote around in the performance of your duties, I would highly recommend you check out the Dell XPS 12. It's worth cash, in my humble opinion.

Now, how can I get my hands on a long term tester?

Recent Articles on FortyPoundHead.com

Killing Disconnected Terminal Server Sessions

Why would you pay $12.95 per month ?

Living with the Surface

Three Windows Command Prompt Replacements

Console

PowerCMD

PromptPal

Your Favorite Documentation Tool?

ShellFileCopy with VB6

Compare Two Files in VB6

Get Available Drivespace with VB6

Adjusting windows border width in Windows 8

Dell XPS 12 - Worth it ?