Jump to content

RetroTechCollection:Reliable technical sources: Difference between revisions

From RetroTechCollection
Created page with "{{shortcut|RTC:RTS}} {{guideline}} '''Reliable technical sources''' provide accurate, verifiable information for documenting vintage computing and gaming hardware. This guideline helps contributors identify authoritative sources while recognizing the unique challenges of documenting obsolete technology where original manufacturers may no longer exist. == Source Hierarchy == === Tier 1: Primary Technical Sources === '''Most authoritative''' - Use as primary references:..."
 
Remove Category:Source evaluation (category does not exist; page is in RetroTechCollection guidelines)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{shortcut|RTC:RTS}}
{{guideline}}
{{guideline}}


'''Reliable technical sources''' provide accurate, verifiable information for documenting vintage computing and gaming hardware. This guideline helps contributors identify authoritative sources while recognizing the unique challenges of documenting obsolete technology where original manufacturers may no longer exist.
A '''reliable technical source''' gives accurate, checkable information about vintage computing and gaming hardware. This guideline helps contributors judge sources for machines whose manufacturers may no longer exist.


== Source Hierarchy ==
== Source hierarchy ==


=== Tier 1: Primary Technical Sources ===
=== Tier 1: primary technical sources ===
'''Most authoritative''' - Use as primary references:
The most authoritative. Use as primary references:
* official service manuals: the manufacturer's repair and maintenance documentation
* engineering schematics and technical drawings
* component datasheets from the component manufacturer
* technical bulletins: official updates, corrections and modifications
* factory training material: service courses and certification documentation
* patents and other engineering documents


* '''Official service manuals''' - Factory-authorized repair and maintenance documentation
=== Tier 2: published technical references ===
* '''Engineering schematics''' - Original circuit diagrams and technical drawings
Highly reliable. Suitable for primary sourcing:
* '''Component datasheets''' - Manufacturer specifications for individual components
* technical books by authors with documented industry experience
* '''Technical bulletins''' - Official updates, corrections, and modifications
* peer-reviewed academic papers on computer history and technology
* '''Factory training materials''' - Service courses and certification documentation
* trade magazines with technical editorial standards
* '''Patents and engineering documents''' - Legal filings with detailed technical descriptions
* conference proceedings
* government, military and research-institution technical reports


=== Tier 2: Published Technical References ===
=== Tier 3: established technical websites ===
'''Highly reliable''' - Suitable for primary sourcing:
Generally reliable. Good for supporting information:
* websites of manufacturers that still maintain legacy product information
* museum documentation from institutions with curatorial standards
* technical wikis with an established community and editorial oversight, cited to the specific page (for example a capacitor list on the Console5 wiki, identified as a secondary source)
* professional repair services with a documented reputation
* universities and technical schools


* '''Technical books by recognized experts''' - Authors with documented industry experience
=== Tier 4: community sources ===
* '''Academic papers''' - Peer-reviewed research on computer history and technology
Use with caution and verify where possible:
* '''Industry publications''' - Trade magazines with technical editorial standards
* moderated technical forums with established expertise and peer review
* '''Conference proceedings''' - Papers from technical conferences and symposiums
* blogs by individuals with verifiable technical credentials
* '''Government technical reports''' - Military or research institution documentation
* technical videos backed by written documentation
* collaborative community documentation projects


=== Tier 3: Established Technical Websites ===
== Evaluating a source ==
'''Generally reliable''' - Good for supporting information:
Ask:
* Does the author have relevant technical experience, or industry background?
* Can the claims be checked against other sources?
* Does it give detailed procedures with specific values, and appropriate safety warnings?
* Does it cite the original documentation?
* Does it correct its mistakes?
* For community sources: have other experts reviewed it, and does the source have a record of accuracy?


* '''Manufacturer websites''' - Current companies maintaining legacy product information
== Specific source types ==
* '''Museum documentation''' - Computer history museums with curatorial standards
* '''Technical wikis''' - Sites with established communities and editorial oversight
* '''Professional repair services''' - Businesses with documented expertise and reputation
* '''Educational institutions''' - Universities and technical schools with relevant programs


