Index Thing


The Hippo Techo Blog


119 Posts. Displaying page 4 of 12.
Previous Next

Go to page:

Hide All

Dec 16, 2006

Belkin G+ MIMO Wireless ADSL Router

Close ...
The Netgear DG834G seemingly went flakey so another router was the quick fix.

The depressing thing with wireless networks is that components don't die in the conventional sense in that a plume of black smoke indicates a terminal expiry or all the appropriate lights fail to shine. In the absence of such wonderful visual indicators of a problem software is the next step and sadly there is very little on the market that truly indicates the source of problems with the wireless connections. Most give cute little generic pictures of components and say there is a problem - wow as if I didn't know. Strange how it is possible to detect as many as 8 networks and not be able to connect to the local AP. The maximum range of operation is c. 10 to 20 metres.

Until the Netgear failed the network consisted of 2 PC's (XP SP1 & 2), 1 ThinkPad (XP SP2) & 1 Powerbook (OSX 10.4) using WEP 128 bit TCP/IP.

Using the Belkin G+ MIMO with WEP 128 bit -

The ThinkPad worked OK (Intel Pro/Wireless 2200BG)
The P3 PC worked OK (Linksys WMP54G)
The P4 PC failed (Belkin F5D7000)
The Powerbook failed (Airport Express)

The F5D7000 card failure was difficult to troubleshoot since when the new WEP settings were applied the PC just froze requiring a reboot. I put this down to the fact that even though it was a Belkin card working with a Belkin router the card was sourced in NZ so maybe a regional difference in software had an effect (notably - other cards from Intel and Linksys were fine).
The card in the P4 PC was replaced with an F5D9050 USB MIMO wireless card and worked well out of the box.

So only the Powerbook remained.
If the WEP was disabled and the network left open the Powerbook could connect OK but not with WEP.

The solution was to try WPA-PSK using TKIP on all machines and initially they all worked fine.

As outlined further up the page it became apparent that the G4 Powerbook would not connect via wireless until the Thinkpad was connected. This appeared to be yet another problem with "wireless" and unfortunately no firmware updates have been issued for the G+ MIMO router.

As above the USB G+ MIMO unit in the P4 whilst connecting OK was very marginal in performance so in went the 100% reliable copper.

Software - XP
Nov 10, 2006

XP Desktop Folder Settings

Close ...
One of the main things that has irked me about XP is the fact that folder windows opened from desktop icons do not retain the position and size parameters - everything is OK then you see that classic screen shimmer and the next time you open an icon the window settings have defaulted ( I tend to like having desktop folder icons for subject groupings a bit like the old Program Manager of 3.11 days eg: Development, Utilities, Webstuff, etc).

Well so far I think the answer has been a tweak to the registry involving the Bags key.




KB article 813711 explains the details - I set the Value to 5000 and so far it seems to work fine.

At this stage there has been no need to delete the keys (they apparently regenerate themselves) and restart windows - just making the changes as per the KB article has been sufficient.

I must say it was getting rather depressing having an OS that couldn't even remember fundamental settings for windows like position and size....

Software - XP
Nov 10, 2006

Frontpage 2003 Installer Issue

Close ...
When starting Acrobat 6.0 the Frontpage installer starts running (since FP 2003 is already installed this is a pain).
Bit of a saga once again when Microsoft is involved ..

Had a fossick around and found -

C:WindowsInstaller containing 4d22d.msi (this is the FP installer dated from the install of FP2003)

I renamed the file (x4d22d.msi) and then next time Acrobat was run I got an error where the FP installer couldn't locate FP11N.MSI

Did a search and located this file in -

N:MSOCacheAll Users90000409-6000-11D3-8CFE-0150048383C9 containing FP11N.MSI

Using Programs>Accessories>System Tools>Disk Cleanup I tried to clean out the MSOCache folder only to find that it got rid of everything except for the FP11N.MSI, SKU117.XML and some other sub folders - so much for the Disk Cleanup (typical CrapOS where stuff can be installed but never cleaned out). I tried the Disk Clean again but it indicated that the Office files were no longer there so the application thought it had done the job but in the real world nothing had really happened.

I renamed the MSOCache folder (xMSOCache) and still had the problem.

Where to from here then ..

Tried the great Microsoft pantheon of knowledge and found a utility called Windows Installer Clean Up Utility (wicuu2.exe). Well the knowledge base article stated caution when using this thing. It advised that the installed files for the application wouldn't be removed only the surplus install files and registry entries.
I installed and ran the utility only to find that FP 2003 had indeed been uninstalled - on a brighter note I no longer had the problem when starting Acrobat.
I think the concept of this utility is that it is only used to clean out Control Panel>Add&Remove Program remnants for previous applications that have not fully uninstalled.

