 Taken back in March when Emil & his girlfriend were visiting. For some reason I didn’t take pictures of the informational signs, so I don’t actually remember which waterfalls these are pictures of. They’re in the Columbia River Gorge, off the old highway. I’ll have to head back out there sometime & capture what the names are... Now playing: Stars – Sad Robots (EP) – 05 14 Forever
Lewis and Clark Bridge across the Columbia River between Rainier, OR and Longview, WA. Taken last year while heading to the coast via Astoria. Fort Clatsop (replica) in the Fort Clatsop National Historical Park. It was prettier when I was there in July (2007), but unfortunately I don’t seem to have any pictures from that! Astoria Bridge that carries US 101 across the Columbia River at Astoria, OR. The beach at Nehalem Bay State Park. See, not all days out at the coast during winter are that bad... ...just don’t look in the other direction. Or maybe it was just luck that there was a clear patch right over the part of the beach I was walking on. On the dune right next to the beach at Nehalem Bay State Park. Cannon Beach. The water seemed colder then at Nehalem beach when I was walking around out in it. Now playing: Lifehouse – Lifehouse – 01 Come Back Down
It was hot Friday and Saturday. Which meant I was busy being lazy and staying cool by sitting in my car (with its AC running). I should have posted this when it was 100+ degrees out, but I didn't, but now it's appropriate again because snow is predicted to fall in the mountains tomorrow! Yes, the weather has gone crazy this year. Outside my apartment window, back in February. Now Playing: Brenda Weiler – Fly Me Back – 09 Fly Me Back
US 26, right after/before the tunnel through the west hills. Looking towards downtown & PSU. Houses/apartments/condos/whatever built on the side of the west hills. Now Playing: Po' Girl – Home to You – 09 9 hrs to Go
So...I switched over from SharePoint to dasBlog as the blog engine on the site. This means that the RSS feed URL has changed. The old ones should all still work, courtesy of the magic of 301 redirects, but still, everyone likes to be up-to-date, right? The new URL for the main site feed is: http://www.ntldr.com/SyndicationService.asmx/GetRss Now Playing: Lightning Dust – Lightning Dust – 01 Listened On
Downtown Portland, from the Vista Viaduct over Goose Hollow. That's the MAX (public transit train) just starting to go by. The viaduct (looking east-ish towards downtown). This picture was taken in February instead of January, so that's why the sky isn't as dreary a shade of gray. Another picture from February of the Viaduct. Now Playing: Coldplay – Viva la Vida – 07 Viva la Vida
In response to this post, yes, you actually can "run" PowerShell on Windows 2000. No, there is no out of the box way for it to run. No, it's not supported in the slightest. I'm not even sure it's technically legal (haven't read that Windows EULA in a long time). And even when it is running, there are likely to be things that don't work. That said, here's how to get Windows PowerShell v1.0 to run on Windows 2000. What you will need Creating the installer (on Windows XP) - Install the .NET Framework 2.0 SDK. You'll need a specific tool from it, and it's easier to just install the SDK and grab the tool than it is to try and extract it somehow.
- Extract KB926139 (run 'WindowsXP-KB926139-v2-x86-ENU.exe /extract').
- Make a copy of the 'powershell.exe' file that was extracted from KB926139. Now break out your hex editor, a copy of the Portable Executable Format Spec, and modify the header so the Windows 2000 loader will actually run the image. Or just use your hex editor to modify the byte beginning at offset 0x00000132 in 'powershell.exe' so it is 0x00 instead of 0x01 (Windows 2000 is version 05.00, not 05.01).
- Read the 'update\update.inf' file extracted from KB926139. This plain text file contains the instructions on how to install PowerShell on Windows XP, so all that's needed is for them to be duplicated on Windows 2000 (batch/reg files? windows scripting host? whatever you want!).
- 'PSCustomSetupUtil.exe /install' doesn't seem to actually work on Windows 2000. So use a combination of 'InstallUtil.exe' from the .NET Framework and 'GacUtil.exe' from the .NET Framework SDK (this tool is the entire reason the .NET Framework SDK is needed).
Installation (on Windows 2000) - Install the .NET Framework 2.0
- Follow the instructions in update.inf from the extracted KB926139 to install.
- Remember to substitute 'installutil.exe' and 'gacutil.exe' for usages of 'pscustomsetuputil.exe /install'.
- Replace the official version of powershell.exe with the one containing a modified header.
- Maybe create a shortcut and define console window appearance settings.
For the lazy: all scripted up I've gone ahead and deciphered the update.inf file, so if you're feeling lazy, just download this file and follow these instructions. Note that the included scripts assume that Windows is installed in C:\WINNT. If it's elsewhere, you'll have to modify all the scripts & registry files. - Unzip the 'install package.zip' file you just downloaded.
- Get 'gacutil.exe' and 'gacutil.exe.config' from the .NET Framework SDK. Place them in the NETFXSDK subdirectory of the unzipped install package.
- Get KB926139 and extract it to the KB926139 subdirectory of the unzipped install package.
- Copy 'powershell.exe' from the KB926139 subdirectory into the bin directory. Modify it as in step 3 of "Creating the installer".
- Take the whole install package structure, now with the PowerShell binaries/installer tools, to a Windows 2000 system and run the 'System Setup.cmd' batch file.
- (optional) Run the 'User Setup.js' script to configure the PowerShell window's default settings to match whatever I had on whatever system I was on when I figured all this out (most useful because it enables tab completion, which isn't on by default in 2k, unlike in XP and later).
Now Playing: Basia Bulat – Oh, My Darling – 07 In the Night
Here are some more pictures of Reservoir #3 in Washington Park, Portland, Oregon. I took them back in February, so you can tell I'm a bit behind on posting things... Now Playing: Josh Ritter – Hello Starling – Bone Of Song
At work, we use Maven to do builds for the project I work on. The Infrastructure IT people also have helpfully configured it so that every user account has a home directory conveniently located on a file server. Since we use Windows (Windows 2000 to be precise...), that home directory is a UNC path of the form \\server\share\folder.
This, it turns out, is rather bad for Maven.
See, Maven has a settings.xml file that allows you to configure it. Things like the local repository location, proxy settings, remote repositories, etc. get configured in that file. So it's kind of important. Maven looks for that file at <home directory>/.m2/settings.xml. And there in lies the problem with having <home directory> be a UNC path: Maven or Java or something just breaks, and that file isn't found/read.
Now, apparently if you put the file in C:\server\share\folder\.m2, Maven will find it. Sometimes. I didn't see consistent behaviour when trying that approach, and ended up abandoning it last year. Part of the problem may have been that different Maven things (mvn, Eclipse plugin) handled the exceptional situation differently, so builds might work from inside Eclipse and then fail on the command line.
So I began looking for a different approach, and took a look at the root cause of the problem. Attempting to get the Infrastructure people to change their policies and affect thousands of accounts as doomed to a slow failure, forcing me to try and find a workaround that was specific to my computer.
And at last! The grand unveiling! It's really quite simple in principle: if the home directory path is causing a problem, lets just make Maven see a different path. Doing so isn't quite that simple though.
Here are the steps:
- First, a user specific HOME variable is created, pointing to the location the home directory needs to be redirected to.
- Then define a system wide JAVA_OPTS variable, with the value of "-Duser.home=%HOME%". This isn't strictly necessary to get Maven itself to run, but is useful for creating a consistent experience with Java applications and this home directory redirection scheme.
- Now, the magic Maven command-fu: create another system wide variable, MAVEN_OPTS. Value is "-Duser.home=%HOME%". Yes, this is the same as the JAVA_OPTS value. But mvn reads MAVEN_OPTS instead of JAVA_OPTS.
- A bit of Eclipse integration: edit the eclipse.ini file and add the "-Duser.home=%HOME%" (note that I think you have to expand the %HOME% to the actual value; I doubt Eclipse uses Windows command prompt style variable referencing syntax) string after the -vmargs option. Now Eclipse will use the redirected home directory during startup.
- More Eclipse integration: plugin/feature support: Go to Window->Preferences->Java->Installed JREs and edit any entries so they contain the VM argument "-Duser.home=%HOME%" (again, have to expand that %HOME% yourself to what the value is).
Okay, that should be it for just Maven. In theory these steps could be applied to other Java apps that have problems with finding settings in home directories. I've been lucky enough not to run into any of those apps though.
Now playing: Basia Bulat – Oh, My Darling – 07 In The Night
First it was the IIS box serving this site, but now it's going to be the whole network that's moving to Windows Server 2008. I'm attempting to go with a complete new forest installation, which will force migrating everything over from the old Server 2003 forest, so that should be interesting. And now, onto the first notes about that experience!
So...here's what's happening: installing a "new" server using Windows Server 2008, making it the first DC in the domain, and then installing Virtual Server 2005 R2 SP1 Enterprise (okay, can that name get any longer?!) without installing IIS. And it's the Core version of Server 2008, so everything is via the command line. After having worked on it for the better part of today, I'm now sitting here wondering why the heck anyone would use Core. I mean, if I wanted a command line only interface, I'd just use BSD or Linux!
For future reference here are a couple of things:
Useful commands:
pnputil -i -a <inf> (install device drivers (I think...I haven't confirmed if this actually installed them yet))
cscript %systemroot%\system32\scregedit.wsf /au 4 (Enable automatic updates)
cscript %systemroot%\system32\scregedit.wsf /ar 0 (Enable Terminal Services)
cscript %systemroot%\system32\scregedit.wsf /im 1 (Enable remote IPSec management)
netsh interface ipv4 show interface (get the list of names for use in other netsh commands)
Feldspar:
netsh interface ipv4 set address name=2 source=static address=10.0.1.9 mask=255.0.0.0 gateway=10.0.0.1
netsh interface ipv4 set address name=3 source=static address=10.0.1.10 mask=255.0.0.0 gateway=10.0.0.1
netsh interface ipv4 add dnsserver name=2 address=10.0.1.9 index=1
netsh interface ipv4 add dnsserver name=3 address=10.0.1.10 index=1
Useful links:
http://blogs.technet.com/shinsley/archive/2007/04/19/windows-server-longhorn-server-core.aspx
http://blogs.technet.com/server_core/archive/2008/04/16/reducing-the-server-core-disk-footprint.aspx
http://support.microsoft.com/kb/890893/en-us
|
About the author

Jeffrey Stults is a software developer currently in Portland, Oregon. He is contactable at:
stultsj@ntldr.net
Archive
| | Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|
| 26 | 27 | 28 | 29 | 30 | 31 | 1 | | 2 | 3 | 4 | 5 | 6 | 7 | 8 | | 9 | 10 | 11 | 12 | 13 | 14 | 15 | | 16 | 17 | 18 | 19 | 20 | 21 | 22 | | 23 | 24 | 25 | 26 | 27 | 28 | 29 | | 30 | 1 | 2 | 3 | 4 | 5 | 6 |
Disclaimer
Disclaimer
The opinions expressed herein are my own personal opinions and do not represent
my employer's view in any way.
© Copyright
2012
Jeffrey Stults, Jr.
Statistics
Total Posts: 256 This Year: 0 This Month: 0 This Week: 0 Comments: 23
Utilities
Pick a theme:
Sign In
|