Lauren Willihnganz
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Note Insights Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    Forensic Report: ... =============== | Identity of the reporting agency | MDEF | |----------------------------------------|--------------------------------| | Case identifier | Forensics of the Obsolescence | | Identity of the submitter | Agnes, Max, Toni, Yetkin, Francesco, Lo | | Date of receipt | 19/11/2025 | | Date of report | 22/11/2015 | ## Examination ### PC Desktop **Serial number:** SF382 **Brand:** Intel **Colour:** Black ::: | Picture | Component | Serial Number | Brand | Specifications | Made in| | -------- | -------- | -------- | ------- | ------- | -- | |![IMG_9477 Large](https://hackmd.io/_uploads/BJGSDhal-e.jpg)| PC Shell | SF382 | Antec| ATX Mid-Tower | China |![d801c96f-714d-46f0-967b-787320951287 2](https://hackmd.io/_uploads/rJ-hD36lZx.jpg)| Fan | -| Antec | Power and speed cables |China | ![IMG_9689 Large](https://hackmd.io/_uploads/SJxnF2pgZe.jpg)| Speaker | -| Antec | (two cables) |China |![IMG_9488 2 Large](https://hackmd.io/_uploads/HyzE526gZg.jpg)| Power Suply | DT090BCRX0022430| Antec | 380W 100V-240V 8A-4A 47 Hz-63Hz |China |![IMG_9532 2 Large](https://hackmd.io/_uploads/Sy-i0ybZbe.jpg) | Mother Board | 6627GE12B4F0| Intel | nylon PA66, ABS |China | ![IMG_9526 Large](https://hackmd.io/_uploads/B13QXlZb-e.jpg)| CD Player | 909LAYA324090| LC | Laser class1, SATA, 5V 20.A/ 12V 2.5A |Korea |![IMG_9566 Large](https://hackmd.io/_uploads/BJS5Qe-WWl.jpg)| Hard Disc | CFFD9UKA| Hitachi Global | Model: HDT722525VLSA80 |Thailand ## Forensic Questions **What does it do?** This PC desktop is performed as a personal computer for home or office use. *Key Components* -Run Windows XP or early Windows Vista efficiently -Handle multitasking better than single-core PCs (thanks to quad-core CPU) -Store large amounts of data on 250GB HDD -Play DVDs and early-to-mid 2000s PC games -Connect via USB, Ethernet, and audio ports -Quad-core capability means it could run multiple programs simultaneously with less slowdown. *Simplified Operational Flow* 1. Power on → BIOS checks hardware 2. CPU starts → quad-core processor runs multiple tasks at once 3. Operating system loads from the hard drive. 4. Desktop ready → user can run programs, browse the web, or access files. **How does it work?** CPU (Computation Processing Unit): Quad-core processor RAM: 1–4GB DDR2 Storage: 250GB SATA HDD OS: Windows XP Power supply: 380W **How is it built?** Case prepared → frame and panels ready. Motherboard installed → CPU, RAM, and chipsets attached. Power supply added → connected to motherboard. Drives installed → 250GB HDD and DVD/CD drive placed. Cables and fans connected → power, data, and airflow set up. Side panels on & tested → BIOS checked and OS installed. **Why it failed, or it wasn't used anymore?** Outdated Technology: The system can’t keep up with modern software, web standards, or operating systems, even though the CPU, RAM, and drives still function. Limited Compatibility: Ports, memory capacity, and hard drive speed make it impractical for today’s tasks, so users abandoned it in favor of newer machines. ## Steps taken 1. Open the case – Unscrew and slide out the side panels. 2. Remove the fan – Take out the CPU or case fan for inspection. 3. Remove the power supply – Unscrew and disconnect it from the case and motherboard. 4. Remove front panel components – Detach the power/reset buttons, USB ports, and front audio connections. 5. Remove the optical drive – Unscrew and slide out the CD/DVD reader. 6. Remove the motherboard – Unscrew it from the case and carefully lift it out. 7. Start testing individual components – Power supply, drives, RAM, CPU, etc., to ensure they work. <div style="padding:56.25% 0 0 0;position:relative;"><iframe src="https://player.vimeo.com/video/1139856524?badge=0&amp;autopause=0&amp;player_id=0&amp;app_id=58479" frameborder="0" allow="autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share" referrerpolicy="strict-origin-when-cross-origin" style="position:absolute;top:0;left:0;width:100%;height:100%;" title="unpacking tech system"></iframe></div><script src="https://player.vimeo.com/api/player.js"></script> ## Testing After the disassembly process, we meticulously examined each individual component. Utilizing a precision lab power supply and a high-resolution multimeter, we conducted comprehensive tests to determine the optimal voltage required for each component's functionality. ## Examination ### HP SERIES5 527SF **Serial number:** **Brand:** HP **Model:** SERIES5 527SF **Colour:** Black ::: | Picture | Component | Serial number | Quantity | Specifications | Made in | | -------- | -------- | -------- | ------- | ------- | -- | |![IMG_9443 Large](https://hackmd.io/_uploads/rkMG5g-bbe.jpg) | Display | 3CM3510JRC | 1| Backlight, Polarized filter, TFT, Liquid Crystal, Color Filter, Polarized filter, cover glass | China |![IMG_9473 Large](https://hackmd.io/_uploads/Hk_72xZbWg.jpg) | Buttons | R017117810263| 1 | 134x9mm, 3.3V, PBC |China ![IMG_9459 Large](https://hackmd.io/_uploads/rJhY3eWZZe.jpg)| Mother Board| R017122811011| 1 |MediaTek Micro controller, pcv |Korea |![IMG_9465 Large](https://hackmd.io/_uploads/r1pvneWWbl.jpg)| LCD control board |EALLBY4010A2| 1 | 1920x1080 pixel |China ## Forensic Questions **What does it do?** Display (LCD Panel): The display is the part that shows the final image. It receives the video signals and transforms them into visible light using liquid crystals and color filters. Buttons / Control Panel: The buttons allow the user to interact with the monitor: turning it on and off, navigating menus, changing brightness, etc. They serve as the interface between the user and the electronics. Motherboard (Main Logic Board): This board is the “brain” of the monitor. It processes the incoming video signal (HDMI/VGA), manages power distribution, stores firmware, and controls all the internal communication between components. LCD Control Board (T-CON): The T-CON board converts the processed video data from the motherboard into high-speed timing and voltage signals that drive the pixels of the LCD. **How does it work?** Display (LCD Panel): The LCD works by using a backlight that produces white light, which passes through layers of liquid crystals. When voltage is applied to specific areas, the crystals twist to let more or less light through. Combined with RGB filters, this creates colored pixels that form the image. Buttons / Control Panel: The buttons are simple tactile switches. When they are pressed, they complete a small electrical circuit on a secondary PCB. This sends a low-voltage signal to the motherboard, which interprets the action (power on, menu, etc.). Motherboard: It receives the video input, decodes it, and converts it into a digital format suitable for the LCD. It regulates voltages, controls the backlight, and sends structured video data to the T-CON board. It does this using integrated circuits, memory, and power regulators. LCD Control Board (T-CON): The T-CON organizes the timing of the image by sending high-speed pulses to row and column drivers. These signals determine when each pixel should activate and how much voltage it should receive to twist the liquid crystals. **How is it built?** The monitor is built as a compact layered system. At the front, the LCD panel is made of thin glass layers with liquid crystals inside, supported by a plastic and metal frame. Behind it, there is a backlight that provides the illumination needed for the image. All the electronics are mounted behind the screen. The main board processes the video signal, and a smaller control board sends the timing signals to the pixels. These boards are connected with ribbon cables and fixed to the back housing. The buttons are placed on a small board along the edge of the frame and simply send signals when pressed. Overall, the monitor is assembled by stacking the screen, the light system, and the electronic boards together in a compact, enclosed structure. **Why it failed, or it wasn't used anymore?** The monitor had been physically damaged — the LCD panel was completely broken, likely from a fall or a strong impact. Because the glass was shattered, it could no longer display an image. However, all the internal components such as the buttons, motherboard, and control board were still functional. The monitor was discarded only because the screen itself was destroyed. ## Steps taken 1. Cleaned the dust off the printer and brought it to the MDEF room 2. Disassembled using our toolbox 3. Laid out all parts individually and documented. ![IMG_9612 Large](https://hackmd.io/_uploads/BJS7aeZbWg.jpg) ## Testing After the disassembly process, we meticulously examined each individual component. Utilizing a precision lab power supply and a high-resolution multimeter, we conducted comprehensive tests to determine the optimal voltage required for each component's functionality.

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully