122 Posts Displaying page 3 of 13
< >

Displaying page:

Software - XP
Aug 24, 2005

Properties in Right-click context menu for folders not working

Close ...
Platform: XP Pro with SP1

This has been happening as an intermittent problem and getting annoying. The problem was basically down to an interaction problem with IIS and Zonealarm. When I did a reset of the IIS (iisreset in the cmd window) suddenly all the properties windows I had been trying to get popped up.

Further details of this problems can be found at - html

The DependOnService registry fix as outlined tends to indicate that the W3SVC needs to be started before the TrueVector service is started.

Hardware - Windows
Aug 24, 2005

Mapping a Windows key on IBM R51 ThinkPad

Close ...
Use the Access IBM facility.

Configure>Manage Keyboard & Pointing Devices>Map Keys to Functions

A good key to use seems to be the Right Alt Key (AltGr on the keyboard)

Aug 07, 2005

Networking printers on wireless LAN

Close ...
Using 54G wireless LAN with PowerBook G4 client running OS 10.2 (Jaguar) and Samsung ML-1210 laser printer (USB) on an XP SP1 client.

My experience was as follows:

There seems to be 2 fundamental approaches that can be used to allow a Mac OSX machine to use a Windows XP hosted printer.

use the inbuilt SAMBA functionality of the OSX

use IP Printing approach in OSX

I initially had some success with the SAMBA method when trying an Epson 740 colour inkjet printer - this was made easier by the fact that the Epson drivers were easily found/already installed in the Mac's Print Centre.

A good run down on the procedure is found at - ows.html

I later found another procedure using the IP Printing mode in the OSX Print Centre and despite the numerous hassles I had getting it to work it is the more straightforward approach.

A good run down on this is given at -

Thanks to Anonymous who posted this one - the main detail was -

On the WinXP Box:

Add the TCP/IP print server service

1. Log in with Administrative privileges.

2. Click Start -> Settings -> Control Panel.

3. Double-click Add-remove Programs.

4. Click the Add-Remove Windows Components side button.

5. Open the Other Network File and Printer Services section.

6. Put a checkmark in Print Services for Unix.

7. Click OK; click Next. (The Computer will probably ask for the WinXP install disk, go ahead and put it in and the install will run automatically.)

8. Click Finish.

9. Close the Add-remove programs window.

To have the service start automatically (as a daemon):

1. Click Start -> Settings -> Control Panel.

2. Double-click Administrative Tools.

3. Double-click Services.

4. Double-click TCP/IP print Server.

5. Change the "Startup Type" to Automatic.

6. Click OK and close the windows that are open.

To share the printer for TCP/IP printing:

1. Click Start -> Settings -> Printers.

2. Right-click the print you want to share and select Sharing.

3. Click the radio button for Share as and fill in the share name you want to print to.

On your Mac:

1. Launch the Print Center.

2. Click the "Add Printer" button.

3. Change "Appletalk" to "IP Printing"

4. Enter the WinXP Computer's IP address in the Address box.

5. Uncheck the default queue radio button.

6. Enter the name of the printer share you defined on the XP machine.

