Monday, May 16, 2011
Sunday, May 15, 2011
Saturday, May 14, 2011
Maxtor Central Axis password reset
Solved the password problem - Seagate Community Forums
passwords can only be alpha-numeric. No special characters. Too bad it doesn't warn you about that ahead of time.
So, to reset the device (without deleting any data, of course), do the following:
Using the end of a stretched-out paperclip, press and hold the reset button under the base of the device. The indicator on the right side will start flashing, and eventually the middle indicator will flash red once. When that happens, release the reset button. Then the right side indicator will flash again and eventually return to solid.
At this point you can go back to the Maxtor Manager software on your computer and go back through the initial setup process. Just be sure to set the admin password with only alpha-numeric characters.
Friday, June 19, 2009
Thursday, June 11, 2009
comcast dvr
Transferring Recorded or Live Programs to a Computer
DCT64xx Firewire capture and HD/SD to DVD guide
MCE 2005 STB Controller
HowTO record via 1394/Firewire to WindowsXP now with MCE support
Make your own Home Theatre Mac (HTMac)
How to Buy a DVD Recorder
Record and playback high definition TV signals
DCT64xx Firewire capture and HD/SD to DVD guide
MCE 2005 STB Controller
HowTO record via 1394/Firewire to WindowsXP now with MCE support
Make your own Home Theatre Mac (HTMac)
How to Buy a DVD Recorder
Record and playback high definition TV signals
Tuesday, May 19, 2009
Monday, May 4, 2009
Saturday, April 25, 2009
Thursday, April 9, 2009
Wednesday, March 18, 2009
vbscript links in no particular order
Tuesday, March 10, 2009
Tuesday, March 3, 2009
Thursday, February 26, 2009
run .msi files as admin
If you are using Vista with UAC enabled, you may have noticed that some existing MSI packages may not install as expected.
Here's a fix.
The reason is because Windows Installer by default doesn't elevate to higher privileges until it is about to actually start doing work in the install sequence.
The attached .REG file adds a "Run as administrator" option to the context menu for .MSI files. This forces an elevation prompt before the .MSI is run so the entire install session is run with elevated privileges.
this dose not seem to work with .msi's living on network drives once moved to a local drive life is fine
Here's a fix.
The reason is because Windows Installer by default doesn't elevate to higher privileges until it is about to actually start doing work in the install sequence.
The attached .REG file adds a "Run as administrator" option to the context menu for .MSI files. This forces an elevation prompt before the .MSI is run so the entire install session is run with elevated privileges.
this dose not seem to work with .msi's living on network drives once moved to a local drive life is fine
getip
====================== ie progress msg/bar ==================
===================== network adaptot settings=================
| Assign a Static IP Address |
| • | Assign the DNS Domain for a Network Adapter |
| • | Assign the WINS Server for a Network Adapter |
| • | Enable Dead Gateway Detection for All Network Adapters |
| • | Enable DHCP |
| • | Enable DNS on All Network Adapters Enable WINS for All Network Adapters . Send an empty array to the settings This eliminates the servers. Sample scripts for configuring TCP/IP settings (IP address, DNS Server, WINS Server, etc.) on client computers. |
| Retrieving Network Configuration Information Sample scripts for retrieving information about TCP/IP settings on client computers. |
List Network Adapter Connection Status
Submitted by: Anonymous
'==========================================================================
'
' VBScript Source File -- Created with SAPIEN Technologies PrimalScript 2007
'
' NAME: getGatewayAD
'
' AUTHOR: mmccafferty1 , pps
' DATE : 3/3/2009
'
' COMMENT:
'
'==========================================================================
Sub getGatewayAD()
Set objShell = CreateObject("WScript.Shell")
Set objWshScriptExec = objShell.Exec("ipconfig /all")
Set objStdOut = objWshScriptExec.StdOut
Set objRegEx = CreateObject("VBScript.RegExp")
objRegEx.Global = True
objRegEx.Pattern = "\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}"
While Not objStdOut.AtEndOfStream
strLine = objStdOut.ReadLine
Set colMatches = objRegEx.Execute(strLine)
If InStr(strLine,"Gateway") And colMatches.Count > 0 Then
For Each strMatch in colMatches
Wscript.Echo strMatch.Value
arroctetts = Split(strMatch.Value,".")
Next
WScript.Echo UBound(arroctetts)
End If
Wend
For octett = 0 To UBound(arroctetts)
WScript.Echo octett & " " & arroctetts(octett)
Next
End Sub
Sub pingsubnet()
getGatewayAD
Dim WshShell, WshPing, strPingResults
Set WshShell = WScript.CreateObject("WScript.Shell")
'ping the subnet & put non ping addrs In a file
' Wscript.StdOut.Write strPingIP
For host = 2 To 254
Set WshPing = WshShell.Exec("ping -n 3 -w 1000 " & strPingIP) 'send 3 echo requests, waiting 1 sec each
strPingResults = LCase(WshPing.StdOut.ReadAll)
Next
End sub
Windows XP and Windows Server 2003 Behavior When Connected to Both Wired and Wireless Networks
How Can I Tell If a Wireless Network Adapter is Connected to the Network?
Querying wireless status in Windows with VBScript and WMI
MSNdis_80211_ServiceSetIdentifier
How Do I Find Information About the Network Adapter Cards on My Computer?
vba-ping
Function PingSilent(strComputer)
Set objPing = GetObject("winmgmts:{impersonationLevel=impersonate}")._
ExecQuery("select * from Win32_PingStatus where address = '"_
& strComputer & "'")
For Each objStatus in objPing
If IsNull(objStatus.StatusCode) or objStatus.StatusCode<>0 Then
'WScript.Echo("Computer " & machine & " is not reachable")
PingSilent = 0
Else
'WScript.Echo("Computer " & machine & " is Live")
PingSilent = 1
End If
Next
End Function
IcmpSendEcho: Ping a Machine by IP Address
Tuesday, February 24, 2009
comcast info
Comcast High Speed Internet FAQ
list of comcast approved modems
list of comcast approved modems
self install. info from comcast
how 2Connecting the modem and a television to the same cable wall outlet
| Step 1: Connect the modem to the cable outlet. | ||
| Disconnect the cable going to your television from the cable wall outlet. | ||
| Use the short coaxial cable to connect the cable wall outlet to the single input on the splitter. | ||
| Connect the cable going to your television to one of the outputs on the splitter (the outputs are the two jacks on the same side). | ||
| Connect one end of the long coaxial cable to the second output on the splitter. | ||
| Connect the other end of the long coaxial cable to the cable input on your cable modem. | ||
| Step 2. Connect the modem to the computer, depending on the type of port available. | ||
| For Ethernet ports, use the Cat-5E cable to connect the port on the cable modem to the port on your computer. | ||
| For USB ports, use a USB cable (not included) to connect the port on the cable modem to the port on your computer. | ||
| Step 3. Install the software. | ||
| Insert the High-speed Internet Install Wizard CD to install the software. | ||
Connecting the modem to a different cable wall outlet than a television
| Step 1: Connect the modem to the cable outlet. | ||
| Use the long coaxial cable to connect the cable wall outlet to the cable input on your cable modem. | ||
| Step 2. Connect the modem to the computer, depending on the type of port available. | ||
| For Ethernet ports, use the Cat-5E cable to connect the port on the cable modem to the port on your computer. | ||
| For USB ports, use a USB cable (not included) to connect the port on the cable modem to the port on your computer. | ||
| Step 3. Install the software. | ||
| Insert the High-speed Internet Install Wizard CD to install the software. | ||
Sunday, February 22, 2009
internet speed tests
Internet Speed Test - Broadband, DSL Bandwidth Connection Check + two more very cool speed tests that you can take?
Friday, February 20, 2009
home networking
However, to really secure this so that there isn't an inadvertant hole that someone else might sneak through when you're elswhere you need to make sure the local, approved address (all this traffic management will be IP address based) of the Toshi. is not likely to be replicated at the library.
There are 3 "private" address ranges available for use that never appear on the internet. They are:
a) 10.0.0.0 to 10.255.255.255 - this is a single class A range. Mask is 255.0.0.0
b) 172.16.0.0 to 172.31.255.255 - These are 16 class B ranges. Mask is 255.255.0.0
c) 192.168.0.0 through 192.168.255.255. These are 256 class C addresses and thus normally have a 255.255.255.0 mask
The library network will be on one of these 3 sets of addresses, as will your home LAN.
You will most commonly see either 192.168.0.0/24 (the /24 means 24 bit mask, or 255.255.255.0) or 192.168.1.0/24. The next most common is 10.0.0.0/8 (the /8 is, of course, an 8 bit mask or 255.0.0.0)
If you select a very uncommon range for your LAN at home then you can be reasonably confident of leaving your firewall open for that range. I would also consider using a non-standard mask for the local LAN IF your router/access point will allow and the built in DHCP server can cope.
Perhaps use a 172 range, like 172.29.0.0/28 - this would make available the address range 172.29.0.0 to 172.29.0.15 (14 usable addresses the lowest is always the network identifier and the highest is the broascast address so you always lose 2) - the decimal mask would be 255.255.255.240 - a most unusual mask to use with a class B address as well as being a largely unused private range allocation. Not perfectly secure, but the first step in security should always be obscurity. The reason for the non-standard mask is to further secure things. Even if you happen to connect to a LAN using the same base address range (the 172.329.0.0 part) your machine will still be inaccessible UNLESS they have also picked the same mask.
So, the easy way to alleviate this is to fix the addresses on the AD HOC network. Make the addresses from one of the ranges mentioned in my previous post (192.168.x.x, 172.17 to 21.x.x or 10.x.x.x - I suggest you use something from the 172 ranges to reduce the possibility of a conflict with any wired network you might connect to). Masks on both machines should match, addresses should be different but within the range defined by the mask. E.G. 172.18.1.1 and 172.18.1.2 with a mask of 255.255.255.248 (this will define a range of 172.18.1.0 to 172.18.1.7. Remember, the 0 and 7 are network and broadcast respectively so only 1 to 6 are available.
Then, you should be able to connect to the other machine by IP address rather than hoping the name will work (there's that slow browser service again). You can always update your local hosts files if you really want to use names. (C:\windows\system32\drivers\etc\hosts) Edit it with Notepad - the syntax has examples in the file. Make sure you end the last line with an
Also, in this kind of situation it is probably best to go into the TCPIP properties, Advanced button, WINS tab and make sure that either the "Default" or "Enable Netbios over TCP/IP" radio button is selected - if in doubt, select the "Enable..." option.
Get this going with your firewall disabled, then enable it to setup the additional security. Using encryption on the wireless is also a good idea, but again, get it going first then add the encryption - then if it stops working, at least you'll know where to look
There are 3 "private" address ranges available for use that never appear on the internet. They are:
a) 10.0.0.0 to 10.255.255.255 - this is a single class A range. Mask is 255.0.0.0
b) 172.16.0.0 to 172.31.255.255 - These are 16 class B ranges. Mask is 255.255.0.0
c) 192.168.0.0 through 192.168.255.255. These are 256 class C addresses and thus normally have a 255.255.255.0 mask
The library network will be on one of these 3 sets of addresses, as will your home LAN.
You will most commonly see either 192.168.0.0/24 (the /24 means 24 bit mask, or 255.255.255.0) or 192.168.1.0/24. The next most common is 10.0.0.0/8 (the /8 is, of course, an 8 bit mask or 255.0.0.0)
If you select a very uncommon range for your LAN at home then you can be reasonably confident of leaving your firewall open for that range. I would also consider using a non-standard mask for the local LAN IF your router/access point will allow and the built in DHCP server can cope.
Perhaps use a 172 range, like 172.29.0.0/28 - this would make available the address range 172.29.0.0 to 172.29.0.15 (14 usable addresses the lowest is always the network identifier and the highest is the broascast address so you always lose 2) - the decimal mask would be 255.255.255.240 - a most unusual mask to use with a class B address as well as being a largely unused private range allocation. Not perfectly secure, but the first step in security should always be obscurity. The reason for the non-standard mask is to further secure things. Even if you happen to connect to a LAN using the same base address range (the 172.329.0.0 part) your machine will still be inaccessible UNLESS they have also picked the same mask.
So, the easy way to alleviate this is to fix the addresses on the AD HOC network. Make the addresses from one of the ranges mentioned in my previous post (192.168.x.x, 172.17 to 21.x.x or 10.x.x.x - I suggest you use something from the 172 ranges to reduce the possibility of a conflict with any wired network you might connect to). Masks on both machines should match, addresses should be different but within the range defined by the mask. E.G. 172.18.1.1 and 172.18.1.2 with a mask of 255.255.255.248 (this will define a range of 172.18.1.0 to 172.18.1.7. Remember, the 0 and 7 are network and broadcast respectively so only 1 to 6 are available.
Then, you should be able to connect to the other machine by IP address rather than hoping the name will work (there's that slow browser service again). You can always update your local hosts files if you really want to use names. (C:\windows\system32\drivers\etc\hosts) Edit it with Notepad - the syntax has examples in the file. Make sure you end the last line with an
Also, in this kind of situation it is probably best to go into the TCPIP properties, Advanced button, WINS tab and make sure that either the "Default" or "Enable Netbios over TCP/IP" radio button is selected - if in doubt, select the "Enable..." option.
Get this going with your firewall disabled, then enable it to setup the additional security. Using encryption on the wireless is also a good idea, but again, get it going first then add the encryption - then if it stops working, at least you'll know where to look
Subscribe to:
Posts (Atom)