=== Tier 4: Community Sources ===
=== Service manuals ===
'''Use with caution''' - Verify when possible:
Original manufacturer documentation is the best source.


* '''Moderated technical forums''' - Communities with established expertise and peer review
Highly reliable:
* '''Expert blogs''' - Technical blogs by individuals with verifiable credentials
* official factory service manuals
* '''Video documentation''' - Technical videos with supporting written documentation
* authorised dealer training material
* '''Collaborative projects''' - Community-driven documentation with multiple contributors
* factory service bulletins and updates
* licensed third-party service documentation


== Evaluating Source Quality ==
Use with verification:
* scans of uncertain provenance
* translations of foreign-language manuals
* manuals reconstructed from several sources
* community-written service guides


=== Technical Authority ===
=== Technical specifications ===
Assess the technical credibility of sources:
Primary sources are original component datasheets, system specification sheets, engineering drawings and schematics, and factory test procedures. Secondary sources are technical reference books, industry standards documents, specifications cross-referenced from several sources, and verified community measurements.


* '''Author credentials''' - Does the author have relevant technical experience?
=== Historical information ===
* '''Professional background''' - Has the author worked in the relevant industry?
For dates, production numbers and history, the authoritative sources are company annual reports and press releases, dated patent filings, contemporary industry publications, and museum and archive collections. Supporting sources are period technical journalism, interviews with the original engineers, community documentation projects, and examination of the hardware itself (date codes, board revisions).
* '''Technical accuracy''' - Can claims be verified against other sources?
* '''Peer recognition''' - Is the author recognized by other technical professionals?


=== Documentation Standards ===
== Manufacturer considerations ==
Look for sources that demonstrate:


* '''Detailed procedures''' - Step-by-step instructions with specific parameters
=== Active companies ===
* '''Safety awareness''' - Appropriate warnings and safety procedures
A manufacturer still in business may keep legacy product information and support documentation on its website, and may issue official statements. Documentation it has authorised is a licensed source.
* '''Error acknowledgment''' - Willingness to correct mistakes and update information
* '''Source attribution''' - References to original documentation and other sources


=== Community Validation ===
=== Defunct companies ===
For community sources, consider:
For companies no longer trading, look to archive collections (museums, libraries and private collections), documentation from former engineers and technicians, companies that acquired the assets or rights, and community preservation projects.


* '''Peer review''' - Has the information been reviewed by other experts?
=== Changes of ownership ===
* '''Track record''' - Does the source have a history of accurate information?
When a company has changed hands, the documentation rights may belong to the acquirer, to a licensed distributor, or to several different owners after a partial acquisition. Some older documentation may be in the public domain.
* '''Community standing''' - Is the author respected within the technical community?
* '''Correction mechanisms''' - Are errors identified and corrected promptly?


== Specific Source Types ==
== Regional and language considerations ==
Hardware was often changed for different markets, and specifications differ between regions (mains voltage, video standard). Check which regional version a source describes.


=== Service Manuals ===
For non-English sources, use a qualified technical translator where possible, have translations checked by a native speaker with technical knowledge, compare sources in different languages, and make sure technical terms are translated correctly.
'''Original manufacturer documentation''' is the gold standard:


'''Highly Reliable:'''
== Online sources ==
* Official factory service manuals
Signs that a website is reliable: clear authorship and contact information, regular maintenance, a way to report corrections, and links to authoritative sources.
* Authorized dealer training materials
* Factory service bulletins and updates
* Licensed third-party service documentation


'''Use with Verification:'''
Warning signs: anonymous authorship, no source attribution, out-of-date information, no way to report corrections, and heavy advertising or commercial focus.
* Scanned copies of uncertain provenance
* Translations of foreign-language manuals
* Reconstructed manuals based on multiple sources
* Community-created service guides


=== Technical Specifications ===
For web pages that may disappear, use the Wayback Machine, institutional digital archives and community mirror sites, and keep local copies of important documents. Manuals can be uploaded here; see [[Help:Uploading service manuals]].
'''Component and system specifications''' require careful verification:


'''Primary Sources:'''
== Forums and community experts ==
* Original component datasheets
The best forums are moderated, long established, encourage citation, correct mistakes, and have expert moderators. Look for claims confirmed by several experts, references to the original documentation, detailed procedures with specific measurements, and a record of accuracy.
* System specification sheets
* Engineering drawings and schematics
* Factory test procedures


'''Secondary Sources:'''
A reliable community expert has relevant professional experience, is respected by other members, is consistently accurate, cites authoritative sources, and admits and corrects mistakes.
* Technical reference books
* Industry standard documents
* Cross-referenced specifications from multiple sources
* Verified community measurements


=== Historical Information ===
== Special circumstances ==
'''Dates, production numbers, and historical context:'''


'''Authoritative Sources:'''
=== Poorly documented hardware ===
* Company annual reports and press releases
Where documentation is unclear or missing, cross-check every source you can find, take the most conservative interpretation when sources conflict, look for agreement among several experts, and test procedures and specifications yourself where it is safe to do so.
* Patent filings with dates
* Contemporary industry publications
* Museum and archive collections


'''Supporting Sources:'''
=== Proprietary information ===
* Technical journalism from the period
Proprietary technical data may be used when the rights holder has officially released it, when it was obtained legally by reverse engineering, when it was released in the public interest, or when it has become public with time.
* Interviews with original engineers
* Community documentation projects
* Archaeological evidence from hardware examination


== Manufacturer-Specific Considerations ==
=== Conflicting sources ===
 
=== Active Companies ===
For manufacturers still in business:
 
* '''Current websites''' - May maintain legacy product information
* '''Support documentation''' - Sometimes includes historical technical data
* '''Official statements''' - Press releases and technical communications
* '''Licensed materials''' - Documentation authorized by current copyright holders
 
=== Defunct Companies ===
For companies no longer in business:
 
* '''Archive collections''' - Museums, libraries, and private collections
* '''Former employee documentation''' - Engineers and technicians from the original company
* '''Successor company information''' - Companies that acquired assets or rights
* '''Community preservation efforts''' - Volunteer documentation and preservation projects
 
=== Licensing and Acquisitions ===
When companies have changed hands:
 
* '''Current rights holders''' - Companies that acquired technical documentation rights
* '''Licensing agreements''' - Authorized distributors of technical information
* '''Partial acquisitions''' - Some documentation may be owned by different entities
* '''Public domain status''' - Some older documentation may have entered public domain
 
== Regional and Language Considerations ==
 
=== International Sources ===
Technical information varies by region:
 
* '''Regional specifications''' - Different countries may have different technical standards
* '''Localization differences''' - Hardware may be modified for different markets
* '''Translation accuracy''' - Verify technical translations against original language sources
* '''Cultural context''' - Understanding regional manufacturing and design practices
 
=== Language Barriers ===
For non-English sources:
 
* '''Professional translation''' - Use qualified technical translators when possible
* '''Native speaker verification''' - Have translations checked by native speakers with technical knowledge
* '''Multiple language comparison''' - Compare information across different language sources
* '''Technical term accuracy''' - Ensure technical terminology is correctly translated
 
== Digital and Online Sources ==
 
=== Website Reliability ===
Evaluating online technical sources:
 
'''Indicators of Reliability:'''
* Professional presentation and organization
* Clear authorship and contact information
* Regular updates and maintenance
* Correction mechanisms and feedback systems
* Links to additional authoritative sources
 
'''Warning Signs:'''
* Anonymous authorship
* Lack of source attribution
* Outdated information without updates
* No mechanism for corrections
* Excessive advertising or commercial focus
 
=== Archive and Preservation ===
For historical online sources:
 
* '''Wayback Machine''' - Archive.org preservation of historical web content
* '''Digital archives''' - Institutional preservation of online materials
* '''Mirror sites''' - Community-maintained copies of important resources
* '''Download preservation''' - Local copies of critical technical documents
 
== Community and Forum Sources ==
 
=== Technical Forums ===
Evaluating community-generated technical content:
 
'''High-Quality Forums:'''
* Moderated communities with technical expertise
* Long-standing forums with established reputations
* Communities that encourage source citation
* Forums with correction and update mechanisms
* Sites with technical advisory boards or expert moderators
 
'''Quality Indicators:'''
* Multiple expert confirmation of technical claims
* References to original documentation
* Detailed procedures with specific measurements
* Community peer review and feedback
* Track record of accurate information
 
=== Expert Contributors ===
Identifying reliable community experts:
 
* '''Professional background''' - Industry experience in relevant fields
* '''Community recognition''' - Respected by other technical community members
* '''Consistent accuracy''' - Track record of providing correct information
* '''Source attribution''' - Regular citation of authoritative sources
* '''Error correction''' - Willingness to admit and correct mistakes
 
== Special Circumstances ==
 
=== Orphaned Hardware ===
For hardware with unclear documentation status:
 
* '''Multiple source verification''' - Cross-check information from various sources
* '''Conservative approach''' - Use most restrictive interpretation when sources conflict
* '''Community consensus''' - Rely on agreement among multiple expert sources
* '''Experimental verification''' - Test procedures and specifications when safe to do so
 
=== Proprietary Information ===
Handling confidential or proprietary technical data:
 
* '''Authorized disclosure''' - Information officially released by rights holders
* '''Reverse engineering''' - Legally obtained information through legitimate analysis
* '''Whistleblower protection''' - Information released in public interest
* '''Time-based release''' - Information that becomes public after certain periods
 
=== Conflicting Sources ===
When authoritative sources disagree:
When authoritative sources disagree:
* prefer the higher-tier source
* more recent information may supersede older data
* check whether each source covers a different board revision or region
* ask recognised technical experts
* measure it yourself where possible


* '''Source hierarchy''' - Prefer higher-tier sources over lower-tier ones
== Unreliable sources ==
* '''Date preference''' - More recent information may supersede older data
These are generally unreliable for technical documentation:
* '''Scope consideration''' - Some sources may cover specific revisions or regions
* social media posts, unless from verified official accounts
* '''Expert consultation''' - Seek input from recognized technical experts
* sales listings on eBay, Amazon or elsewhere
* '''Empirical testing''' - Verify through direct measurement when possible
* unmoderated wikis without editorial oversight
 
* anonymous technical claims
== Red Flags and Unreliable Sources ==
* clickbait sites
 
=== Avoid These Source Types ===
'''Generally unreliable for technical documentation:'''
 
* '''Social media posts''' - Unless from verified official accounts
* '''Sales listings''' - eBay, Amazon, or commercial descriptions
* '''Unmoderated wikis''' - Sites without editorial oversight or fact-checking
* '''Anonymous sources''' - Technical claims without identified authors
* '''Clickbait sites''' - Content designed for traffic rather than accuracy
 
=== Warning Signs ===
'''Indicators of potentially unreliable information:'''
 
* Lack of specific technical details
* Claims without supporting evidence
* Obvious technical errors or inconsistencies
* Failure to cite original sources
* Sensationalized or exaggerated claims
* Commercial bias or promotional content
 
== Verification Strategies ==
 
=== Cross-Reference Checking ===
Verify information through multiple sources:
 
* '''Independent confirmation''' - Find the same information in unrelated sources
* '''Technical consistency''' - Ensure specifications make technical sense
* '''Historical context''' - Verify information fits known historical timeline
* '''Expert review''' - Have technical experts evaluate questionable information
 
=== Empirical Verification ===
When possible, test information directly:
 
* '''Measurement verification''' - Test electrical specifications with appropriate equipment
* '''Procedure testing''' - Verify repair procedures on actual hardware
* '''Component testing''' - Confirm component specifications through direct testing
* '''Safety validation''' - Ensure safety procedures are effective and appropriate
 
== Documentation and Citation ==
 
=== Source Attribution ===
When using technical sources:


* '''Complete citation''' - Include all relevant publication information
Treat information with caution if it lacks specific technical detail, makes claims without evidence, contains obvious technical errors or inconsistencies, does not cite original sources, exaggerates, or has a commercial bias.
* '''Access information''' - Note how others can access the same source
* '''Version specificity''' - Identify specific versions or revisions
* '''Archive links''' - Provide permanent access through archive services


=== Quality Assessment ===
== Verification ==
Document source reliability:
* Find the same information in independent sources.
* Check that the specification makes technical sense and fits the known timeline.
* Check that the source covers the same machine and revision. A manual for a sibling model is not a source for its neighbour.
* Ask technical experts to review doubtful information.
* Where possible, test it directly: measure the voltages, try the procedure on real hardware, test the components, and confirm that safety procedures work.


* '''Tier classification''' - Identify which reliability tier the source belongs to
== Citing ==
* '''Verification status''' - Note whether information has been independently verified
Give the full publication details, say how others can get the same source, identify the version or revision, and add an archive link where the source may disappear. Note any known limitations of the source. See [[RetroTechCollection:Citing sources]].
* '''Limitations''' - Identify any scope limitations or known issues with the source
* '''Alternative sources''' - Provide additional sources when available


== See Also ==
== See also ==
* [[RetroTechCollection:Citing sources]]
* [[RetroTechCollection:Citing sources]]
* [[RetroTechCollection:Technical documentation]]
* [[RetroTechCollection:Technical documentation]]
* [[RetroTechCollection:Copyright policy]]
* [[RetroTechCollection:Copyrights]]
* [[RetroTechCollection:Content standards]]


[[Category:RetroTechCollection guidelines]]
[[Category:RetroTechCollection guidelines]]
[[Category:Source evaluation]]

Latest revision as of 17:36, 1 October 2026

A reliable technical source gives accurate, checkable information about vintage computing and gaming hardware. This guideline helps contributors judge sources for machines whose manufacturers may no longer exist.

Source hierarchy

[edit source]

Tier 1: primary technical sources

[edit source]

The most authoritative. Use as primary references:

  • official service manuals: the manufacturer's repair and maintenance documentation
  • engineering schematics and technical drawings
  • component datasheets from the component manufacturer
  • technical bulletins: official updates, corrections and modifications
  • factory training material: service courses and certification documentation
  • patents and other engineering documents

Tier 2: published technical references

[edit source]

Highly reliable. Suitable for primary sourcing:

  • technical books by authors with documented industry experience
  • peer-reviewed academic papers on computer history and technology
  • trade magazines with technical editorial standards
  • conference proceedings
  • government, military and research-institution technical reports

Tier 3: established technical websites

[edit source]

Generally reliable. Good for supporting information:

  • websites of manufacturers that still maintain legacy product information
  • museum documentation from institutions with curatorial standards
  • technical wikis with an established community and editorial oversight, cited to the specific page (for example a capacitor list on the Console5 wiki, identified as a secondary source)
  • professional repair services with a documented reputation
  • universities and technical schools

Tier 4: community sources

[edit source]

Use with caution and verify where possible:

  • moderated technical forums with established expertise and peer review
  • blogs by individuals with verifiable technical credentials
  • technical videos backed by written documentation
  • collaborative community documentation projects

Evaluating a source

[edit source]

Ask:

  • Does the author have relevant technical experience, or industry background?
  • Can the claims be checked against other sources?
  • Does it give detailed procedures with specific values, and appropriate safety warnings?
  • Does it cite the original documentation?
  • Does it correct its mistakes?
  • For community sources: have other experts reviewed it, and does the source have a record of accuracy?

Specific source types

[edit source]

Service manuals

[edit source]

Original manufacturer documentation is the best source.

Highly reliable:

  • official factory service manuals
  • authorised dealer training material
  • factory service bulletins and updates
  • licensed third-party service documentation

Use with verification:

  • scans of uncertain provenance
  • translations of foreign-language manuals
  • manuals reconstructed from several sources
  • community-written service guides

Technical specifications

[edit source]

Primary sources are original component datasheets, system specification sheets, engineering drawings and schematics, and factory test procedures. Secondary sources are technical reference books, industry standards documents, specifications cross-referenced from several sources, and verified community measurements.

Historical information

[edit source]

For dates, production numbers and history, the authoritative sources are company annual reports and press releases, dated patent filings, contemporary industry publications, and museum and archive collections. Supporting sources are period technical journalism, interviews with the original engineers, community documentation projects, and examination of the hardware itself (date codes, board revisions).

Manufacturer considerations

[edit source]

Active companies

[edit source]

A manufacturer still in business may keep legacy product information and support documentation on its website, and may issue official statements. Documentation it has authorised is a licensed source.

Defunct companies

[edit source]

For companies no longer trading, look to archive collections (museums, libraries and private collections), documentation from former engineers and technicians, companies that acquired the assets or rights, and community preservation projects.

Changes of ownership

[edit source]

When a company has changed hands, the documentation rights may belong to the acquirer, to a licensed distributor, or to several different owners after a partial acquisition. Some older documentation may be in the public domain.

Regional and language considerations

[edit source]

Hardware was often changed for different markets, and specifications differ between regions (mains voltage, video standard). Check which regional version a source describes.

For non-English sources, use a qualified technical translator where possible, have translations checked by a native speaker with technical knowledge, compare sources in different languages, and make sure technical terms are translated correctly.

Online sources

[edit source]

Signs that a website is reliable: clear authorship and contact information, regular maintenance, a way to report corrections, and links to authoritative sources.

Warning signs: anonymous authorship, no source attribution, out-of-date information, no way to report corrections, and heavy advertising or commercial focus.

For web pages that may disappear, use the Wayback Machine, institutional digital archives and community mirror sites, and keep local copies of important documents. Manuals can be uploaded here; see Help:Uploading service manuals.

Forums and community experts

[edit source]

The best forums are moderated, long established, encourage citation, correct mistakes, and have expert moderators. Look for claims confirmed by several experts, references to the original documentation, detailed procedures with specific measurements, and a record of accuracy.

A reliable community expert has relevant professional experience, is respected by other members, is consistently accurate, cites authoritative sources, and admits and corrects mistakes.

Special circumstances

[edit source]

Poorly documented hardware

[edit source]

Where documentation is unclear or missing, cross-check every source you can find, take the most conservative interpretation when sources conflict, look for agreement among several experts, and test procedures and specifications yourself where it is safe to do so.

Proprietary information

[edit source]

Proprietary technical data may be used when the rights holder has officially released it, when it was obtained legally by reverse engineering, when it was released in the public interest, or when it has become public with time.

Conflicting sources

[edit source]

When authoritative sources disagree:

  • prefer the higher-tier source
  • more recent information may supersede older data
  • check whether each source covers a different board revision or region
  • ask recognised technical experts
  • measure it yourself where possible

Unreliable sources

[edit source]

These are generally unreliable for technical documentation:

  • social media posts, unless from verified official accounts
  • sales listings on eBay, Amazon or elsewhere
  • unmoderated wikis without editorial oversight
  • anonymous technical claims
  • clickbait sites

Treat information with caution if it lacks specific technical detail, makes claims without evidence, contains obvious technical errors or inconsistencies, does not cite original sources, exaggerates, or has a commercial bias.

Verification

[edit source]
  • Find the same information in independent sources.
  • Check that the specification makes technical sense and fits the known timeline.
  • Check that the source covers the same machine and revision. A manual for a sibling model is not a source for its neighbour.
  • Ask technical experts to review doubtful information.
  • Where possible, test it directly: measure the voltages, try the procedure on real hardware, test the components, and confirm that safety procedures work.

Citing

[edit source]

Give the full publication details, say how others can get the same source, identify the version or revision, and add an archive link where the source may disappear. Note any known limitations of the source. See RetroTechCollection:Citing sources.

See also

[edit source]