Skolob Matrix - Since 1996
http://www.skolob.co.uk/skolob/index.php?blogId=1
<p>Welcome to the Skolob Matrix. This is place on the web that has been long forgotten.</p>
skolob2011-12-21T12:05:04ZGeneral : www.eflight.com.au
http://www.skolob.co.uk/skolob/index.php?op=ViewArticle&articleId=8&blogId=1
<p>
If you are interested in flights, car hire or hotels then please consider checking out <a href="http://www.eflight.com.au" title="Eflight booking agent">EFlight</a>. They are based in Australia and are run by qualified travel agents, im just giving them a plug cuz of the great service they gave me!
</p>General2008-05-27T14:41:27ZskolobGeneral : Vodafone Australia GPRS WAP Mobile Internet Settings
http://www.skolob.co.uk/skolob/index.php?op=ViewArticle&articleId=7&blogId=1
<p><a id="res_8" href="http://www.skolob.co.uk/skolob/gallery/1/logo_vodafone2.gif"><img src="http://www.skolob.co.uk/skolob/gallery/1/logo_vodafone2.gif" border="0" alt="Vodafone" title="Vodafone" hspace="5" vspace="5" align="left" /></a><strong>Vodafone Australia GPRS Settings<br /><br /></strong>Here are the hard to find GPRS settings for Vodafone Australia. Unfortuantly you cant just put in the APN address in some phones like the Motorola RAZR V3... </p><p>Homepage : http://live.vodafone.com<br />Service Type : WAP<br />Gateway : 10.202.2.60<br />Port : 9201<br />GPRS APN : live.vodafone.com</p><p> <strong>Vodafone Australia GPRS Settings<br /><br /></strong>Here are the hard to
find GPRS settings for Vodafone Australia. Unfortuantly you cant just
put in the APN address in some phones like the Motorola RAZR V3... Homepage : http://live.vodafone.com<br />Service Type : WAP<br />Gateway : 10.202.2.60<br />Port : 9201<br />GPRS APN : live.vodafone.com</p><p><strong>Here are the comlpete settings from my old Motorola V3 mobile :</strong></p><p>Name : Vodafone WAP<br />Homepage : http://live.vodafone.com<br /> Service Type 1 : WAP<br />Gateway IP 1 : 010.202.002.060<br />Port : 9201<br />Domain 1 :<br />Service Type 2 : WAP<br />Gateway IP 2 : 000.000.000.000<br />Domain 2 :<br />DNS 1 : 000.000.000.000<br />DNS 2 : 000.000.000.000 <br />Timeout : 5 minutes (remember you are charged in 5min blocks!)<br />CSD No. 1 :<br />User Name 1 :<br />Password 1 :<br />Speed (Bps) 1 : 9600<br />Line Type 1 : Modem<br />CSD No. 2 :<br />User Name 2 :<br />Password 2 :<br />Speed (Bps) 2 : 9600<br />Line Type 2 : Modem<br />GPRS APN : live.vodafone.com<br />User Name :<br />Password :<br /> </p><p> </p>General2007-11-15T14:27:47ZskolobWindows Programming : Visual Basic 6 ( vb6 / vb classic ) Compile Make EXE Button Disabled.
http://www.skolob.co.uk/skolob/index.php?op=ViewArticle&articleId=6&blogId=1
<p><a id="res_7" href="http://www.skolob.co.uk/skolob/gallery/1/7-vb6.gif"><img src="http://www.skolob.co.uk/skolob/gallery/1/previews/7-vb6.gif" border="0" alt="Visual Basic 6" /></a></p><p>One of the most annoying problems that can repeatly occur when using VB6 over a prolonged period on some machines is that the make .exe compile make EXE button to become disabled and greyed out.</p><p>To fix this goto <strong>Toolbars</strong> > <strong>Customize</strong>. Then press the <strong>RESET</strong> button.</p><p> </p>Programming2007-10-11T13:22:20ZskolobWindows Programming : OLE Automation (Guide)
http://www.skolob.co.uk/skolob/index.php?op=ViewArticle&articleId=5&blogId=1
<p><span style="font-family: Verdana,Arial,Helvetica,sans-serif"><strong>OLE AUTOMATION<br />
(December 1998) </strong></span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"><strong>SUMMARY</strong> </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> The purpose of this report is to determine the problems associated with implementing Object Linking and Embedding (OLE) Automation features into a software product, giving the reader an introduction to OLE Automation. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> Common OLE Automation implementation problems are first discussed with examples of each given. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> Solutions to these implementation problems are then explored and analyzed. </span></p>
<p> <span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"><strong>CONCLUSIONS</strong> </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> OLE Automation is a feature that allows common users to write simple programs that control larger, third-party applications that support OLE Automation. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> A variety of problems can occur with the implementation of OLE Automation in an application, starting at a high-level and eventually infesting the entire application. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> Practical solutions to these implementation problems include better developer education about OLE Automation and more efficient planning on how to implement OLE Automation. </span></p>
<p> <span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"><strong>RECOMMENDATIONS</strong> </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> An effective implementation of OLE Automation begins before any code is actually written, when programmers should be educated as to how OLE Automation works and have input as to how it will be implemented in the project. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> In the actual development stage the developers should share the work of applying OLE Automation with one person leading the group instead of all of OLE Automation being lumped to one person. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> Another efficient development step is to have the developers use methods common to all code for OLE Automation, thus reducing code maintenance and bug potential. </span></p>
<p> <span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> <strong>INTRODUCTION</strong> </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> In the computer industry today applications exist for almost every conceivable user need. However, if a user wanted to use parts of one application in another (ie. use a graph created in a spreadsheet in a word processing package) then until 1992 this could not be done. It was at this time that Microsoft created the Object Linking and Embedding (OLE) stream of programming functions that allowed programmers to create applications for users that allowed one large document to consist of a variety of smaller documents, each created in a different application. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> A subset of the OLE concept was known as OLE Automation. In short, OLE Automation allows program developers to expose certain program components (or objects) so that these can be manipulated by Visual Basic users to create large custom applications that consist of a variety of smaller, third-party applications (each of which is accessed via these exposed objects). This definition becomes clearer through an example: Consider a person with not alot of programming experience who needs to create a small application that with one mouse button click will launch a word processor and with another mouse button click will launch a spreadsheet application. Before OLE Automation this task would have required a great deal of programming time and effort; but because of OLE Automation this task is greatly simplified, as only ten lines of code will accomplish the desired task. Although this may not appeal to the casual user, this simplicity is attractive to many large corporations who need customizable applications. These corportations have been the major market that OLE Automation has catered to. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> OLE Automation also requires very little programming maintenance over the years, as the object names that are exposed by the original application developer will rarely change; implying that a program written using Word 6 and Excel 4 in 1993 will work with Word 7 and Excel 6 in 1996 just as well. </span></p>
<p> <span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> <strong>Problems with Implementing OLE Automation </strong> </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> From the introduction one may have the view that OLE Automation has no disadvantages and is a big step in the world of programming. However, exposing the objects in the original application can be quite a time consuming and inefficient process if done incorrectly, and many software corporations fall into this inefficiency trap because OLE Automation is so new they do not know how to apply it effectively. The purpose of this section is to examine these traps. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> In the software design industry it is common practice for a members of a development team to each be assigned separate features of a product. Unfortunately, as a result OLE Automation is usually given as an entire task to one individual. This has several ramifications, all of which combine to give an unsatisfactory implementation of OLE Automation. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> The problems start in the design of how OLE Automation will be implemented. Because one person has to design OLE Automation, naturally they determine which features of the application will be exposed and how the user will manipulate them. This can create problems because the Automation team member will be exposing objects that were designed by other people, and thus may end up making certain objects more difficult for a user to access than others. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> For instance, if one team member is working of a line utility for an application, they will usually have little or no input as to which line features will be made available or how these features will be made available. Thus the OLE Automation team member may plan to expose the line length and line width; when in fact the two most important line properties to expose are the lines color and number of nodes. As one can see, an error has already appeared in OLE Automation in the high-level design phase. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> Besides the aforementioned high-level design error, the low-level implementation of OLE Automation is usually inefficient and hard to maintain. This again stems from the division of labor within the project, as each developer will program their section without OLE Automation in mind and thus make the job of exposing objects that much more difficult. By using object-oriented software design concepts, this is because each individual developer does not use methods that are friendly towards the exposing of objects, and thus these methods must be rewritten by the OLE Automation engineer so that each object can be properly exposed. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> For instance, using the line tool example again, if one wants to expose a line object for automating, the easiest and most efficient way to do this would be to call a function actually used by the line tool to draw the line. This way, the method to call already exists in the application, so no extra code needs to be written to expose the line object. However, this scenario is usually impossible to replicate in reality because said function almost never exists in the application; the only functions used by the line developer are functions that help the line tool work, not ones that help OLE Automation work. Usually, the only way that the line object could be exposed is to copy bits and pieces from the line tool code, a method that is both inefficient (because very little object-oriented techniques are being used) and hard to maintain (as every time the line implementation changes, code changes are required in both the line code AND in the OLE Automation code as well). </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> The possible flaws of OLE Automation are now evident in both its high- level design phase and low-level implementation. </span></p>
<p> <span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> <strong>Solutions to these Problems</strong> </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> In the previous section problems with OLE Automation were examined in both high-level and low-level contexts. This section will address these problems, providing solutions that will enable a more efficient implementation of OLE Automation. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> There are two solutions available for the high-level OLE Automation problems: plan OLE Automation implementation in advance, and divide up the workload of OLE Automation as to not lump it all on one person. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> Planning OLE Automation in advance means that in the early stages of the project, all team members should be educated as to what OLE Automation is and how it works. This education is necessary because many software developers consider implementing OLE Automation a very difficult task when in fact it can be quite simple if planned correctly. After this education the team members should discuss how OLE Automation can be most easily implemented and who on the team is most qualified (or most willing) to coordinate the implementation. Also in this planning stage the team members should decide which OLE Automation objects to expose and how to expose them. This should be done in order to make OLE Automation easier for the end user to use, and to also make all team members aware of how detailed OLE Automation will be. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> After the planning stage, the chosen OLE Automation leader should divide up the task of Automation between the various team members. Ideally, the leader should still be responsible for about 80-90 per-cent of the actual implementation; the remaining 10-20 per-cent should be assigned so that some of the more complicated Automation routines could be programmed by the people who designed the objects they are meant to expose (eg. the line guru would program the Automation line object ). Another advantage of this is that the individual programmers will keep in mind the needs of the OLE engineer when designing their own sections. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> By now the high-level implementation of OLE should be complete. All that remains is actually writing the code which, as pointed out earlier, is error-prone as well. Besides dividing up the programming tasks (as mentioned before) another solution to inefficient low-level implementation of OLE Automation is to use object-oriented design methodologies to create common functions that are used by both the actual tool to be exposed and by the Automation function that exposes it. For example, if the line tool is being Automated it would be ideal if there was a function in the actual line tool code that does most (if not all) of what the Automation code needs to accomplish. This obviously results in a lot less Automation code, implying a more efficient and maintenance free low-level implementation of OLE Automation. </span></p>
<p><span style="font-size: x-small; font-family: Verdana,Arial,Helvetica,sans-serif"> By using both these high-level and low-level techniques the myth that OLE Automation is hard to design and program should be shattered as a maintainable, efficient, and well planned OLE Automation implementation should result.</span></p>Programming2007-09-17T15:35:46ZskolobPalmtop PC's - HP 95LX, 100LX, 200LX - Three Poems Hidden Easter Eggs
http://www.skolob.co.uk/skolob/index.php?op=ViewArticle&articleId=3&blogId=1
<p><a id="res_1" href="http://www.skolob.co.uk/skolob/resserver.php?blogId=1&resource=hp95lx.jpg"><img src="http://www.skolob.co.uk/skolob/resserver.php?blogId=1&resource=hp95lx.jpg&mode=preview" border="0" hspace="20" vspace="5" align="top" /></a> </p><p align="left"> <em>Easter Eggs hidden sections for Hewlett Packard 95LX, 100LX and 200LX!!! (Should also apply to the 1000CX - Ill test when I have time!) </em></p><p> </p><div class="instructions" style="margin-top: 10px"> <div class="instrbreak"><img src="http://www.skolob.co.uk/skolob/resserver.php?blogId=1&resource=hp95lx.jpg" border="0" /> <br /></div><div class="instrbreak"> </div><div class="instrbreak">With the palmtop off, hold down [Esc] and press [On]. The palmtop enters its ROM-based self-test mode. (Warning! Do NOT run the Plug-in Card test on a flash card - it will destroy data! This test is meant for older SRAM cards only!) </div><div class="instrbreak">Cursor down to the Display test, then...</div><div class="instrbreak"> </div><div class="instrbreak"> </div><div class="instrbreak">For HP 95LX, 100LX and 200LX: </div><div class="instrbreak">Press [Enter] 14 times to step through the display modes, and you will see a limerick about a caveman.</div><div class="instrbreak"> </div><div class="instrbreak"> </div><div class="instrbreak">For 100LX and 200LX: </div><div class="instrbreak">Press [Ctrl]+[Enter], then hold down [Alt] while pressing [Enter] 13 times. You will see a cryptic poem, presumably about troubles the HP developers went through.</div><div class="instrbreak"> </div><div class="instrbreak"> </div><div class="instrbreak">For 200LX: </div><div class="instrbreak">Press [Ctrl]+[Enter], then hold down [Shift] while pressing [Enter] 13 times. You will see a poem about Jaguar<a class="kLink" id="KonaLink1" href="http://www.eeggs.com/items/14253.html#" target="_top"><span style="font-weight: 400; font-size: 14px; position: static; font-family: arial,sans-serif; color: blue"><span style="font-weight: 400; font-size: 14px; position: static; font-family: arial,sans-serif; color: blue"></span></span></a>, Cougar and Felix (the codenames for the 95LX, 100LX and 200LX). </div> </div>Palmtop PC2007-03-14T12:16:13ZskolobPalmtop PC's - Skolob's Hewlett Packard 95LX Palmtop
http://www.skolob.co.uk/skolob/index.php?op=ViewArticle&articleId=2&blogId=1
<p><a id="res_1" href="http://www.skolob.co.uk/skolob/resserver.php?blogId=1&resource=hp95lx.jpg"><img src="http://www.skolob.co.uk/skolob/resserver.php?blogId=1&resource=hp95lx.jpg&mode=preview" border="0" hspace="20" vspace="5" align="left" /></a> </p>
<p>The little compact HP 95LX released in 1991 weighed in at a tiny 11 ounces, the device also only occupied the space of two chequebooks glued back to back (6.3 in x 3.4 in x 1 in) and could run on on two AA batteries for up a month! This made it one excellent portable device and MS-DOS computer for use on the run, today it is highly collectable!</p><p>I have written up my own modern day FAQ with information I have gained on this device over the years. Ive compiled information on on serial port pin outs, hidden features, battery saving tips, important keys, avoiding the dreaded hinge crack, infrared transfer information and much more.</p><p>Also included is hidden easter egg information for the 95LX, 100LX and 200LX devices. </p>
<p><span style="font-size: 18px; line-height: normal">Skolob's <strong>Hewlett Packard 95LX</strong> Palmtop Page</span></p>
<h4><img src="http://www.skolob.co.uk/skolob/gallery/1/4-hp95lx.JPG" border="0" alt="Photo of my HP 95LX" /><br />
<br />
<strong>Copyright (c) 2005 - 2007 SKOLOB.CO.UK by Vauxhall.</strong><br />
May not be reproduced or copied without permission.<br />
Revision : 14/Mar/2007</h4><p>The 95LX has a 8086-compatible MS-DOS computer with either 512k or 1Meg of memory. </p><p>
<strong>History of the HP 95LX computer</strong><br />
The history of the HP 95LX handheld computer is available from HP at : <a class="postlink" href="http://www.hp.com/hpinfo/abouthp/histnfacts/museum/personalsystems/0025/index.html" target="_blank">http://www.hp.com/hpinfo/abouthp/histnfacts/museum/personalsystems/0025/index.html</a></p><p> </p><p><strong>Production Dates</strong><br />The device was introduced on the 23th April 1991 for US$699 until 1st January 2003. There was an estimated production run of about 400,000 devices.</p><p> </p><p><strong>Keystroke Commands</strong><br />
Useful keystroke commands in the 95lx available anywhere in the system :
</p><a class="postlink" href="http://www.hp.com/hpinfo/abouthp/histnfacts/museum/personalsystems/0025/index.html" target="_blank"></a><table align="center" border="0" cellpadding="3" cellspacing="1" width="500">
<tbody>
<tr>
<td><strong>Quote:</strong></td>
</tr>
<tr>
<td>[CTRL]+[ALT]+[DELETE] - Reset Device <br />
[CTRL]+[SHIFT]+[ON] - Initialise RAM Disk <br />
[SHIFT]-[SETUP] - System Setup (only available from menu)</td>
</tr>
</tbody>
</table><p> </p><p>
<strong>How do I access MS-DOS?</strong><br />
Select [Filer] from menu, then [Menu] Key and then press [S]. The system will now be in full MS-DOS mode, the version of DOS. To return to Filer type in EXIT at the DOS prompt then press [Enter] key. </p><p>
All the usual DOS commands can be used - heres a small sample :</p><table align="center" border="0" cellpadding="3" cellspacing="1" width="500">
<tbody>
<tr>
<td><strong>Quote:</strong></td>
</tr>
<tr>
<td>DIR - List files <br />
DIR /P - List files a page at a time. <br />
VER - Display current DOS version <br />
EXIT - Exit DOS</td>
</tr>
</tbody>
</table><p> </p><p><strong>Reducing battery consumption</strong><br />
It is a known fact that the 95lx can effectively keep the serial port 'open' even if it is not in use. This can slightly increase the drain on the batteries. To prevent this drain goto DOS and type in :
</p><strong></strong><table align="center" border="0" cellpadding="3" cellspacing="1" width="500">
<tbody>
<tr>
<td><strong>Quote:</strong></td>
</tr>
<tr>
<td>SERCTL /O</td>
</tr>
</tbody>
</table><p>
See topic below for turning serial port back on for when its needed!</p><p> </p><p><strong>Full syntax of the SERCTL command</strong><br />
SERCTL is a command in DOS that allows turning on/off of serial/infrared services. <br />
<br />
</p><strong></strong><table align="center" border="0" cellpadding="3" cellspacing="1" width="500">
<tbody>
<tr>
<td width="574"><strong>Quote:</strong></td>
</tr>
<tr>
<td>SERCTL /O Turns off the power to the active port. <br />
SERCTL /W Turn serial port on <br />
SERCTL /I Turns infrared port on. </td>
</tr>
</tbody>
</table><p> </p><p>
<strong>Full syntax of the DISPCTL command</strong><br />
DISPCTL is a command in DOS that allows turning on/off cursor tracking/alt arrow key movement. <br />
<br />
Due to small size of 95lx screen not all screen data can usually be viewed at once. Cursor tracking attempts to automatically adjust the screen to show the 'active' part. It can be a problem with some programmes, therefore it can be turned off and on using the DISPCTL command. The DISPCTL command can also enable or disable the ATL-Arrowkey screen movement command on or off.<br />
<br />
</p><table align="center" border="0" cellpadding="3" cellspacing="1" width="500">
<tbody>
<tr>
<td><strong>Quote:</strong></td>
</tr>
<tr>
<td>DISPCTL +C Cursor tracking on <br />
DISPCTL -C Cursor tracking off <br />
DISPCTL +K ALT+Arrowkey screen movement on <br />
DISPCTL -K ALT+Arrowkey screen movement of</td>
</tr>
</tbody>
</table>
<p><br />
<strong>System Self Test</strong><br />
There is a built in system self test system for testing display, RAM, ROM, Plugin Card, Timers, Infrared, Serial port and Keyboard. To access the Self Test menu, insure the device is off then press [ESC]+[ON], then a menu will appear! WARNING! Plugin card test may destory any data on cards plugged in! <br />
</p><p> </p><p><strong>Avoiding the common HP palmtop hinge crack!</strong><br />
Although hinge cracks are far more common on later 200lx models due to the tightness of the hinge you should always treat the 95lx with care. Shut the device from the right hand side because this is where the hinge mechanism is. When shutting from the right, ensure you are not just holding the top edges of the device while shutting as this puts the maximum pressure on the hinge. The lower down and closer to the hinge you use your hands to shut the device the better.<br />
<br />
<strong></strong></p><p><strong>How do I know if I have the dreaded hinge crack?</strong><br />
With the device shut, sitting in front of you. Look in the right edge corner of the case, for any lines near the join of the top panel with the rounded hinge! It may look like a scratch, but it is more than likely to be a hairline hinge crack. If you have this crack, open and shut the device carefully - as otherwise eventually the hinge will completely snap. <br />
<br />
<strong></strong></p><p><strong>Serial Cable pinouts for 95LX</strong><br />
The serial cable pin outs for the HP48 calculator which according to a number of references on the internet is the same as the 95lx pinouts. (I cannot 100% confirm this fact, so please use these details at your own risk.)</p>
<table align="center" border="0" cellpadding="3" cellspacing="1" height="0" width="500">
<tbody>
<tr> </tr>
<tr>
<td><pre><span style="font-size: x-small; font-family: courier new,courier"><strong>HP48</strong> | <strong>RS232-9</strong> | <strong>RS232-25</strong><br />-----+---------+----------<br /> 1 | shield | shield<br /> 2 | 2 | 3<br /> 3 | 3 | 2<br /> 4 | 5 | 7</span></pre></td>
</tr>
</tbody>
</table>
<p> </p><p><strong>Transfering files to HP 95LX using Infrared using a iPAQ Pocket PC</strong><br />One method of transfering files to and from the device is via the Infrared beam. The Infrared beam uses the HP SIR protocol and is generally incompatible with most Windows 98/XP infrared devices. A simple simple alternative I found was using an old iPAQ Pocket PC and using a HPSIR compatible file transfer programme to send the data across. </p>
<p> </p><p><strong>Games for the 95LX : Hidden TigerFox Game</strong><br />
A game called TigerFox is included on the 95lx, (may not be available on all versions!), it can be accessed by entering the command TF in DOS. </p>
<p> </p><p><strong>Games for the 95LX : Tetlix Tetris Clone Game</strong></p>
<table align="center" border="0" cellpadding="3" cellspacing="1" width="500">
<tbody>
<tr> </tr>
<tr>
<td><p> </p>
<span style="font-size: x-small; font-family: courier new,courier"> █▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒█<br />
Level 0 / 1 █▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒█<br />
█▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒█<br />
Score 158 █▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒█<br />
█▒▒▒▒▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒█<br />
█▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒█<br />
TETLIX █▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒█<br />
Right = --> █▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒█<br />
Left = <-- █▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒█<br />
Drop = ↓ █▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒█<br />
Rotate= F1 █▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒█<br />
Pause = F2 █▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒█<br />
█▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒█<br />
█▒▒▒▒▒▒▒▒ ▒▒▒▒▒▒▒▒▒█<br />
█▒▒▒▒▒ ▒▒▒ ▒▒▒▒█<br />
█ ▒▒▒▒█</span><br /></td>
</tr>
</tbody>
</table><p>
<br />
A tetris clone for fans of this type of puzzle games. This can be downloaded from our web server <a href="http://www.skolob.co.uk/3rdparty/files/hplx95/tetlix.zip">here</a>.</p><div class="instrbreak"> </div><div class="instrbreak"><strong>Hidden Easter Eggs within the 95LX and other models</strong> </div><div class="instrbreak"> </div><div class="instrbreak">With the palmtop off, hold down [Esc] and press
[On]. The palmtop enters its ROM-based self-test mode. (Warning! Do NOT
run the Plug-in Card test on a flash card - it will destroy data! This
test is meant for older SRAM cards only!) </div><div class="instrbreak">Cursor down to the Display test, then...</div><div class="instrbreak"> </div><div class="instrbreak"> </div><div class="instrbreak">For HP 95LX, 100LX and 200LX: </div><div class="instrbreak">Press [Enter] 14 times to step through the display modes, and you will see a limerick about a caveman.</div><div class="instrbreak"> </div><div class="instrbreak"> </div><div class="instrbreak">For 100LX and 200LX: </div><div class="instrbreak">Press
[Ctrl]+[Enter], then hold down [Alt] while pressing [Enter] 13 times.
You will see a cryptic poem, presumably about troubles the HP
developers went through.</div><div class="instrbreak"> </div><div class="instrbreak"> </div><div class="instrbreak">For 200LX: </div><div class="instrbreak">Press [Ctrl]+[Enter], then hold down [Shift] while pressing [Enter] 13 times. You will see a poem about Jaguar, Cougar and Felix (the codenames for the 95LX, 100LX and 200LX).</div><div class="instrbreak"> </div><div class="instrbreak"><strong>Assembley Image for HP 95LX</strong></div><div class="instrbreak"> </div><div class="instrbreak"> <img src="http://www.skolob.co.uk/skolob/gallery/1/hp-95assy.jpg" border="0" alt="HP 95LX Assembly Image" /></div><p> </p>Palmtop PC2007-03-14T10:06:52Zskolob