7. Select your printer model (Install Gimp-Print if you don't see a ppd for your printer, restart print center and try again).

My take on the procedure was -

Installing/enabling the Print Services for Unix in XP is no problem (you do need the XP CD of course).

Setting the Service to Startup Type=automatic is straight forward.

The Mac Print Centre (for me unknown territory) was the first area of delay.

Selecting the IP Printing was easy and the printer share just had to be SamsungM (as in the XP box) however I came to understand that the actual printer driver needed to be installed in the Print Centre. Samsung drivers are not included in the OSX load so I needed to find some.

This place was excellent -

The ESP GhostScript package had already been installed at some stage earlier in the great adventure so I just needed to install the Samsung package. It worked beautifully and appeared in the Print Centre as I expected.

The printing was being submitted with no errors but nothing happened.

The Event Viewer in XP showed entries relating to the LPDSVC (Line Printer Daemon Service) and was suggesting problems with the path/share.

The sharing was indeed where the problem lay.

Setting the sharing against the printer was a hassle for me - normally it is straight forward but for some reason when I hit the APPLY button the applet would go into a "Not Responding" state. The result was the printer was in a half shared state. When I tried to set it the PC would "suggest" a name (eg: SamsungM) even if I typed another so go with the suggestion. If I disabled and then re-enabled the share the suggested name became something like SamsungM.2 (the next time it was SamsungM.3 and so on). Checking the registry confirmed that the share name wasn't registered in as many places as it should be so eventually I decided to go for the usual troubleshooting method for Windows and restart the machine whereupon I found it went into limbo and I couldn't even get Task Manager to fire up (there is still a good case for even XP to qualify for the CrapOS tag) so I waited for 20 mins (sometimes things start happening after XP has had a smoko) and still limbo so did the big power switch thing (Scandisk was invoked on restart).

Well - things looked up, the share had been lost but when I reapplied it the suggestion for the sharename was SamsungM and the registry was more complete (It looked better when I hit the OK button rather than the APPLY button because the window closed and no limbo).

Bingo- after the sharing was properly invoked the printer worked.

So all in all the networking of the Samsung ML-1210 in theory should have been a 10 minute job - I took a bit longer getting there but the tortoise made it and the IP Printing method works well.


I found the LPD method broke on 10.3 however a reasonably easy alternative is available.
The Print Center died with 10.2 but has been replaced by the Printer Setup Utility in 10.3. The XP end basically remains the same ( in my case the printer shares was SamsungM ) the only other embellishment was to create a user account on the XP machine.

In the OSX -

Go to Printer Setup Utility
Select Windows Printing
Select Network Neighbourhood
Select the network eg: HOMELAN
Enter USER/PASSWORD combo (this doesn't show if the Keychain Save has been used previously)
Select the printer share from the list shown eg: SamsungM
Select printer model eg: Samsung ML-1210,Foomatic & GDI

That's it folks!

A really useful visual management tool in OSX 10.3 is the CUPS printers page in the browser which shows the status of the printers along with errors, etc

URL is

Hardware - Windows
Aug 07, 2005

Printer Sharing on XP Pro SP1

Close ...
Whether it is a real problem or just a quirk of my particular install of XP there is a problem with applying a share to a printer.

I check the "Share this printer" radio button and the Share name text box populates with a suggested name of 8 chrs in length. Changing this usually gets mixed results but if I accept the suggestion and APPLY or OK the applet goes into a "Not Responding" state. I need to close the window and after a few flash of the desktop graphics the system recovers. On viewing the printer in the Printers and Faxes part of the Control Panel the printer appears shared however if I go the the Sharing tab I see an erroneous name such as EpsonSty.2 and viewing the registry confirms that the share hasn't been fully applied.

Particular registry entries I check are -

HKLM/SYSTEM/CurrentControlSet/Control/Print/Printers/Epson Stylus

Share Name REG_SZ EpsonSty

HKLM/SYSTEM/CurrentControlSet/Control/Print/Printers/Epson Stylus
COLOR 740 ESC/P 2/DsSpooler

printShareName REG_SZ EpsonSty (this is missing usually)

If the sharing is disabled and re-enabled then the same happens but the suggested name just increments - eg:

EpsonSty becomes EpsonSty.2 then EpsonSty.3, etc

It seems a bit hit and miss but to resolve the issue I did the following which appears to work.

Unplug USB printer

Disable the share

Delete the printer

Use Regedit -

Clear out entries such as EpsonSty, EpsonSty.2, etc from various keys as below.



Close Regedit and restart PC. The only stuff left should be the old driver installs which are OK.

Plug in USB printer and XP should soon pick it up and then acknowledge it has been installed because the drivers are still in place.

Jun 10, 2005

Clients using Belkin F5D7000 wireless card

Close ...
XP client using Belkin F5D7000:

Had problems with wireless link dropping out. Got to a stage that the wireless link would not connect at all and it was the same with two different hard disks running XP SP1 in the same P4.

Resolution: Quite a bit of horsing about on this which is par for the course with CrapOS, etc but relocated the WAG54G to a position c. 8cm from the client aerial and still no connection (I had doubts about the integrity of the Linksys signal). I think the problem stems back to the fact that the Belkin F5D7000 card was sourced in NZ (designated F5D7000au) and the original setup CD is an Oz/NZ distro. I had applied later UK upgrade updates on top of this driver since the UK driver updates require the base CD to be installed whereas the updates for Aus/NZ are standalone and don't necessarily require the original CD. So lesson learn't that I will continue using the Oz/NZ driver updates for my card and all seems solid enough at the moment. I managed to install the driver without the full wireless monitor utility which may also make a difference as the utilities appear to affect the card operations very intermittently ( this may however only be the case when the drivers are horribly mixed as they were before re-installation correctly).

During all the hassle of course I found that there are updates to XP for wireless -

KB815485 - Overview of the WPA Wireless Security Update in Windows XP


Jun 10, 2005

Linksys WGA54G-UK

Close ...

Use PC connected via ethernet & run Setup CD

Select "Connect to Internet" (Infrastructure) Note: Head to Head is Adhoc setting

Set gateway to (WAG54G router G/W)

Initially the Xbox needs the dashboard to be updated by running the Xbox Live CD.

Re-power the Xbox without the CD and Dashboard should give the Xbox Live option.

If DHCP is used on the G/W router then the Xbox will find the Xbox Live server and download the updates.

If DHCP is not used then the IP address,mask,G/W, DNS details will have to be specified in the Xbox.

Using DHCP Rainbow Six(3) loses connection.

When Xbox started after WGA54 was on got "No Connection".

Needed to go to Dashboard, select Settings & Troubleshooting. The Xbox then did scan and picked up the IP, DNS etc.

Preferable to run Xbox on static settings?

Port Fwding recommendations

88 UDP

3074 UDP

3074 TCP

Jun 10, 2005

Linksys WAG54G Wireless ADSL/Router/Gateway

Close ...
F/W 1.01.7

Required standard UK setting of -

RFC2364 PPPoA, VPI=0, VCI=38 & VC multiplexing for the DSL interface.

Configuration can be done via web interface (default http:// is

Using iBook - MS Explorer 5.1 for Mac NBG (No Bloody Good)
- Netscape 7 for Mac OK

Using PC both IE & Mozilla are fine (see below: use IE for firmware upgrading)

Issue: "wireless clients connected" button in STATUS>WIRELESS screen fails to show the networked clients unless they are using DHCP addresses. Using the Refresh button is NBG. It only appears to work if clients are DHCP.

Issue: ADSL link appears to go west occasionally but status indicates that DSL is OK. I found that unchecking the "Connect on Demand" and checking the "Keep Alive: Redial Period = 30 sec" seemed to do the trick.

Issue: Upgrading the firmware from 1.00.7 to 1.01.7 using Mozilla Firefox failed. I ran the upgrade process via the web interface and all was well with the progress bars appearing however when the progress bar was "complete" nothing happened for c. 15 seconds and then it started again, & again, etc. This happened about 10 x so I closed the browser after the completion of a progress bar and luckily the old firmware load was still OK (I didn't have a cabbage!). I then tried it again with IE6 and everything was OK - I got a completion acknowledgement page and when I next logged onto the router the firmware had indeed been updated. (incidentally I used a hard ethernet connection rather than wireless to do the upgrade.)

Jun 10, 2005

54G wireless LAN

Close ...
In case it is of interest this is my experience of setting up a wireless LAN using the following components -

Linksys WAG54G wireless ADSL/router/gateway

Linksys WGA54G-UK wireless game adaptor (Xbox)

Linksys WMP54G PCI nic

Belkin F5D7000 PCI nic

Apple Airport Extreme nic

I got all the Linksys stuff from which provided good service and delivery. All the devices conform to the Broadcom 54G chipset so I didn't have any real issues regarding compatibility.

Overall setup:

Basic setup is WAG54G on the ADSL connection using BT Openworld. The only problem with BT Openworld as I can see is that the IP allocation is dynamic (that is usual and no problem) but the DNS allocation and Gateway IP also changes dynamically which I think may be upsetting the Xbox when I try to fix the DNS in the Xbox settings (still working on this).

The wireless LAN has two XP clients (one has the WMP54 PCI card and the other a Belkin F5D7000 PCI card), a MacOS X client (Airport Extreme card) and an Xbox using the WGA54G-UK unit

Each client is running a static IP and the DNS server specified are BT's ( I cheat and use the BTI (Nband) ones - & 95)

128 bit WEP is implemented

At this stage I need to keep the DHCP running on the gateway for the Xbox. This allows the DNS for the XboxLive to still work. The Xbox and the WGA54G unit both have a static IP allocated which is also in the DHCP range. The static IP will allow ports to be forwarded to the Xbox without using a DMZ or compromising the other clients.


Quite a few changes on the network ....

A Netgear DG834G ADSL wireless router has replaced the WAG unit.

Latterly the XBox games adaptor doesn't get used so it is no longer a client.

A Thinkpad client running XP with SP2 has been added using an Intel PRO wireless 2200BG card. The ISP has also changed to V21 running 512K ADSL.

The Netgear router is a lot more stable on the wireless side of things and static IP allocation works just fine with the clients. Regarding security the 128 bit WEP is sufficient for a residential situation along with the use of MAC access tables (anyone sitting outside in a car with a laptop soon gets noticed!).

DNS is taken from the ISP with no real problems.

The only real hassle with V21 as an ISP was an issue, that took a week or two to resolve, that blocked access to a major UK bank - it is not clear but BT had their fingers in the pot somewhere!!!! Other than that the service outages have been un-noticeable.


The Netgear appeared to go flakey on the wireless LAN so a quick and dirty fix was to go out and get a Belkin G+ MIMO unit.

Tried using the WEP on the Belkin but the G4 Powerbook didn't like the 128 bit WEP (unsecure no WEP was OK) so set the LAN up for WPA with TKIP and worked OK. The Linksys WMP54G card in the P3 worked fine. The old Belkin F5D7000 wireless PCI card in the P4 wouldn't work (when connecting the PC would freeze) so I replaced it with a Belkin USB unit which installed OK but had marginal performance (this is 6 metres from the router via 2 walls and a staircase).

Enough I said and proceeded to spend the afternoon running in an ethernet cat 5e cable - needless to say the P4 now runs at a full 100MHz reliably, nothing like good ol' copper!

However it soon became apparent that the G4 Powerbook would not connect via wireless until the Thinkpad was connected and turned on so this was a problem.

No firmware updates were currently available for the Belkin so up a gum tree.

Shame about the Netgear but I need things to work and there is no way of testing these units satisfactorily to see if they are genuinely faulty.

It always seems to be the wireless portion of the routers which give doubt as the ethernet ports work fine all the time. In my mind wireless does a lot of sucking!

Sometimes I wonder if problems with the ADSL line connectivity actually impact on the wireless LAN although with good design it shouldn't.


The biggest hassle just occurred recently. Disconnection of my internet service occurred 15th November as a result of a financial disagreement between V21 (my ISP) and its sub-provider Netservices. The upshot of it all was that Netservices arranged for the ADSL service cease order to be placed as at 24th November and disconnection occurred on 1st December. So I am now with BT Broadband and have a shiny new (free) BT HomeHub to replace the dodgy Belkin G+ MIMO.

So far so good - on ADSL MAX (8 Meg) the BT HomeHub ( a Thomson unit) appears solid but a bit difficult to manage since it is set up for the mass market and pre-configured (getting about 5.6 Meg over 2.3 miles so far).

All the clients work OK on WEP128 (tried WPA but no go).

More on the BT HomeHub experience further up the page.

Mar 18, 2005

Javascript Error - Uncaught Exception

Close ...
The following error (using JS console) was encountered when using a mouseover function (NAV panel on the wanderinghippo web page) from a Mac.

Error: uncaught exception: [Exception... "Not enough arguments [nsIDOMWindowInternal.scroll]" nsresult: "0x80570001 (NS_ERROR_XPC_NOT_ENOUGH_ARGS)" location: "JS frame :: <unknown filename> :: onmouseover :: line 1" data: no]

Silly error really - the .js file that drives the NAV scrolling wasn't on the server.

This can also be caused with files that are in another subfolder and don't have a correct path (eg: javascript/whscroll.js specified rather than ../javascript/whscroll.js ).

Mar 18, 2005

javascript:open_window('wombat.html') broken

Close ...
With Firefox 1.0 and a few versions prior I had a problem with hyperlinks that would not open. This involved any link with using the "javascript:open_window("wombat.html")" function. I also found that FF intermittently wouldn't launch and this was due to the firefox.exe still running as a process despite the fact the app wasn't in use.

The source of the problem turned out to be a buggy extension (Open Java Console) - when this was disabled and the browser restarted the links worked fine. On closing the browser the firefox.exe closed down as it should also.

Although the Open Java Console extension was 0.6 I downloaded a 0.6.1 version and this worked fine (interestingly the "about" still shows 0.6 for the version)
Incidentally, quite a good site to test this is HERE (defunct)

122 Posts Displaying page 3 of 13
< >

Displaying page:

expander -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- -------- expander