So I installed FP2003 again and this time I said yes to deleting the surplus install files (the installer gives this option). However that would be too easy and of course the MSOCache folder was still there and of course the installer was in the WindowsInstaller folder as well (now called 3b7ad9.msi ) - of course the problem with the Acrobat interaction resurfaced again.

What was weird is that as I was trying the renaming technique on the 3b7ad9.msi file again when I started up Acrobat the FP CD (which I had left in the drive) actually started spinning and then Acrobat launched with no problem. Ever since everything is OK but why I don't know.

It seems the MSOCache folder is created by Office 2003 as a Local Install feature for future repair/re-install of components without requiring the CD and indeed FP2003 did exactly this. However since I still use Office 97 and the only 2003 app I use is FP then maybe the System Tools Disk Clean couldn't handle this (expecting other Office 2003 files/cabs to delete?).

So in summary the MSOCache folder (which in my case is on the N: drive) could not be deleted using the MS recommendations and since they say in BOLD letters not to use Windows Explorer to do it what was a humble user to do .......?

.....I used Windows Explorer to rename the folder (xMSOCache) and after a week with no problems dispatched it into the dustbin of technocracy ....

Another encounter with the "Daddy knows best" regime of MS & XP.

Software - Apps
Nov 06, 2006

HTMLGate application triggers Office 2000 installation process on startup

Close ...
On startup the Office 2000 installation appears and gives -

The feature you are trying to use is on a CD-ROM or other removable disk that is not available.

Insert the 'Microsoft Office 2000 SR-1 Professional' disk and click OK.

If the Office 2000 CD was installed the following error was encountered -

Error 1305. Error reading from file:
Verify that the file exists and that you can access it.

The problem was that the HTMLGate app required the HTML Source Editing tool from the Office 2000 suite. This tool was set as install on first use and HTMLGate was obviously the first app on my PC to require this.

The 2nd problem with error 1305 was a bad block on the Office 2000 CDROM so once the Office files were copied to the C: drive and the faulty DLL found elsewhere the Office install proceeded and fixed the issue with HTMLGate on startup.

The XP system and application error logs were useful in showing the bad block issue and the HTML Source Editing calls.

Software - Apps
Nov 06, 2006

Using SyncBack application with DVD-RAM for backup

Close ...
The freeware version of SyncBack is excellent for doing incremental backups and synchronising files/folders.
Initially however I had difficulty getting it to work with my DVD-RAM recorder.

Recorder: LG 4120B (HL-DT-ST DVDRAM GSA-4120B)

Media: Panasonic 4.7G DVD-RAM

OS: XP Pro SP1

Usefully XP will support DVD-RAM as installed however the support is limited.
The MS driver appears to use a version of the MEIUDF.SYS driver which allows read/write in FAT32 format but only read in UDF format.

Using SyncBack with the MS driver didn't work since the SyncBack application requires UDF devices and the XP driver will only write with FAT32.

Luckily I found an LG driver that improves things a bit.

I just ran the setup.exe and the PC needed to reset but afterwards the SyncBack app worked fine


LG = Lucky Goldstar (Korean manufacturer)
MEI = Matsushita Electrical Industries (Panasonic is a brand along with Technics and others)
UDF = Universal Disk Format (types 1.5 and 2.0)
HL-DT-ST = Hitachi LG Data Storage

Location of LG driver:
Details of MS support:

Nov 06, 2006

W3C Schema for HTMLPad 2006

Close ...
How the intellisense seems to work-
A document is opened and the tag completion list uses the appropriate .ini file in the datamldefs folder. The decision on which file to use is done on the Doctype in the page (if enabled in the options).
eg: If an XHTML 1.1 page is opened then the list will derive from datamldefsXHTML 1.1.ini
If the Doctype is not checked then the list will be dependent on the language specifications selected in the options.

It is to be noted that HTMLPad has only an XHTML 1.0.ini file which bunches the Frameset/Transitional/Strict variations together.
This file also includes the Ruby tags which only appeared in the XHTML 1.1 standard.

To improve this separate ini files for the XHTML 1.0 variants can be used however to be able to select varying ini files the "Use Doctype to switch specification" should not be checked.

Base file used was XHTML 1.1.ini
Location: C:\Program Files\HTMLPad 2006\data\mldefs\

Original W3C file used was xhtml1-strict.xsd


Cut and Paste using the W3C file as original reference.
The xhtml 1.0.ini file supplied is actually a composite of Strict/Transitional/Frameset.
xml:lang is not catered for and also is not in the 1.1 file at all!

File tips:
name,d=<string> ( ,d indicates the attribute as deprecated)
%endtag=0 ( 0 indicates an empty element, shows as green in Auto tag lists)
action,r=<url> ( ,r indicates a required attribute)

