Welcome to my site … made by a homecomputer enthusiast of the 80s for just those and who are simply interested in it 😉
This is not only about the famous “bread box”, the Commodore C64, but generally about 8-bit home computers of the 80s … the time when we (now about 45/50 years old) had the first contact with computers.
So besides the Commodores, it’s also about the Schneider, Amstrad, Sinclair, Atari, Apple
So have fun exploring the site!
Who we are
The addresses of our website are: https://www.homecomputerguy.de, https://homecomputerguy.de, https://www.retroguy.de, https://retroguy.de.
What personal information we collect and why we collect it
COMMENTS
When visitors post comments on the site, we collect the information displayed in the comment form, the visitor’s IP address and the user-agent string (which identifies the browser) to assist in detecting spam.
Your email address can be used to create an anonymous string (also called a hash) and send it to the Gravatar service to check if you are using it. The Gravatar service privacy policy can be found here: https://automattic.com/privacy/. After your comment is posted, your profile picture will be publicly visible in the context of your comment.
MEDIA
If you are a registered user and upload photos to this site, you should avoid uploading photos with an EXIF GPS location. Visitors to this site may download photos stored on this site and extract their location information.
Contact Forms
COOKIES
When you write a comment on our website, this may be a consent to store your name, e-mail address and website in cookies. This is a convenience feature so that you don’t have to re-enter all this information when you write another comment. These cookies are stored for one year.
If you have an account and log in to this website, we will set a temporary cookie to determine if your browser accepts cookies. This cookie does not contain any personal information and is discarded when you close your browser.
When you log in, we will set some cookies to store your login information and display options. Login cookies expire after two days and display option cookies expire after one year. If you select “Stay signed in” when you sign in, your sign-in will be maintained for two weeks. When you log out of your account, the login cookies are deleted.
When you edit or publish an article, an additional cookie is stored in your browser. This cookie does not contain any personal information and only refers to the post ID of the article you are editing. The cookie expires after one day.
Embedded content from other websites
Contributions on this website may contain embedded content (e.g. videos, pictures, articles etc.). Embedded content from other websites behaves exactly as if the visitor had visited the other website.
These sites may collect information about you, use cookies, embed additional third-party tracking services, and record your interaction with that embedded content, including your interaction with the embedded content if you have an account and are logged on to that site.
Analysis Services
WHO WE SHARE YOUR DATA WITH
HOW LONG WE STORE YOUR DATA
If you write a comment, it will be saved including metadata for an unlimited time. This way we can automatically detect and release follow-up comments instead of having to keep them in a moderation queue.
For users who register on our website, we also store the personal information they provide in their user profiles. All users can view, change or delete their personal information at any time (the user name cannot be changed). Website administrators can also view and change this information.
WHAT RIGHTS YOU HAVE TO YOUR DATA
If you have an account on this website or have written comments, you can request an export of your personal data from us, including all the data you have given us. In addition, you can request the deletion of all personal data that we have stored about you. This does not include data that we have to keep due to administrative, legal or security reasons.
WHERE WE SEND YOUR DATA
Visitor comments could be examined by an automated spam detection service.
This feature only records activities of a site’s registered users, and the retention duration of activity data will depend on the site’s plan and activity type.
Data Used: To deliver this functionality and record activities around site management, the following information is captured: user email address, user role, user login, user display name, WordPress.com and local user IDs, the activity to be recorded, the WordPress.com-connected site ID of the site on which the activity takes place, the site’s Jetpack version, and the timestamp of the activity. Some activities may also include the actor’s IP address (login attempts, for example) and user agent.
Activity Tracked: Login attempts/actions, post and page update and publish actions, comment/pingback submission and management actions, plugin and theme management actions, widget updates, user management actions, and the modification of other various site settings and options. Retention duration of activity data depends on the site’s plan and activity type. See the complete list of currently-recorded activities (along with retention information).
Data Synced (?): Successful and failed login attempts, which will include the actor’s IP address and user agent.
Image views are only recorded if the site owner, has explicitly enabled image view stats tracking for this feature via the jetpack_enable_carousel_stats filter.
Data Used: If image view tracking is enabled, the following information is used: IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code.
Activity Tracked: Image views.
This feature is only accessible to users logged in to WordPress.com.
Data Used: In order to process a comment like, the following information is used: WordPress.com user ID/username (you must be logged in to use this feature), the local site-specific user ID (if the user is signed in to the site on which the like occurred), and a true/false data point that tells us if the user liked a specific comment. If you perform a like action from one of our mobile apps, some additional information is used to track the activity: IP address, user agent, timestamp of event, blog ID, browser language, country code, and device info.
Activity Tracked: Comment likes.
Data Used: If Akismet is enabled on the site, the contact form submission data — IP address, user agent, name, email address, website, and message — is submitted to the Akismet service (also owned by Automattic) for the sole purpose of spam checking. The actual submission data is stored in the database of the site on which it was submitted and is emailed directly to the owner of the form (i.e. the site author who published the page on which the contact form resides). This email will include the submitter’s IP address, timestamp, name, email address, website, and message.
Data Synced (?): Post and post meta data associated with a user’s contact form submission. If Akismet is enabled on the site, the IP address and user agent originally submitted with the comment are synced, as well, as they are stored in post meta.
Data Used: An iframe is inserted into the page, using an HTTP connection. The iframe is governed by Giphy’s privacy policy.
Activity Tracked: We don’t track any activity. For details of what Giphy tracks, refer to their privacy policy.
Data Used: This feature will send a hash of the user’s email address (if logged in to the site or WordPress.com — or if they submitted a comment on the site using their email address that is attached to an active Gravatar profile) to the Gravatar service (also owned by Automattic) in order to retrieve their profile image.
Data Used: In order to record page views via WordPress.com Stats (which must be enabled for page view tracking here to work) with additional loads, the following information is used: IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code.
Activity Tracked: Page views will be tracked with each additional load (i.e. when you scroll down to the bottom of the page and a new set of posts loads automatically). If the site owner has enabled Google Analytics to work with this feature, a page view event will also be sent to the appropriate Google Analytics account with each additional load.
Data Used: Commenter’s name, email address, and site URL (if provided via the comment form), timestamp, and IP address. Additionally, a jetpack.wordpress.com IFrame receives the following data: WordPress.com blog ID attached to the site, ID of the post on which the comment is being submitted, commenter’s local user ID (if available), commenter’s local username (if available), commenter’s site URL (if available), MD5 hash of the commenter’s email address (if available), and the comment content. If Akismet (also owned by Automattic) is enabled on the site, the following information is sent to the service for the sole purpose of spam checking: commenter’s name, email address, site URL, IP address, and user agent.
Activity Tracked: The comment author’s name, email address, and site URL (if provided during the comment submission) are stored in cookies. Learn more about these cookies.
Data Synced (?): All data and metadata (see above) associated with comments. This includes the status of the comment and, if Akismet is enabled on the site, whether or not it was classified as spam by Akismet.
This feature is only accessible to users logged in to WordPress.com.
Data Used: In order to process a post like action, the following information is used: IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID (on which the post was liked), post ID (of the post that was liked), user agent, timestamp of event, browser language, country code.
Activity Tracked: Post likes.
Activity Tracked: We don’t track anything. Refer to the Mapbox privacy policy for details of any activity they track.
Data Used: A visitor’s preference on viewing the mobile version of a site.
Activity Tracked: A cookie (akm_mobile) is stored for 3.5 days to remember whether or not a visitor of the site wishes to view its mobile version. Learn more about this cookie.
This feature is only accessible to registered users of the site who are logged in to WordPress.com.
Data Used: IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code. Some visitor-related information or activity may be sent to the site owner via this feature. This may include: email address, WordPress.com username, site URL, email address, comment content, follow actions, etc.
Activity Tracked: Sending notifications (i.e. when we send a notification to a particular user), opening notifications (i.e. when a user opens a notification that they receive), performing an action from within the notification panel (e.g. liking a comment or marking a comment as spam), and clicking on any link from within the notification panel/interface.
Data Used: A pin is embedded using JavaScript resources loaded from Pinterest directly.
Activity Tracked: We don’t track any activity. For details of what Pinterest tracks, refer to their privacy policy.
Data Used: In order to check login activity and potentially block fraudulent attempts, the following information is used: attempting user’s IP address, attempting user’s email address/username (i.e. according to the value they were attempting to use during the login process), and all IP-related HTTP headers attached to the attempting user.
Activity Tracked: Failed login attempts (these include IP address and user agent). We also set a cookie (jpp_math_pass) for 1 day to remember if/when a user has successfully completed a math captcha to prove that they’re a real human. Learn more about this cookie.
Data Synced (?): Failed login attempts, which contain the user’s IP address, attempted username or email address, and user agent information.
Data Used: When official sharing buttons are active on the site, each button loads content directly from its service in order to display the button as well as information and tools for the sharing party. As a result, each service can in turn collect information about the sharing party. When a non-official Facebook or a Pinterest sharing button is active on the site, information such as the sharing party’s IP address as well as the page URL will be available for each service, so sharing counts can be displayed next to the button. When sharing content via email (this option is only available if Akismet is active on the site), the following information is used: sharing party’s name and email address (if the user is logged in, this information will be pulled directly from their account), IP address (for spam checking), user agent (for spam checking), and email body/content. This content will be sent to Akismet (also owned by Automattic) so that a spam check can be performed. Additionally, if reCAPTCHA (by Google) is enabled by the site owner, the sharing party’s IP address will be shared with that service. You can find Google’s privacy policy here.
Data Used: To initiate and process subscriptions, the following information is used: subscriber’s email address and the ID of the post or comment (depending on the specific subscription being processed). In the event of a new subscription being initiated, we also collect some basic server data, including all of the subscribing user’s HTTP request headers, the IP address from which the subscribing user is viewing the page, and the URI which was given in order to access the page (REQUEST_URI and DOCUMENT_URI). This server data used for the exclusive purpose of monitoring and preventing abuse and spam.
Activity Tracked: Functionality cookies are set for a duration of 347 days to remember a visitor’s blog and post subscription choices if, in fact, they have an active subscription.
Data Used: IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code. Important: The site owner does not have access to any of this information via this feature. For example, a site owner can see that a specific post has 285 views, but he/she cannot see which specific users/accounts viewed that post. Stats logs — containing visitor IP addresses and WordPress.com usernames (if available) — are retained by Automattic for 28 days and are used for the sole purpose of powering this feature.
Activity Tracked: Post and page views, video plays (if videos are hosted by WordPress.com), outbound link clicks, referring URLs and search engine terms, and country. When this module is enabled, Jetpack also tracks performance on each page load that includes the JavaScript file used for tracking stats. This is exclusively for aggregate performance tracking across Jetpack sites in order to make sure that our plugin and code is not causing performance issues. This includes the tracking of page load times and resource loading duration (image files, JavaScript files, CSS files, etc.). The site owner has the ability to force this feature to honor DNT settings of visitors. By default, DNT is currently not honored.
Information according to § 5 Telemediengesetz (TMG):
Jürgen Wich
e-mail: juergen.wich[-at-]web.de
Responsible for the content is according to § 55 Abs. 2 Rundfunkstaatsvertrag (RStV)
Jürgen Wich
e-mail: juergen.wich[-at-]web.de
Exclusion of liability:
The content of our website was created with the greatest possible care. However, we do not guarantee that this content is correct, complete, up-to-date or that it is pleasing. According to § 7 paragraph 1 TMG we are responsible for the content, even if it was ordered.
In accordance with §§ 8, 9 and 10 TMG, we are not obliged to monitor information from third parties that has been transmitted or stored or to investigate circumstances that indicate illegal activities.
This does not affect our obligation to block or remove information, which is based on general laws.
However, we are only liable at the moment we become aware of a concrete violation of rights. Then an immediate removal of the corresponding content will be carried out.
Our website contains links to external websites of third parties, but we have no influence on their contents. It is therefore not possible for us to accept any liability for these contents.
The respective provider/operator of the respective website is always responsible for this. At the time of linking, we check the linked websites for a possible legal violation in full width.
However, we cannot be expected to constantly monitor the content of the linked Internet pages without a concrete indication. However, if we become aware of an infringement, we will immediately remove the corresponding link, we can do that.
3rd copyright
The contents of our website are, as far as possible, protected by copyright. It requires a written permission of the creator for the person who duplicates, edits, distributes or uses the contents.
The downloading and copying of our internet site is to be permitted in writing by us for both private and commercial use. We would like to point out that with regard to the contents of our Internet site, insofar as they were not created by us, we have at all times observed the copyright of third parties.
If you would inform us that you have nevertheless found a copyright infringement, we would appreciate this very much. Then we can remove the corresponding content immediately and would no longer infringe the copyright.
Our website can be used regularly without the provision of personal data. Should such data (e.g. name, address or e-mail) be collected after all, this is done voluntarily or only with your and our express consent.
The transmission of data on the Internet is subject to security vulnerabilities. It is therefore possible for third parties to gain access to this data. A complete protection is not possible, although commendable.
We object at this point to the use of our contact data to send us unsolicited advertising/information material/spam mails. Should this happen, we would have to consider legal action.
Indication of the source: Flegl Rechtsanwälte GmbH
With the ZX Spectrum Plus, the ZX is finally growing up! And yet it was the beginning of the end for the British company Sinclair as a legendary computer manufacturer. Because in 1986 the British competitor Amstrad acquired the trademark rights for Sinclair and released with the Spectrum +2 and +3 two successors of the 8-bit computer with 128kB memory – one with built-in cassette recorder drive and the other with floppy disk drive. Thus Amstrad took over the design from its own computer line, which also had a built-in cartridge drive or floppy disk drive.
I am especially proud to have a Spectrum +2A in my collection, because this model was not very widespread in Germany.
Continue reading “Sinclair 128K ZX Spectrum +2”
]
The Apple IIc or //c was the portable version of the famous Apple II computer (the c stands for compact) and was launched in 1984. That was the same year that Apple also launched the first Macintosh pushed by Steve Jobs. Two camps had formed within the company: On the one hand, the developers around Steve Wozniak with the extremely successful Apple II and on the other hand Steve Jobs, who was determined to realize his vision of the Macintosh – a computer with a graphical interface and mouse. With the Apple //c, the Apple II developers countered with a stylish, compact computer that was fully compatible with Apple II. The computer also looked good on the boss’s desk. However, the device cannot be called a laptop, as the screen was external and the computer had no battery.
Continue reading “The Apple //c – The Cute One”
