Diferencias

Muestra las diferencias entre dos versiones de la página.

--- en:hardware:perifericos:flashdisk [2026/05/13 18:39] – creado jesus
+++ en:hardware:perifericos:flashdisk [2026/05/15 06:11] (actual) – jesus
@@ Línea 1: / Línea 1: @@
 ~~NOTOC~~
-====== Flash Drive ======
 <html>
@@ Línea 19: / Línea 18: @@
   .pcw-subtitle-box { background-color: #00ff00; color: #000b00 !important; padding: 5px 12px; font-weight: bold; display: inline-block; margin: 20px 0 15px 0; text-transform: uppercase; position: relative; z-index: 3; font-family: 'Courier New', Courier, monospace; }
-  /* --- RETRO DATA SHEET --- */
+  /* --- RETRO TECHNICAL DATASHEET --- */
   .tech-info-box { border: 1px dashed #004400; padding: 15px; margin-bottom: 20px; background: rgba(0, 8, 0, 0.5); }
   .tech-info-row { display: flex; border-bottom: 1px solid rgba(0, 68, 0, 0.3); padding: 4px 0; font-size: 0.95em; }
@@ Línea 27: / Línea 26: @@
   .tech-value a { color: #00ff00 !important; text-decoration: underline !important; }
-  /* --- CRT SCREEN FILE WITH WHITE TEXT --- */
+  /* --- CRT ON-SCREEN FILE WITH WHITE TEXT --- */
   .pcw-terminal-file { border: 1px solid #00ff00; background: rgba(0, 15, 0, 0.9); padding: 15px; margin: 20px 0; font-family: monospace; white-space: pre-wrap; font-size: 0.9em; color: #ffffff !important; box-shadow: 0 0 15px rgba(0, 255, 0, 0.2); }
@@ Línea 40: / Línea 39: @@
   .img-label { font-size: 0.75em; color: #00aa00; margin-top: 8px; font-weight: bold; text-transform: uppercase; letter-spacing: 0.5px; }
+  /* --- LIGHTBOX MODAL SETUP: STRICT NATIVE REAL SIZE WITH SCROLL --- */
   .modal-pcw { display: none; position: fixed; z-index: 9999; top: 0; left: 0; width: 100%; height: 100%; background-color: rgba(0, 10, 0, 0.95); overflow: auto; }
   .modal-pcw:target { display: block; text-align: center; }
   .close-overlay { display: inline-block; min-width: 100%; min-height: 100%; padding: 40px; box-sizing: border-box; text-decoration: none !important; cursor: zoom-out; vertical-align: middle; }
-  .modal-content { max-width: 90% !important; max-height: 85vh !important; border: 4px solid #00ff00; box-shadow: 0 0 50px rgba(0, 255, 0, 0.5); margin: 5vh auto; display: inline-block; }
+  .modal-content { border: 4px solid #00ff00; box-shadow: 0 0 50px rgba(0, 255, 0, 0.5); margin: 5vh auto; display: inline-block; max-width: none !important; max-height: none !important; height: auto !important; }
 </style>
-<!-- INTERACTIVE MODAL LAYER (LIGHTBOX) -->
+<!-- INTERACTIVE MODAL LIGHTBOX LAYERS -->
 <div id="pfd1" class="modal-pcw"><a href="#close" class="close-overlay"><img class="modal-content" src="/lib/exe/fetch.php?media=hardware:perifericos:CirtechFlashDisk_1.jpg"></a></div>
 <div id="pfd2" class="modal-pcw"><a href="#close" class="close-overlay"><img class="modal-content" src="/lib/exe/fetch.php?media=hardware:perifericos:CirtechFlashDisk_2.jpg"></a></div>
@@ Línea 53: / Línea 53: @@
 <div id="ppcbabove" class="modal-pcw"><a href="#close" class="close-overlay"><img class="modal-content" src="/lib/exe/fetch.php?media=hardware:perifericos:CirtechFlashDisk_PCB_Above.jpg"></a></div>
 <div id="ppcbbelow" class="modal-pcw"><a href="#close" class="close-overlay"><img class="modal-content" src="/lib/exe/fetch.php?media=hardware:perifericos:CirtechFlashDisk_PCB_Below.jpg"></a></div>
+<div id="pfd3" class="modal-pcw"><a href="#close" class="close-overlay"><img class="modal-content" src="/lib/exe/fetch.php?media=hardware:esquemas:CirtechFlashDisk_3.jpg"></a></div>
 <div class="pcw-monitor-ultra">
@@ Línea 58: / Línea 59: @@
   <div class="tech-info-box">
-    <div class="tech-info-row"><div class="tech-label">Company</div><div class="tech-value"></html>[[..companias:cirtech|Cirtech]]<html></div></div>
+    <div class="tech-info-row"><div class="tech-label">Company</div><div class="tech-value"></html>[[en:companias:cirtech|Cirtech]]<html></div></div>
-    <div class="tech-info-row"><div class="tech-label">Distributor</div><div class="tech-value"></html>[[..companias:cirtech|Cirtech]]<html></div></div>
+    <div class="tech-info-row"><div class="tech-label">Distributor</div><div class="tech-value"></html>[[en:companias:cirtech|Cirtech]]<html></div></div>
     <div class="tech-info-row"><div class="tech-label">Year</div><div class="tech-value">1994</div></div>
-    <div class="tech-info-row"><div class="tech-label">Hardware</div><div class="tech-value">PCW Expansion Bus</div></div>
+    <div class="tech-info-row"><div class="tech-label">Hardware</div><div class="tech-value">PCW expansion bus</div></div>
     <div class="tech-info-row"><div class="tech-label">Compatibility</div><div class="tech-value">PCW 8256 - PCW 8512</div></div>
     <div class="tech-info-row"><div class="tech-label">Language</div><div class="tech-value">English</div></div>
-    <div class="tech-info-row"><div class="tech-label">Price</div><div class="tech-value">England: 1024k - £65.00 & 2048k - £95.00</div></div>
+    <div class="tech-info-row"><div class="tech-label">Price</div><div class="tech-value">UK: 1024k - £65.00 & 2048k - £95.00</div></div>
-    <div class="tech-info-row"><div class="tech-label">Status</div><div class="tech-value"></html>[[..preservado|Preserved]]<html></div></div>
+    <div class="tech-info-row"><div class="tech-label">Status</div><div class="tech-value"></html>[[en:preservado|Preserved]]<html></div></div>
   </div>
-  <div class="pcw-subtitle-box">Device View</div>
+  <div class="pcw-subtitle-box">Device Overview</div>
   <div class="drive-grid-container">
     <div class="drive-card">
       <div class="drive-gallery">
-        <div class="img-frame"><a href="#pfd1"><img src="/lib/exe/fetch.php?media=hardware:perifericos:CirtechFlashDisk_1.jpg"></a><span class="img-label">Front Unit</span></div>
+        <div class="img-frame"><a href="#pfd1"><img src="/lib/exe/fetch.php?media=hardware:perifericos:CirtechFlashDisk_1.jpg"></a><span class="img-label">Front View</span></div>
-        <div class="img-frame"><a href="#pfd2"><img src="/lib/exe/fetch.php?media=hardware:perifericos:CirtechFlashDisk_2.jpg"></a><span class="img-label">Perspective Unit</span></div>
+        <div class="img-frame"><a href="#pfd2"><img src="/lib/exe/fetch.php?media=hardware:perifericos:CirtechFlashDisk_2.jpg"></a><span class="img-label">Perspective View</span></div>
       </div>
     </div>
@@ Línea 79: / Línea 80: @@
   <div class="content-body">
-    <p>The Flash Disks are a family of external storage interfaces based on Flash memory. It is an add-on for the PCW no larger than a matchbox. In fact, the largest component of the flash drive is the connector that plugs into the PCW expansion port at the back.</p>
+    <p>The Flash Disk is a family of external storage interfaces built upon Flash memory components. This upgrade module for PCW computers is no larger than a standard matchbox. In fact, the largest physical component of the entire flash layout is the custom edge connector that links straight into the rear PCW expansion port.</p>
-    <p>Cirtech was the first company to offer this brilliant piece of hardware, incredibly fast, and at a low cost, allowing programs to boot from ROM. It could be purchased in 1024k and 2048k versions.</p>
+    <p>Cirtech stood as the pioneer enterprise to supply this outstanding hardware solution, achieving lightning-fast transfer speeds at a highly budget-friendly cost, allowing applications to boot directly from ROM structures. It was distributed in two independent hardware variations: 1024k and 2048k capacities.</p>
-    <p>The bank of small ROM chips it includes made it a revolutionary device for the PCW, if revolutionary is an appropriate word for a data drive containing no moving parts. It is a disk purely in the sense that part of the computer's internal memory information is named "Drive M:". ROM is a read-only memory and describes the peculiarity of this silicon chip. These flash drives contained a 1024k or 2048k chip.</p>
+    <p>The matrix of integrated mini ROM chips made this module a revolutionary storage solution for the PCW range—if "revolutionary" fits as an accurate label for a data storage peripheral that features no moving mechanical assemblies. It serves as a disk drive purely in the logic framework where parts of the active internal workstation environment recognize its memory pool as "Drive M:". ROM defines Read-Only Memory, describing the specialized trait of this raw silicon component array. These specific flash expansion cards housed either a 1024k or a 2048k chip layout.</p>
   </div>
-  <div class="pcw-subtitle-box">Circuit Board Captures (PCB)</div>
+  <div class="pcw-subtitle-box">PCB Board Layouts</div>
   <div class="drive-grid-container">
     <div class="drive-card">
       <div class="drive-gallery">
-        <div class="img-frame"><a href="#ppcbfront"><img src="/lib/exe/fetch.php?media=hardware:perifericos:CirtechFlashDisk_PCB_Front.jpg"></a><span class="img-label">PCB Front</span></div>
+        <div class="img-frame"><a href="#ppcbfront"><img src="/lib/exe/fetch.php?media=hardware:perifericos:CirtechFlashDisk_PCB_Front.jpg"></a><span class="img-label">PCB Component Side</span></div>
-        <div class="img-frame"><a href="#ppcbback"><img src="/lib/exe/fetch.php?media=hardware:perifericos:CirtechFlashDisk_PCB_Back.jpg"></a><span class="img-label">PCB Back</span></div>
+        <div class="img-frame"><a href="#ppcbback"><img src="/lib/exe/fetch.php?media=hardware:perifericos:CirtechFlashDisk_PCB_Back.jpg"></a><span class="img-label">PCB Solder Side</span></div>
         <div class="img-frame"><a href="#ppcbabove"><img src="/lib/exe/fetch.php?media=hardware:perifericos:CirtechFlashDisk_PCB_Above.jpg"></a><span class="img-label">PCB Top Profile</span></div>
         <div class="img-frame"><a href="#ppcbbelow"><img src="/lib/exe/fetch.php?media=hardware:perifericos:CirtechFlashDisk_PCB_Below.jpg"></a><span class="img-label">PCB Bottom Profile</span></div>
@@ Línea 96: / Línea 98: @@
   <div class="content-body">
-    <p>To explain the difference between the more well-known "ROM" and the more familiar "RAM" (Random Access Memory), think of household light switches: electrical switches. The "gates" inside RAM chips can be turned on and off as needed, but ROM chips are "trapped" in either the on or off position. While the analogy isn't completely exact, the Flash Drive can actually be reprogrammed using the "utility disk" floppy supplied with the hardware. A better comparison might be with switches that control a home video recorder or an alarm system: these are not permanent, but turning them off requires extra steps, meaning you have to reprogram their functions.</p>
+    <p>To break down the core difference between standard "ROM" arrays and the more household "RAM" architectures (Random Access Memory), consider traditional domestic wall switches: electrical toggle switches. The logical "gates" built inside RAM silicon can be flipped on and off dynamically as needed, whereas ROM chips remain hardwired and permanently "stuck" into an explicitly fixed menu of on or off positions. While this comparison is not perfectly seamless here, the storage architecture of this Flash Drive can actually be reflashed and updated utilizing the bundled "support disk" volume supplied alongside the hardware kit. Therefore, a superior comparison would link it to the control switches that govern a domestic VCR setup or an electronic alarm layout: these settings are not permanent, but resetting them requires deliberate extra steps, meaning you must reprogram their active roles manually.</p>
-    <p>The Flash Drive's ROM can hold data from two system boot floppy disks: one for LocoScript and one for CP/M. Once the data has been loaded, the PCW boots surprisingly fast—taking roughly a quarter of the time normally required to load a disk from drive A:. Because its switches are "trapped," the drive needs no power to preserve data, making it unaffected when turning off the PCW. The only drawback is that, while you can add extra files to the flash drive, you cannot alter or delete anything without clearing the chips completely to start over.</p>
+    <p>The embedded flash ROM layout can host raw volume data matching two separate bootable system disks simultaneously: a native LocoScript environment and a standard CP/M workspace. Once this image configuration has been written, the PCW boots up at a jaw-dropping speed—taking roughly a quarter of the time typically spent loading a physical diske volume via Drive A:. Its hardwired "stuck" switch architecture guarantees the system preserves its contents completely without drawing system power, remaining completely unaffected when you shut off the host PCW. The main structural constraint is that while you can add extra file streams to the active flash allocation, you cannot selectively alter or erase separate items without wiping the silicon clean to start over from scratch.</p>
-    <p>Therefore, Cirtech highlights that the boot startup configuration should be carefully chosen and tested before committing it to the flash drive. It should be a setup that you are sure of and unlikely to change—the implications for LocoScript users are detailed in the box below:</p>
+    <p>Consequently, Cirtech strongly advises that your master boot system setup should be thoroughly verified and benchmarked before committing its data to the flash array. It must mirror an configuration you are totally confident in and unlikely to modify soon—the operational effects for LocoScript operators are broken down inside the following console data table:</p>
   </div>
   <div class="pcw-terminal-file">
-[ REQUIREMENTS CONFIGURATION - LOCOSCRIPT ]
+[ REQUIREMENT PROFILE - LOCOSCRIPT ]
-LocoScript users stand to benefit the most from this high-tech innovation for the PCW, simply because a large LocoScript configuration takes too long to boot from floppy disks. However, it does demand some thought when designing the flash drive's boot system. The SETTINGS.STD file cannot be updated once it is on drive C:, so make sure it contains your ideal adjustments—and the same goes for the TEMPLATE.STD files that will be copied to drive M: at boot. Do not place the USERSPEL dictionary on the flash drive—keep copies on your data disks.
+LocoScript operators stand to gain the most from this advanced high-tech innovation for the PCW environment, simply because complex LocoScript configurations take an excessive amount of time to boot when pulled from standard floppy media. However, it demands careful planning when designing your master flash drive boot image. The master SETTINGS.STD file cannot be updated dynamically once it resides inside Drive C:, so ensure it reflects your ideal parameters beforehand—and the same rule governs the TEMPLATE.STD files destined to be duplicated onto Drive M: during system initialization. Do not place the USERSPEL spell-checking database on the flash drive memory—keep those archives stored on your active data floppy volumes instead.
-For LocoFile owners, the most exciting feature of the flash drive is the way it handles data files—they can be inspected on drive C: (though they cannot be altered). This means .DATA files should not be stored in the ROM folder if they are likely to change. On the other hand, however, it opens up the possibility of gaining instant access to large amounts of reference material. Insert this data into data files, but do not use the .DATA suffix—call them anything else instead; LocoFile will still recognize them. These files will not be copied to drive M:, though they will always be available on drive C:.
+For LocoFile owners, the most spectacular feature of this flash drive resides in how it manages database file structures—they can be indexed and audited straight from Drive C: (though they cannot be rewritten). This means that critical .DATA files should not be written into the ROM folder structure if they are expected to change. On the other hand, however, it unlocks immediate access loops to massive blocks of static reference materials. Inject these datasets into the structural folders, but strip away the conventional .DATA suffix—assign alternative extensions instead; LocoFile will still index them smoothly. These reference blocks will not be copied over to active RAM storage (Drive M:) during initialization, though they remain constantly accessible via ROM allocation (Drive C:).
   </div>
   <div class="content-body">
-    <p>The flash drive is only compatible with LocoScript version 3.06 onwards (plus the parallel development, version 2.56) and the latest CP/M versions (1.15 or 2.15 depending on the PCW model). You might, therefore, require an upgrade to use it. The flash drive is not compatible with Flipper, but there is no problem with The Network (as long as a "key" is used); the floppy disk will be inserted at boot since Cirtech complies with this requirement to fight piracy.</p>
+    <p>The master flash interface natively requires LocoScript version 3.06 or higher (along with its parallel system branch, version 2.56) and the newest CP/M builds (1.15 or 2.15 depending on your specific PCW computer model). You might, as a result, require a system upgrade pack to use it. The flash drive is structurally incompatible with Flipper utility extensions, but routes smoothly with The Network configurations (provided a proper "key" file is present); the copy-protected floppy media will be prompted at boot, as Cirtech abides by this standard to prevent illegal distribution.</p>
-    <p>As far as normal CP/M software is concerned, the general rule seems to be that if a program works under CP/M 1.15/2.15, it will work on the flash drive. There are only two exceptions to this: DiscKit (a modified version supplied by Cirtech) and the original Moonstone 2-in-1 program, but the latest version of 2-in-1 sold by Locomotive Software works fine.</p>
+    <p>Regarding standard production software under CP/M environments, the general rule dictates that if a program compiles and executes under CP/M 1.15/2.15, it will operate flawlessly from the flash storage pool. Only two known exceptions disrupt this ecosystem: DiscKit (which requires a custom-modified build distributed directly by Cirtech) and the primitive core edition of Moonstone 2-in-1—note that the newest revision of 2-in-1 published by Locomotive Software operates perfectly.</p>
-    <p>Money Manager needs a few changes in its configuration screen—instructions are given inside a "Read Me" file on the flash drive utility disk. These alterations are necessary because Money Manager normally uses its own special setup, the PROFILE.SUB file (plus a non-standard SUBMIT.COM), for an automatic startup. The point of the flash drive is that multiple CP/M programs will likely be installed, and not all of them can have their own auto-boot system.</p>
+    <p>Money Manager calls for minor alterations inside its primary environment parameters—the specific steps are bundled inside a "Read Me" file hosted on the flash drive companion disk. These tweaks are mandatory because Money Manager typically invokes its own unique environment mapping via a custom PROFILE.SUB file (alongside a non-standard SUBMIT.COM engine) for automated booting. The main intent of the flash drive is to allow several separate CP/M tools to coexist smoothly, and not every platform can enforce its own absolute auto-boot loop.</p>
   </div>
   <div class="pcw-terminal-file">
-[ THE FLASH DRIVE AND CP/M ]
+[ THE FLASH DRIVE ENGINE UNDER CP/M ]
-The flash drive installation procedure will not copy the PROFILE.SUB or SUBMIT.COM file unless instructed to do so, and the latter must be the standard version supplied for that specific PCW. However, the PROFILE.SUB can be written to satisfy your own requirements. Essentially, though, CP/M users could create a vast boot disk containing all their utilities and then have the programs stacked in a batch on the ROM drive. CP/M itself appears at boot and each program loads in a matter of seconds—at least as fast as it would from drive M:, for example.
+The automated installation suite of the flash unit will not transfer your PROFILE.SUB or SUBMIT.COM scripts unless explicitly instructed, and the latter must mirror the standard version distributed for that exact PCW workstation build. Nevertheless, the PROFILE.SUB script can be customized freely to meet your personal production criteria. Essentially, CP/M power users can build a massive, comprehensive boot image hosting all their essential utility suites and heavy application binaries stacked together within the master ROM sector. The CP/M console initializes instantly at boot, and each distinct application loads in a matter of seconds—matching or exceeding the data rates achieved when pulling blocks from virtual RAM storage (Drive M:).
-This rapid program access might suggest that The Network is redundant, but that is not the case: it should simply be used differently. In this context, the ROM drive acts as a hard disk, meaning that, apart from the MicroDesign 3 family, programs can be designated as "Transient"—there is no point in keeping them on drive M: when they can be called so quickly from the ROM.
+This hyper-fast binary retrieval loop might suggest that hardware networks like The Network become redundant, but that is not the case: they should simply be deployed differently. In this architectural context, the master ROM block acts like a hard disk drive; thus, with the exception of the MicroDesign 3 production family, applications can be designated as "Transient": there is no logical reason to keep them clogging up virtual RAM storage (Drive M:) when they can be called instantly from the ROM block.
   </div>
   <div class="content-body">
     <strong>Getting Started</strong>
-    <p>The installation procedure requires arranging several floppy drive setups on the computer. For single-drive machines (or those featuring a mix of 3" and 3.5" drives), you need to copy the utility disk to drive M: using COPYDISC, one of the supplied programs. On most twin-drive PCWs, it is placed in drive A: and the appropriate boot startup disk (or disks) are read from drive B:. A program called FCOPY then copies the files from the boot disk(s) onto the flash drive.</p>
+    <p>The primary installation routine demands matching several hardware drive assignments on the host machine. For single-drive computer models (or configurations running a mixed cluster of 3" and 3.5" mechanics), you must duplicate the companion master volume data onto RAM storage (Drive M:) utilizing COPYDISC, one of the bundled system utilities. On most dual-drive Amstrad PCW workstations, the master installer resides inside Drive A:, while the structural boot images are processed and read straight from Drive B:. An indexing system tool named FCOPY then writes the selected application files from the source floppy media directly onto the flash expansion block.</p>
-    <p>Next, you will see a "Space remaining" message—the value drops, obviously—as files are transferred. Do not exceed the flash drive's capacity limit (unlikely to affect the larger 2Mb model). If you exceed the limit, FCOPY simply stops copying files, but the load will remain incomplete and you will likely need to start over from scratch. This, however, is best avoided as it is a slow process. Once the first boot disk is complete, the alternate system can be added.</p>
+    <p>As this sequence unfolds, the system will prompt a live "Remaining Space" value—which falls predictably as files are written into memory. Be careful not to exceed the raw capacity limits of the flash device (a constraint highly unlikely to affect users operating the higher-end 2Mb expansion card model). If you cross this storage threshold, the FCOPY tool simply halts its data transfer; however, the resulting boot image will remain incomplete, and you will likely need to restart the entire formatting sequence from scratch. This scenario should be avoided whenever possible, as the manual raw block copy routine is a slow process. Once your primary boot disk profile is completely written, alternative operating systems can be appended.</p>
-    <p>The installation process does not automatically copy a SUBMIT.COM or PROFILE.SUB file—if one is needed, you can copy each separately using its full filename (for example: FCOPY B:SUBMIT.COM). The installation process is not ideal; it involves three programs and command lines instead of menu options.</p>
+    <p>The installation macro does not automatically copy across a SUBMIT.COM file or a PROFILE.SUB script—if your workflow requires them, you must copy each item manually using its complete file parameter path (e.g., typing: FCOPY B:SUBMIT.COM). The legacy installer interface is not the most refined suite, invoking three separate text-driven tools and command-line parameters rather than a clean menu-driven layout.</p>
-    <strong>Putting it to Use</strong>
+    <strong>Putting it into Production</strong>
-    <p>With the auto-boot switch set to "on", the PCW boots faster than you would think possible. You can select the alternate startup system by holding down [ALT] while powering on. If, however, you select LocoScript, you will notice that you now have a drive C:—the ROM drive—which shows not only the boot disk with LocoScript files but also the alternate CP/M boot system. This will clutter the disk on the manager screen, so set all CP/M files to "system" before installation (using SET.COM or a file manager utility) and you won't see them unless you request hidden files to be displayed.</p>
+    <p>With the physical auto-boot toggle switch set to "on", the Amstrad PCW fires up faster than you ever thought possible. You can manually launch your secondary alternative boot operating system by holding down the <kbd>ALT</kbd> key during the power-on sequence. If you select the primary LocoScript profile instead, you will notice the manager screen now lists an extra storage letter: Drive C:—the physical ROM volume. This directory displays not only your master LocoScript operating system layers but also your alternative CP/M system files. This will clutter up your main system document manager view; therefore, it is best to set all your CP/M environment files to "system" attribute status prior to installation (utilizing SET.COM or an equivalent file management tool), which hides them from sight unless you explicitly toggle the view to display "hidden" files.</p>
-    <p>LocoScript will not allow you to edit, save, or delete on drive C:, but you can copy files from it in the usual way and at least as fast as from drive M:.</p>
+    <p>LocoScript will strictly block any attempts to edit, save, or delete objects residing inside Drive C:, but you can copy individual file matrices out of it into other blocks using conventional methods—achieving transfer speeds that easily match virtual RAM disk performance (Drive M:).</p>
-    <p>CP/M is not as simple, however. Here, the ROM drive becomes drive A: and the normal floppy drive A: becomes drive C:—unless you are using the specially modified version of DiscKit, that is. This still names the floppy drives A: and B:, but The Network's disk copy utility now calls them C: and D:. Confusing? In reality, it doesn't take long to get used to it. Cirtech had no room for maneuver in this matter due to the different ways LocoScript and CP/M programs recognize their boot drives.</p>
+    <p>Operating under CP/M, however, is a bit more complex. Within this environment, the flash ROM block assumes the primary role of Drive A:, while your physical floppy disk drive mechanics are remapped to Drive C:—unless you are actively deploying the custom-modified build of DiscKit provided in the Cirtech kit. This custom utility preserves the native layout naming for floppy mechanics as Drive A: and Drive B:, but the legacy disk-copy tools inside "The Network" suite will now reference them as Drive C: and Drive D:. Sounds confusing? In practice, it takes very little time to get accustomed to this remapping. Cirtech had no structural alternative in this architectural design due to the clashing, hardcoded ways LocoScript and conventional CP/M binaries recognize their native boot volumes.</p>
   </div>
-  <!-- FIXED MODAL LAYER AND UPDATED PATH -->
-  <div id="pfd3" class="modal-pcw"><a href="#close" class="close-overlay"><img class="modal-content" src="/lib/exe/fetch.php?media=hardware:esquemas:CirtechFlashDisk_3.jpg"></a></div>
   <div class="drive-grid-container">
     <div class="drive-card">
       <div class="drive-gallery">
-        <div class="img-frame"><a href="#pfd3"><img src="/lib/exe/fetch.php?media=hardware:esquemas:CirtechFlashDisk_3.jpg"></a><span class="img-label">Connected Unit</span></div>
+        <div class="img-frame"><a href="#pfd3"><img src="/lib/exe/fetch.php?media=hardware:esquemas:CirtechFlashDisk_3.jpg"></a><span class="img-label">Module Connected View</span></div>
       </div>
     </div>
@@ Línea 147: / Línea 146: @@
   <div class="content-body">
-    <strong>Checking Compatibility</strong>
+    <strong>Evaluating Compatibility</strong>
-    <p>Inconsistent drive labeling and awkward installations are not the only complaints. The loss of Flipper is always regrettable (though, in this case, it is less noticeable because the ROM drive can reboot quite fast). For some people, the biggest problem would be that Cirtech did not install a "pass-through connector" on the flash drive casing. Therefore, it cannot be connected to a machine that already has a single-ended add-on, such as many printer interfaces. (Apart from this physical limitation, the flash drive is compatible with any other hardware that can be connected to a PCW.)</p>
+    <p>The inconsistent drive letter remapping and the archaic text-driven installation macros are not the only issues to consider. The loss of Flipper utility compatibility is always a shame (though less problematic in this instance, since the ROM block allows the system to reboot and recovery nearly instantly). For specific production workflows, the biggest drawback stems from the fact that Cirtech did not engineer a passthrough expansion edge connector onto the flash drive’s outer shell casing. Consequently, it cannot be mounted to a workstation that already hosts a single-ended expansion upgrade, such as conventional third-party parallel printer adapters. (Setting aside this physical daisy-chain limitation, the flash drive maintains complete electronic compatibility with any alternative hardware module designed for the PCW system.)</p>
-    <p>It would certainly be worthwhile to obtain a dual-direction expansion port adapter—if such things still exist—because the flash drive seems set to transform the PCW world. It is guaranteed to have a profound effect on our PCW utilities—and for a remarkably low price. The 1MB extra memory expansion chips were sold for £30.</p>
+    <p>It would undoubtedly be a highly smart investment to acquire a dual-direction expansion bus splitter adapter—if such accessories are still obtainable on the market—because this flash drive completely modernizes the daily computing experience on the Amstrad PCW. It is guaranteed to have a profound, lasting impact on the operational speed of your workstation utilities—and all for an impressively low retail price. In fact, separate 1MB memory capacity expansion chips were sold standalone for a mere price of £30.</p>
-    <p>In summary, the flash drive is quite fast when it comes to loading our operating system, saving the boot waiting time generated by the floppy drive. A reasonably low price for a new, convenient, and fast peripheral that brings fluidity to data workflows. You can add 1Mb or 2Mb of data capacity, and at its worst, the installation lacks a direct menu and relies on entering several commands.</p>
+    <p>In summary, the flash drive is exceptionally fast when loading your core operating system, entirely eliminating the tedious mechanical read delays associated with booting from floppy media. It stands as a highly affordable peripheral considering it offers a clean, convenient, and rapid experience that introduces true fluid data responsiveness to your daily office workflows. It allows appending 1Mb or 2Mb of instant non-volatile storage, balanced only by a clunky installer software suite that lacks an integrated master menu and demands manual command line inputs to get started.</p>
   </div>
 </div>
 </html>