Modified XHTML 1.0 Strict file HERE (rename as XHTML 1.0 Strict.ini)

Modified XHTML 1.0 Transitional file HERE (rename as XHTML 1.0 Transitional.ini)

Modified XHTML 1.0 Frameset file HERE (rename as XHTML 1.0 Frameset.ini)

Template Locations

C:\Program Files\HTMLPad 2006\templates\HTML\

Related usage notes:

Adding custom schema.

Markup browser uses markup.dat ( View>Markup Browser )
HTML Language specification uses html.dat ( Options>Preferences>Language Options )

markup.dat (as installed)
HTML 4.01
WML 1.1

html.dat (as installed)
HTML 4.01

The files specified (except for DEDI) all relate to the as named files in the mldefs folder. There is no file for DEDI.
Maybe DEDI is short for dedicated and is meant for custom schema - I don't know...

Files can be added to both files and will then be shown as options in the appropriate places.


markup.dat (as modded) html.dat (as modded)
HTML 4.01 HTML 4.01
DEDI XHTML 1.0 Strict
XHTML 1.0 Strict XHTML 1.0 Transitional
XHTML 1.0 Transitional XHTML 1.0 Frameset
XHTML 1.0 Frameset

If the Markup Browser is used and say XHTML 1.0 Strict is selected the tag list will only appear if the same option is selected in the language options. However if any of the default files are selected the tag lists will appear anyway.
If after selecting a custom file another file is then chosen in the markup list the tag list will only show if the file chosen is one of the default ones. If the original custom file is re-selected then the tag list will not appear until the language option
is reapplied for that file.

If the DEDI entry is removed from both dat files the situation remains the same.

It was noticed also that if say the WML 1.1 entry in the markup.dat file was replaced with a custom file then the Markup Browser would still show the tag list for the WML 1.1 file.

It seems that the default file names are written somewhere else as a hard coded reference....

Nov 06, 2006

CSS hover box truncated top with Opera 9.x

Close ...
Problem: A CSS hover span is used within a content div which is inside
an outershell div. Outside the outershell div the hover span box works fine
but inside the hover box is truncated at the top. Opera 8.52 renders the hover
ok as do most other browsers (IE, Mozilla, etc).

Basically to fix the issue I had to alter the outershell top: from 25px to 0px
and the content div top; of 2px was changed to margin-top: 22px;

An example of the problem is shown - HERE

This is how the hover renders after the CSS is tweaked - HERE

Nov 06, 2006

XHTML 1.0 MIME type issue

Close ...
This site is designed for XHTML compatibility but really it is just a load of bollocks because of the following situation with XHTML User Agent compatibility.
Basically true XHTML is not supported by any of the IE browsers (which at the moment constitute the majority of browsers in use).
More about this can be found at

With wanderinghippo although the meta tag is set as application/xhtml & xml the mime type sent from the server(which takes precedence with the UA) is actually text/html as is the case with many other XHTML 1.0 sites. This means the UA will not handle the page in a pure XHTML form.

Why then bother with XHTML 1.0 for the hippo?
You may well ask but I like the challenge of creating a compliant page according to the fiendish standards which in reality aren't that bad - just a shame that IE won't support them.

Update: Use of Content Negotiation

So, IE (along with other browsers) won’t support XHTML if the mime type is served as application/xhtml+xml however
by implementing server side Content Negotiation the issue can be worked around to a point.
If the .xhtml extension is used (at least on Apache servers) the mime type served will be application/xhtml+xml.
The method I have tried on my XAMPP dev server and production server (host using Apache) is to add suitable scripting to the .htaccess file.

ADD following to .htaccess file -

# requires mod_headers module on server
Header append Vary Accept

# requires mod_rewrite module on server
RewriteEngine on
RewriteCond %{HTTP_ACCEPT} !application/xhtml+xml
RewriteRule .* - "[T=text/html; charset=UTF-8]"

Note: I used to use the Abyss web server for dev but found that at this time the .htaccess file is not supported so I changed to the XAMPP web server for dev.

The two required modules for the .htaccess file were uncommented in httpd.conf file and the XAMPP server restarted.

Nov 06, 2006

XHTML Myths and Legends - some answers!

Close ...
1 The target attribute has never been included in Strict versions of HTML 4.01, XHTML 1.0 and XHTML 1.1 - it exists in HTML 4.01 Frameset/Transitional and XHTML 1.0 Frameset/Transitional

2 XHTML 1.0 Strict allows both xml:lang and lang with xml:lang taking precedence. XHTML 1.1 allows only xml:lang

3 The name attribute of the <a>, <map> and <form> tags is deprecated in XHTML 1.0 Strict and removed in XHTML 1.1 in favour of the id attribute

4 The name attribute of the <img> tag is removed in XHTML 1.0 Strict but exists in 1.0 Frameset/Transitional

5 The <iframe> tag is not included in XHTML 1.0 Strict

6 The name attribute of the <applet>, <form>, <frame>, <iframe> and <img> tags is deprecated in XHTML 1.0 Frameset/Transitional

7 The <ruby>, <rbc>, <rtc>, <rb>, <rt> and <rp> tags were introduced with XHTML 1.1

8 The following deprecated tags were excluded in XHTML 1.0 -
<applet>, <basefont>, <center>, <dir>, <font>, <frame>, <frameset>, <isindex>, <menu>, <noframes>, <s>, <strike>, <u>

9 Empty elements such as <br /> and <hr /> or <img src="image.jpg" alt="picture" /> are usually typed as such with a space preceding the slash to allow compatibility for older browsers.

10 XHTML 1.0 content presentation should normally be set as "application/xhtml+xml" in the META tag rather than "text/html" (allowed with XHTML 1.0) however if this is the case then IE will not process the content correctly (not supported). Since most XHTML 1.0 pages are presented as .html files rather than .xhtml files the servers normally present the content as "text/html" and so IE will work but not in strict XHTML mode.
11 <!-- and --> traditionally used for comments are still valid outside tags but the content will be ignored by some XML parsers.
Using these tags within script or style tags however should no longer be implemented because XML parsers will parse these tags including any unescaped XML characters - <![CDATA[ and ]]> should be used within these tags.

12 If XHTML is served as text/html background styling on the BODY tag will affect the whole window(including the HTML tag) but if served as application/xhtml+xml then only the BODY tag is affected. If offsets are used with the BODY tag the window will only be fully affected if the HTML tag is styled.

13 The apostrophe character - &apos; was introduced by XML 1.0 so &#39; may be required for earlier HTML browsers.

14 If XHTML is served as application/xhtml+xml then a javascript document.write() will not work because the XML parser is being used.

Nov 06, 2006

Adding Macro for XHTML 1.0 Validation to Expression Web Designer

Close ...
The macro facility in EWD can be used to provide XHTML validation in a similar manner to that described for FP at Michael Suodenjoki's site - HERE
( cle.htm)
I found this method can also be used in FP2003

A few tweaks are required for the script to be used in EWD. Please bear in mind that I have used EWD CTP1 and Beta 1 so things may be different on retail releases when they happen.

UPDATE: Still works OK with EW Trial version (which I think may be a RC) and final release version also.


Fairly similar to section 3.2 of Michael's article
The validate.bas file can be tweaked with notepad or within the VBA editor.

Tools>Macro>Visual Basic Editor
VBA editor will open (different to screenshot)

View>Project Explorer
This will show Module1 which can be deleted

File>Import File
ExecuteCmd.bas (still works OK without tweaks)
Validate.bas (requires some tweaks)
Form_output.frm (OK as is)

These should now show in the Project Explorer
Close the VBA editor and use EW to complete the install of the macro.

Steps 7 to 17 of Michael's instructions are pretty well still OK for EW.

Tweaks for validate.bas

Line 35: MsgBox "Please open a file in the Expression Web Designer.", _
Line 40: If Not ActivePageWindow.ViewMode = PageViewNormal Then
Line 42: ActivePageWindow.ViewMode = PageViewNormal
Line 45: Dim doc As IHTMLDocument
Line 96: ActivePageWindow.ViewMode = PageViewHtml

Note: It can be convenient to tweak the validate.bas file before the import so a master record is kept since the app uses its own macro file once the import is done.

Macro location:
EWD Trial
C:Documents and SettingsuserApplication DataMicrosoftExpressionWeb DesignerMacros Microsoft Expression Web.wdmacro

EWD CTP1 and Beta1
C:Documents and SettingsuserApplication DataMicrosoftExpressionWeb DesignerMacros Microsoft Expression Web Designer.wdmacro

C:Documents and SettingsuserApplication DataMicrosoftFrontPageMacrosMicrosoft Frontpage.fpm

Typical output on a "clean" XHTML 1.0 page was -

C:BMCDataStuffBMCWebValidationbinnsgmls.exe: C:BMCDataStuffBMCWebValidationpubtextxhtml1.dcl:31:27:W: characters in the document character set with numbers exceeding 65535 not supported
(Above line always appeared - just never worried about it too much)

C:BMCDataStuffBMCWebValidationbinnsgmls.exe: C:BMCDataStuffBMCWebValidationinput.tmp:10:9:E: character data is not allowed here
C:BMCDataStuffBMCWebValidationbinnsgmls.exe: C:BMCDataStuffBMCWebValidationinput.tmp:25:9:E: character data is not allowed here
(Lines above relate to and being in the user page)

119 Posts. Displaying page 4 of 12.
Previous Next

Go to page: