I have a Westell Versalink Model 327W that Verizon Online gave me with my DSL account. I decided that I didn’t want to use it, because I already had a D-link router that was satisfactory for my needs.

Verizon, of course, had the Versalink router pre-configured with an admin password, so I could not change any settings.

So, I powered it on, while holding down the reset button.

Once it came back online, I was able to guess the default password for the Versalink, which is admin/password. That is, username=admin, password=password

Now, I discovered that this dsl modem/router has a really slick feature! Instead of using the DSL port (which is just a phone jack) as the WAN port, you can turn Ethernet port 1 into the WAN port.

Once I got the Versalink “unlocked” from Verizon’s custom configuration, I was able to access all the normal administrative menus. Here is a link to the documentation at Westell.com.

http://www.westell.com/content/sales/327W.pdf

Anyway, just to make it easier for people to find this information here is some search engine fodder:

default password versalink westell 327w verizon online admin password default admin password westell versalink model 327w

Got some bits & pieces and… bits & pieces and… (Weird Science…) But no, I won’t be wearing a bra on my head, not even for ceremonial purposes.

300W Power inverter = $24
PS/2 Mini-keyboard = $17
Mini power supply (350w ATX) = $29
1.2 GHz wireless camera with IR illuminators (100ft RF transmitter range) = $50 (wow!)
15′ USB extension = $5
PS/2 KVM with integrated cables (Linksys) = $35

Had to figure out that to make an ATX psy turn on without hooking it up to an ATX mobo, you have to short the green wire to ground.

I got Windows 2000 to run on my board last night, and today managed to munge the system so badly that I think I’ll have to start fresh. We got the touch-screen working under W2k, and then got the bright idea to install the audio drivers. Whoops! Somehow, W2k just BSODs every time I boot now.

Booted back into W98 (yeah, dual-boot is for losers, but what are ya gonna do…) and deleted the offending driver file, but now the BSOD references another one… swenum.sys I think. Ugh… time to nuke it from space… it’s the only way to be sure.