So you think you have an education

During a period of unemployment I went to learn something about computing.

This was in the late '80's early '90's. …

Today I tried to find out what college I went to to learn about the internet tube line thingie.

I went sooooo long ago I had forgotten the name of the place. I knew where it was though, roughly.

So I plugged in the website I came up with and got the courses offered link:

http://www.llandrillo.ac.uk/courses/2011-2012/location/default.aspx?loc=L

Being the place I got my IT qualification I though it should do better than this:
[quote]Server Error in '/' Application.
ERROR [28000] [Microsoft][SQL Native Client][SQL Server]Login failed for user 'WebGuest'.
ERROR [28000] [Microsoft][SQL Native Client][SQL Server]Login failed for user 'WebGuest'. 
 Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

 Exception Details: System.Data.Odbc.OdbcException: ERROR [28000] [Microsoft][SQL Native Client][SQL Server]Login failed for user 'WebGuest'.
ERROR [28000] [Microsoft][SQL Native Client][SQL Server]Login failed for user 'WebGuest'.

Source Error: 
 The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

   <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
    <system.web>
        <compilation debug="true"/>
    </system.web>
</configuration>

 Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. 


Stack Trace: 

[OdbcException (0x80131937): ERROR [28000] [Microsoft][SQL Native Client][SQL Server]Login failed for user 'WebGuest'.
ERROR [28000] [Microsoft][SQL Native Client][SQL Server]Login failed for user 'WebGuest'.]
   System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode) +1156770
   System.Data.Odbc.OdbcConnectionHandle..ctor(OdbcConnection connection, OdbcConnectionString constr, OdbcEnvironmentHandle environmentHandle) +95
   System.Data.Odbc.OdbcConnectionOpen..ctor(OdbcConnection outerConnection, OdbcConnectionString connectionOptions) +53
   System.Data.Odbc.OdbcConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject) +55
   System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +29
   System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +4863708
   System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +117
   System.Data.Odbc.OdbcConnection.Open() +40
   courses_location_Default.Page_Load(Object sender, EventArgs e) +1265
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +50
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627


Version Information: Microsoft .NET Framework Version:2.0.50727.3625; ASP.NET Version:2.0.50727.3618[/quote]

Having seen the word "[Microsoft]" in brackets I thought :
Must be me on linux.

So I looked up the page quality for the Home Page on the international mark up service offered by the web standards authority W3C:

[quote=W3C] Markup Validation Service 

Check the markup (HTML, XHTML, …) of Web documents
Jump To: Notes and Potential Issues Validation Output 
Errors found while checking this document as XHTML 1.0 Transitional!Result:	 31 Errors, 27 warning(s) 
Address:	
Encoding:	utf-8	 
Doctype:	XHTML 1.0 Transitional	 
Root Element:	html
Root Namespace:	http://www.w3.org/1999/xhtml

The W3C validators rely on community support for hosting and development.
Donate and help us build better tools for a better web.
OptionsShow Source	Show Outline	List Messages Sequentially Group Error Messages by Type
Validate error pages	Verbose Output	Clean up Markup with HTML-Tidy

Help on the options is available. 
 
Notes and Potential Issues

The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.

 Character Encoding mismatch!

 The character encoding specified in the HTTP header (utf-8) is different from the value in the <meta> element (iso-8859-1). I will use the value from the HTTP header (utf-8) for this validation. 

↑ Top
Validation Output: 31 Errors 
 Line 11, Column 4: "if" is not a reserved name 
<![if !IE]><link rel="stylesheet" type="text/css" href="css/non-ie.css" /><![en…

✉ 
 Line 11, Column 7: character data is not allowed here 
<![if !IE]><link rel="stylesheet" type="text/css" href="css/non-ie.css" /><![en…

✉ 

 You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include: 
putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML. 
 Line 11, Column 78: "endif" is not a reserved name 
… !IE]><link rel="stylesheet" type="text/css" href="css/non-ie.css" /><![endif]>

✉ 
 Line 84, Column 75: character "&" is the first character of a delimiter but occurred as data 
…><a href="studentinformation/support/default.aspx">Guidance & Support </a></li>

✉ 

 This message may appear in several cases: 
You tried to include the "<" character in your page: you should escape it as "&lt;"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
 Line 164, Column 93: required attribute "alt" not specified 
…elsh-for-adults/"><img src="/img/home/banners/welsh-for-adults.jpg" /></a></li>

✉ 

 The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element. 

 Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>. 
 Line 252, Column 32: there is no attribute "onMouseover" 
            <li>[html:a onMouseover="document.imagename.src=image1.src" onMouseout="…

✉ 

 You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). 

 This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. 

 How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the  element to incorporate flash media in a Web page, see the FAQ item on valid flash. 
 Line 269, Column 250: there is no attribute "src" 
…ss" value="always"></param>[html:embed src="http://www.youtube.com/v/xh0VaAmo5AU?fs…

✉ 

 You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). 

 This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. 

 How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the  element to incorporate flash media in a Web page, see the FAQ item on valid flash. 
 Line 269, Column 362: there is no attribute "allowscriptaccess" 
…/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="3…

✉ 

 You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). 

 This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. 

 How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the  element to incorporate flash media in a Web page, see the FAQ item on valid flash. 
 Line 269, Column 387: there is no attribute "allowfullscreen" 
…scriptaccess="always" allowfullscreen="true" width="310" height="215"></embed>…

✉ 

 You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). 

 This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. 

 How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the  element to incorporate flash media in a Web page, see the FAQ item on valid flash. 
 Line 269, Column 400: there is no attribute "width" 
…cess="always" allowfullscreen="true" width="310" height="215"></embed></object>

✉ 

 You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). 

 This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. 

 How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the  element to incorporate flash media in a Web page, see the FAQ item on valid flash. 
 Line 269, Column 413: there is no attribute "height" 
…cess="always" allowfullscreen="true" width="310" height="215"></embed></object>

✉ 

 You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead). 

 This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information. 

 How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the  element to incorporate flash media in a Web page, see the FAQ item on valid flash. 
 Line 269, Column 418: element "embed" undefined 
…cess="always" allowfullscreen="true" width="310" height="215"></embed></object>

✉ 

 You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by: 
incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
 Line 296, Column 31: document type does not allow element "style" here 
        <style type="text/css">.flickr_badge_image img {border: 1px solid #c7c7…

✉ 

 The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed). 

 One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error). 
 Line 297, Column 160: cannot generate system identifier for general entity "display" 
….flickr.com/badge_code_v2.gne?count=1&display=random&size=m&layout=x&source=us…

✉ 

 An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs". 

 Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters. 

 If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem. 

 Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed. 
 Line 297, Column 160: general entity "display" not defined and no default entity 
….flickr.com/badge_code_v2.gne?count=1&display=random&size=m&layout=x&source=us…

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 297, Column 167: reference not terminated by REFC delimiter 
….com/badge_code_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&…

✉ 

 If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text. 
 Line 297, Column 167: reference to external entity in attribute value 
….com/badge_code_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&…

✉ 

 This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'. 
 Line 297, Column 167: reference to entity "display" for which no system identifier could be generated 
….com/badge_code_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&…

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 297, Column 159: entity was defined here 
…w.flickr.com/badge_code_v2.gne?count=1&display=random&size=m&layout=x&source=u…
 Line 297, Column 175: cannot generate system identifier for general entity "size" 
…ge_code_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=437…

✉ 

 An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs". 

 Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters. 

 If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem. 

 Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed. 
 Line 297, Column 175: general entity "size" not defined and no default entity 
…ge_code_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=437…

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 297, Column 179: reference not terminated by REFC delimiter 
…ode_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=4378749…

✉ 

 If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text. 
 Line 297, Column 179: reference to external entity in attribute value 
…ode_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=4378749…

✉ 

 This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'. 
 Line 297, Column 179: reference to entity "size" for which no system identifier could be generated 
…ode_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=4378749…

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 297, Column 174: entity was defined here 
…dge_code_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=43…
 Line 297, Column 182: cannot generate system identifier for general entity "layout" 
…_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=43787499%4…

✉ 

 An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs". 

 Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters. 

 If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem. 

 Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed. 
 Line 297, Column 182: general entity "layout" not defined and no default entity 
…_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=43787499%4…

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 297, Column 188: reference not terminated by REFC delimiter 
…e?count=1&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&t…

✉ 

 If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text. 
 Line 297, Column 188: reference to external entity in attribute value 
…e?count=1&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&t…

✉ 

 This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'. 
 Line 297, Column 188: reference to entity "layout" for which no system identifier could be generated 
…e?count=1&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&t…

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 297, Column 181: entity was defined here 
…e_v2.gne?count=1&display=random&size=m&layout=x&source=user_tag&user=43787499%…
 Line 297, Column 191: cannot generate system identifier for general entity "source" 
…ount=1&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=…

✉ 

 An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs". 

 Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters. 

 If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem. 

 Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed. 
 Line 297, Column 191: general entity "source" not defined and no default entity 
…ount=1&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=…

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 297, Column 197: reference not terminated by REFC delimiter 
…&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Websit…

✉ 

 If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text. 
 Line 297, Column 197: reference to external entity in attribute value 
…&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Websit…

✉ 

 This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'. 
 Line 297, Column 197: reference to entity "source" for which no system identifier could be generated 
…&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Websit…

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 297, Column 190: entity was defined here 
…count=1&display=random&size=m&layout=x&source=user_tag&user=43787499%40N06&tag…
 Line 297, Column 207: cannot generate system identifier for general entity "user" 
…andom&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Website"></scrip…

✉ 

 An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs". 

 Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters. 

 If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem. 

 Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed. 
 Line 297, Column 207: general entity "user" not defined and no default entity 
…andom&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Website"></scrip…

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 297, Column 211: reference not terminated by REFC delimiter 
…m&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script></…

✉ 

 If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text. 
 Line 297, Column 211: reference to external entity in attribute value 
…m&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script></…

✉ 

 This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'. 
 Line 297, Column 211: reference to entity "user" for which no system identifier could be generated 
…m&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script></…

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 297, Column 206: entity was defined here 
…random&size=m&layout=x&source=user_tag&user=43787499%40N06&tag=Website"></scri…
 Line 297, Column 227: cannot generate system identifier for general entity "tag" 
…layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script></div></div>

✉ 

 An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs". 

 Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters. 

 If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem. 

 Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed. 
 Line 297, Column 227: general entity "tag" not defined and no default entity 
…layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script></div></div>

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 297, Column 230: reference not terminated by REFC delimiter 
…layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script></div></div>

✉ 

 If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text. 
 Line 297, Column 230: reference to external entity in attribute value 
…layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script></div></div>

✉ 

 This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'. 
 Line 297, Column 230: reference to entity "tag" for which no system identifier could be generated 
…layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script></div></div>

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 297, Column 226: entity was defined here 
…layout=x&source=user_tag&user=43787499%40N06&tag=Website"></script></div></div>
 Line 485, Column 10: end tag for "ul" which is not finished 
     </ul> 

✉ 

 Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p> 

 Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on. 
 Line 495, Column 74: character "&" is the first character of a delimiter but occurred as data 
…ext" style="margin-left:20px;">Advice & Guidance:  01492 542 338/9</strong><br…

✉ 

 This message may appear in several cases: 
You tried to include the "<" character in your page: you should escape it as "&lt;"
You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.
 Line 509, Column 106: cannot generate system identifier for general entity "continue" 
…llo.ac.uk/ServiceLogin?service=CPanel&continue=https%3A%2F%2Fwww.google.com%3A…

✉ 

 An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs". 

 Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters. 

 If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem. 

 Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed. 
 Line 509, Column 106: general entity "continue" not defined and no default entity 
…llo.ac.uk/ServiceLogin?service=CPanel&continue=https%3A%2F%2Fwww.google.com%3A…

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 509, Column 114: reference not terminated by REFC delimiter 
…k/ServiceLogin?service=CPanel&continue=https%3A%2F%2Fwww.google.com%3A443%2Fa%…

✉ 

 If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text. 
 Line 509, Column 114: reference to external entity in attribute value 
…k/ServiceLogin?service=CPanel&continue=https%3A%2F%2Fwww.google.com%3A443%2Fa%…

✉ 

 This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'. 
 Line 509, Column 114: reference to entity "continue" for which no system identifier could be generated 
…k/ServiceLogin?service=CPanel&continue=https%3A%2F%2Fwww.google.com%3A443%2Fa%…

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 509, Column 105: entity was defined here 
…illo.ac.uk/ServiceLogin?service=CPanel&continue=https%3A%2F%2Fwww.google.com%3…
 Line 509, Column 200: cannot generate system identifier for general entity "passive" 
…panel%2Fcloud.llandrillo.ac.uk%2FDashboard&passive=true">Student Email</a></li>

✉ 

 An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs". 

 Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters. 

 If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem. 

 Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed. 
 Line 509, Column 200: general entity "passive" not defined and no default entity 
…panel%2Fcloud.llandrillo.ac.uk%2FDashboard&passive=true">Student Email</a></li>

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 509, Column 207: reference not terminated by REFC delimiter 
…panel%2Fcloud.llandrillo.ac.uk%2FDashboard&passive=true">Student Email</a></li>

✉ 

 If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text. 
 Line 509, Column 207: reference to external entity in attribute value 
…panel%2Fcloud.llandrillo.ac.uk%2FDashboard&passive=true">Student Email</a></li>

✉ 

 This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'. 
 Line 509, Column 207: reference to entity "passive" for which no system identifier could be generated 
…panel%2Fcloud.llandrillo.ac.uk%2FDashboard&passive=true">Student Email</a></li>

✉ 

 This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details. 
 Line 509, Column 199: entity was defined here 
…panel%2Fcloud.llandrillo.ac.uk%2FDashboard&passive=true">Student Email</a></li>

↑ Top
Home About... News Docs Help & FAQ Feedback Contribute 

 This service runs the W3C Markup Validator, v1.2+hg. 

Copyright © 1994-2011 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.[/quote]

I'd have thought a college in Britain would have valid website standards. It would seem they are all just Microsft clowns or clones or whatever the word is.

At least it explains my problems with computing. A perpetual lamer.

But even as a lamer, I would have gone to the web validation site and got it checked out.
What do |I do now.

Write and tell them?
Hardly. They have IT tech and teachers teaching IT tech as far as I know. Or maybe they got out of that line after so many failures like me wanted our money back (I didn't get it but I managed to slip in their not for students site and found some comments about my bad temper. To which I added a few comments of my own.)

So now it's pay back time.
Not really.

My problem is I need the address for my CV.
Would you add a college like that to your CV?
Or smear it into obscurity with the wrong name or something and hope it gets by the board?

TBH I don't care that much. I don't have much in a recent CV and the job on offer isn't that good a job.
Can someone out there please supply me with a reference?
Advertisements

20 thoughts on “So you think you have an education

  1. YOU HAVE READ THIS?????You sad color=white expletive deleted /color]Apparently they have stopped coding for white!Opera is losing it in my opinion.Nowegians are perhaps a little lacking in humour?

  2. Hi, Weatherlawyer!!!Originally posted by Weatherlawyer:

    YOU HAVE READ THIS?????You sad and I'm a bastard

    😀 tu no necesitas pedir "a reference" with a please. Creo que eres más útil aquí con nosotros en OC!!!

  3. Sorry about the language. I was boiling mad at ther time. It seems all so petty now.I tried to put those messages in white. I have just tried a colout that is suppoesde to be allowed "silver" but that didn't work ewither.Red does. Not a lot of use that though, is it?Who uses red; besides women?Stupid ****** coders!What is OC?

  4. Hi, Mike!!! How is your day, dear?
    Sabes? me preguntaba cómo estaba tu vida y pasé a mirar esta frondosa publicación de posts. Y, me llamó la atención que el título estuviese repetido. Entonces, dije: "Mi amigo Mike debe estar haciendo de las suyas" y me lo leí todooooo. 😎 Exactamente así me pasó en uno de mis cursos de computación en ingeniería, cuando se programaba con tarjetas perforadas… era todo tan complicado :ko: :faint: pero esos son tiempos pasados. Hay que recuperarse y seguir la vida.
    Debo admitir que, me sorprendíste con la palabra innombrable en blanco. Eres un excelente hombre, pero muy grosero. Insisto, me parece que fuiste un niño muy mimado, de esos niños que les dan puntapies a las puertas, o al menos eso se nota en algunos de tus posts.
    Sin embargo, esa actitud me causa risa. Claro, yo no pretendo burlarme de ti, yo respeto lo que hagas con tu vida. Ahora, me considero tu amiga, y por eso te digo lo mimado y travieso que pareces. Para mí, eso es divertido. :p pero no te metas conmigo :knight: :queen:
    ¿¿¿Rojo es un color sólo femenino??? :no: queda muy bien para resaltar, Mike.
    What is OC? OC: Opera Community :whistle: 😆
    Happy day!!!

  5. The Original post is about the college I went to in my youth.The website wouldn't open properly in Linux.So I copied the URL and pasted it in the W3C markup checker. It came out with a ton of errors as you can see.It just annoyed me that the place that has taught me computing could have such a poor website. What sort of hard times have they fallen on?One of the instructors there in my day wrote a programme to show the delivery of a complete transport system. It showed every ship the company had and every route any tanker took right into the port/refinery where it was distributed as petrol in lorries.And that was in the 1980's I think.So who or what developed their present site?

  6. Originally posted by semirami:

    You know I wondered how your life was spent looking at this lush publishing posts. And I noticed that the title was repeated. Then I said, "My friend Mike should be making the rounds" and I read it todooooo.Just so happened to me in one of my computer courses in engineering, when programmed with punch cards … it was so complicated but these are times past. We must recover and continue life.I must admit, surprised me with the word unspeakable blank. You are an excellent man, but very rude. Again, I think you were a very spoiled child, one of those kids who are kicking the doors, or at least it shows in some of your posts. However, this attitude makes me laugh. Sure, I do not mean to make fun of you, I respect what you do with your life. Now, I consider myself your friend, so I tell you what you seem spoiled and naughty. To me, that's funny. but do not mess with me¿¿¿Red is a colour only for females??looks good to highlight, Mike

    Punch cards. You are an Ancient Geek.Yes I am spoiled. I needed an harder hand when it mattered. Too late now and yes, I aught to get out a lot more. I have miised all this beautiful weather we are having.I have been nursing this d-d computer watching for earthquakes. You see, with me it is all or nothing. I have absolutely no self control.I beg pardon for the bad language.Your sister keeps telling me off but it just doesn't work when I get wound up with these computers.I wonder why it only posts tyhe plain colours (as if white is not plain or silver is exotic!)I have lost my sound files again. I know it is a settings problem, because the thing makes a noise when it starts up. I just can't get it to record my voice.I seem doomed with these things. I can never get one to work properly.Originally posted by semirami:

    What is OC? OC: Opera Community

    Ai caramba!

  7. Originally posted by Weatherlawyer:

    Punch cards. You are an Ancient Greek.

    Pues, sí… in the 1980's. Estoy segura de eso 🙂 Originally posted by Weatherlawyer:

    Yes I am spoiled. I needed an harder hand when it mattered. Too late now and yes, I aught to get out a lot more. I have missed all this beautiful weather we are having.

    Entonces, solo sonreiré cuando vea tus travesuras con camuflaje. Además, tu eres culpable… tu me enseñaste ese truco 😀 No problem, lo seguiremos pasando great :yes: cuñao!!!

  8. Originally posted by Weatherlawyer:

    .The Original post is about the college I went to in my youth…. And that was in the 1980's I think.

    Ah? pero, estabas estudiando computación o diseño naval in the '80? :confused: Para tu edad, yo creo que esos estudios fueron como en los 1970's :sherlock: porque yo estudié en la década 1980.

  9. Originally posted by semirami:

    Pues, sí… in the 1980's. Estoy segura de eso Originally posted by Weatherlawyer:Entonces, solo sonreiré cuando vea tus travesuras con camuflaje. Además, tu eres culpable… tu me enseñaste ese truco No problem, lo seguiremos pasando great cuñao!!!

    So I'll smile when you see only your antics with camouflage. In addition, you are guilty … you taught me that trick No problem, we will continue going cuñao great!Originally posted by semirami:

    Ah? pero, estabas estudiando computación o diseño naval in the '80? Para tu edad, yo creo que esos estudios fueron como en los 1970's porque yo estudié en la década 1980.

    Ah? but were [you] studying computer science or naval architecture in the '80s? For your age, I believe that these studies were as in the 1970's because I studied in the early 1980.I was only on a beginner's course. Introduction to computers. Part time.Why ask me if I studied naval architecture?I would have a good job building ships if I had.Just a humble carpenter.I just remembered some dates it fell between:http://duckduckgo.com/?q=towyn+and+kinmel+bay+flood&t=oukhttp://www.dailypost.co.uk/news/north-wales-news/2010/02/26/towyn-floods-remembered-20-years-on-55578-25917704/andhttp://duckduckgo.com/?q=towyn+and+kinmel+bay+flood&t=oukhttp://hansard.millbanksystems.com/written_answers/1993/jul/23/flooding-llandudnoBetween those two events I began trying to understand natural disaster.I had got far enough by the Landudno flood that I could forecast rain. I told the computer teacher that I had to leave early as it was about to rain. It was a bright day but scudding clouds had been moving across the sky.I already knew I was going to get a soaking if I didn't hurry. I was going to Bike home to Bangor from Rhos on Sea.I got as far as the Penmaenmawr Tunnel and it started belting down painful hail. I just made it to the tunnel.I found out later that Llandudno got a flash flood.That same time when I got to my mother's house, there was news of a hurricane in Eluthera, Bahamas.After that I really got down to work.I went to all the second hand bookshops and all the libraries devouring everything I could find on astronomy, navigation and weather.It's all a blur as it was an ecclectic mix and I didn't have a clue where any of it would take me or how to search for information.But I do remember the real clincher later when I was struggling to understand tides, wondering if the timing of the tides had as much effect as the declination of the moon and sun.Then the big break through:Wondering if one time of the phase would cause a difference. I had already worked out that a random time difference of an hour or so in the time of the phase meant the difference between rain or shine.(I just happened to be living and moving around in a very tight semicircle bound between mountains and the sea -all through that initiation.)So that's where I really got interested in the sea.Though all of my father's people were sailors or had been. And my mother's people had always lived on the sea shore where I grew up.I suppose that since I grew up with it I never thought of doing anything WITH it for a living. I wish now that I had.Do you know that where the land curves around the shore, forms a ring -at the centre of which is to be found the mineral wealth of the area. Gas in the sea off that coast is 12 miles from every part of the shore from Llandudno to Rhyl.It will be roughly the same everywhere. Try it with the oil wells off Venezuela. If you get rich, mention me to Hugo Chavez.

  10. Originally posted by semirami:

    Hola Mike!!! Espero estés bien. Gracias por aclararme tu oficio. Creo que mi comentario no fue muy acertado porque, según Teresa, no traduje bien, lo cual me impidió comprender tu narrativa previa. Por otra parte, en nuestra costas venezolanas hay petroleo pro también tierra adentro:

    That's easy for you to say.

  11. Originally posted by semirami:

    http://www.mipunto.com/venezuelavirtual/mapas/mapa_hidrocarburos.html

    It is a most curvaceous coastline.It is in fact Spirilliant.The curve starts at Peninsula de la Guaura with the centre at Marcay.It turns around the inside of the hills along the Orinoco and goes out to Puerto Spain.It then runs along the islands to Puerto Rico and Jamaica eventually ending up in the River Coco in Nicaragua.It is a very elliptical spiral but a spiral no less.If you draw perpendiculars from tangents inside the spiral, you will find where the best places to search for oil beds.It looks like it is very close to the Golden Mean.

  12. Originally posted by Weatherlawyer:

    If you draw perpendiculars from tangents inside the spiral

    The arc of the south coast of Santa Domingo looks promising. But then , so do the three curves in Cuba and nobody has looked at Cuba for oil, have they?

  13. I don't think the CIA will be happy:Originally posted by Reuters:

    First Cuba offshore well going slowly, mid-May finish seen* Sources say Repsol encouraged by findings so far* Cuba says five wells to be drilled in 2012-2013* Cuba dependent on Venezuela, Chavez for oilBy Jeff FranksHAVANA, April 13 (Reuters) – Drilling of the first well in the long-awaited exploration of Cuba's offshore oilfields has gone slower than expected, but should be completed by mid-May, sources close to the project said on Friday.They said drillers had encountered harder rock beneath the sea bed than expected, which combined with other minor problems, had slowed progress.When drilling began on Feb. 1, Spanish oil giant Repsol YPF said the average deepwater well takes 60 days to complete, but that many drag on much longer, depending on conditions.A Repsol spokesman could not confirm on Friday the projected mid-May completion date.This well, which is in 5,600 feet (1,706 metres) of water off the communist-run island's north west coast, is the first of five currently planned, Cuban officials say.Cuba has said it could have 20 billion barrels in its offshore fields. It needs the oil to end its dependence on Venezuela, which ships it 114,000 barrels a day.Venezuelan President Hugo Chavez is Cuba's top ally, but island leaders worry that the oil flow could stop if he dies or loses his bid for re-election later this year.The U.S. Geological Survey estimated Cuba may have 5 billion barrels of oil and 10 trillion cubic feet of natural gas offshore, but its study covered only part of the Cuban zone.Various sources said Repsol has been encouraged by its findings thus far, but the company has said results will not be known until the well is finished and studies are conducted.Oil experts say it will take three years or more to bring the Cuban oil on line, if enough is found to justify production.After Repsol completes its well, it will hand the Scarabeo 9 drilling rig over to Malaysia's state-owned Petronas and its Russian partner Gazprom Neft for a second well.Then it will go back to Repsol, which has a consortium with Norway's Statoil and ONGC Videsh, a unit of India's ONGC, for another well.The massive, Chinese-built rig, which is more than 20 miles (32 km) offshore but visible from Havana, is being leased from owner Saipem, a unit of Italian oil company Eni.Repsol drilled a well in Cuban waters in 2004 and found oil, but said it was not commercially viable. Technological limitations imposed by the embargo made it difficult to find another rig for work in Cuba, industry sources have said.

    They should be looking on the Venezuelan side in the softer rock of the shallows in Golfo Batanbo, Golfo de Ana Maria and Golfo de Guacanayabo.Somehow, I don't think that they will listen to me though.

  14. Originally posted by Washington Post:

    Congressional Republicans representing Cuban American communities in Florida say the Obama administration should have imposed sanctions and threatened foreign companies such as Repsol from doing business in Cuba.

    Odd that the people who killed President Kennedy should want to kill President Castro. After getting his lifetime's supply of Cuban cigars secured, it was Kennedy who imposed the embargo. God knows why it is still in place, it is an anachronism.Maybe they just like killing people:

    Congressional Republicans representing Cuban American communities in Florida say the Obama administration should have imposed sanctions and threatened foreign companies such as Repsol from doing business in Cuba.“We need to figure out what we can do to inflict maximum pain, maximum punishment, to bleed Repsol of whatever resources they may have if there’s a potential for a spill that would affect the U.S. coast,” Rep. David Rivera (R-Fla.) told in January a congressional subcommittee that oversees the U.S. Coast Guard.

    There's never a shortage of some very nasty people around, when you look at US foreign policy.Is there?

  15. Meanwhile, in the real world:If you have a globe of the world, make a couple of paper discs; one of 10 degrees diameter and one of 9 degrees.Now play along the coast of Central and South America with them.If you don't have a globe of the world, get one. The perspective of your home is totally different from that given in the 2D of an atlas.For instance compare the Mainland coast of the Gulf of Mexico with the South East coastline of the Caribbean.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s