qlwiki:qlhdd

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
qlwiki:qlhdd [2018/04/25 21:46] – praktikerqlwiki:qlhdd [2023/08/25 12:22] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +{{:qlwiki:falkenberghdd1.jpg?200|}}
 +The QL-HDD-Card was a hard disk interface from German company ABC Elektronic and designed by [[qlwiki:Jürgen Falkenberg]]. 
 +
 +The English version of the QL-HDD-Card Manual (dated 12/1991) (translated from the german original, which you can find further down) appears below:
 +
 +==== Introduction ====
 +
 +
 +
 +The JFC QL-HDD-Card is a powerful and flexible interface card for the system bus of the SINCLAIR QL for operating a hard disk via an additional PC hard disk controller to be connected to the card.\\
 +The device driver for the new directory device win1_ is available in the HDD-Card and is available immediately after switching on. It supports fast disks of virtually any size.
 +
 +=== MFM hard drives ===
 +
 +One of the following MFM controllers is required to operate an MFM hard disk: OMTI: 5520A, 5520B\\
 +Western Digital: WD-1002A-WX1\\
 +DataTech: MFM Controller\\
 +
 +=== RLL hard drives ===
 +
 +RLL hard drives can be powered by one of the following RLL controllers: OMTI: 5527A, 5527B\\
 +Western Digital: WD-1002-27X, WD-1002A-27X
 +
 +
 +=== Power supply unit and housing ===
 +
 +Due to the individually different expansion of many QLs, we have designed the structure of a hard disk system with the HDD card as an "open solution", without a hard disk of a certain size, power supply unit and housing. This allows the experienced hobbyist in particular a significant cost saving compared to the finished complete system. Of course we can deliver all required parts, also ready to plug in.\\
 +
 +The hard disk controller to be connected is already supplied with power from the QL via the HDD card If you are still using the original QL power supply, you must ensure that it is not overloaded (especially if there are other peripherals on the QL). If it gets very hot and dark stripes move vertically across the screen, the power supply is overstrained and must be replaced by a stronger one.
 +
 +For the hard disk an additional power supply with +5V and +12V DC voltage and the hard disk corresponding power design is required in any case. With QL systems, which were built into a PC housing with integrated power supply, this can usually also be used for the Winchester. A suitable housing for the hard disk drive is then already available here. Otherwise, you will need a sheet steel housing, with sufficient space for the additional power supply unit.
 +
 +=== ROM port adapter ===
 +
 +Since the Miracle [[qlwiki:Gold Card]] does not allow parallel operation of other QL cards on the system bus, the HDD-Card can be connected to the ROM port via a special adapter. Of course, the adapter can also be used if the system bus is otherwise occupied and you do not have/do not want to connect a BUS driver.
 +
 +
 +==== INSTALLATION ====
 +
 +
 +=== The QL HDD Card ===
 +
 +Like all JFC peripheral cards, it does not support Sinclair's electrically and mechanically questionable concept with looped through system bus and automatic addressing of slave cards. In our opinion, an extended system with several cards should have a BUS driver with several slots.
 +
 +In principle, the QL-HDD-Card can be connected directly to the QL system bus, the looped through bus of a QL card, any slot of the [[qlwiki:qlbus|JFC BUS]] driver or any other (functional) QL bus driver or with the special ROM port adapter also to the QL ROM port.
 +
 +Due to its dimensions, however, the board cannot be connected directly to the system bus as the first board if the QL motherboard is (still) accommodated in the original housing. In practice, however, the two will hardly occur together.
 +
 +=== Addressing the card ===
 +
 +As with all JFC peripheral cards, the HDD card is addressed transparently and individually by switches. It requires 16K address space and can be switched to one of the 17 expansion slots as well as three additional 16K blocks which are not supported by QDOS but are generally free. For this purpose, one of the valid combinations listed below must be set at switches 1 to 5:
 +
 +{{ :qlwiki:scan_falkenbergtabelle.jpeg?400 |}}
 +
 +When used with other QL peripheral cards, it is important to ensure that an expansion slot is not used twice. 
 +
 +512K RAM expansions are always in the $40000 to $BFFFF address range and can never lead to conflicts. Thanks to their configuration with switches, double address assignment with JFC cards can also be easily avoided. Expansion cards of other manufacturers are either on fixed addresses (eprom cards) or use the automatic addressing from $COOOOO and can only be configured by a modification or via the JFC BUS driver.
 +
 +For a secure check, install your system first completely with the exception of the HDD card and check the intended address space by querying the decimal base address adr with the following command: 
 +
 +PRINT PEEK_W (adr),PEEK_W(adr+2).
 +
 +If the numbers 19195 and 1 are output, the corresponding base address is already occupied.
 +
 +=== Address restrictions with special QL cards ===
 +
 +The [[qlwiki:SuperQBoard|Sandy SuperQBoard]] occupies 32K address space (two consecutive slots), whereby usually only its base address, i.e. the first slot, can be queried. When using a QBoard, the slot preceding the planned HDD card address (if from $COOOO) must also be checked as above.
 +
 +If a JFC QL-ROM card is used as extended operating system ROM ($00000 to $17FFF, ROM card page 1, see ROM card manual}, of course it occupies the 16K blocks at $10000 and $14000.
 +
 +The [[qlwiki:Trump Card|Miracle Trump Card]] uses the slots $10000, $14000 and $1COOO in principle. If it is equipped with 768K RAM, all slots from $COOOOO are occupied and the HDD card can only be addressed to $COOO (ROM port).
 +
 +To use the HDD card with the Miracle [[qlwiki:Gold Card]], the special ROM port adapter is required and the card must be installed on $COOO.
 +
 +The addresses $10000, $14000 and $1COOO are not originally intended for extensions and are not checked by the standard QDOS so that the driver EPROM is not recognized. If you still want to use this address space (with the exception of the cases mentioned above), the Winchester driver must be explicitly included after system startup by the command CALL adresse+48, whereby the corresponding decimal value (65536, 81920 or 114688) must be used for address. If you have assembler and system knowledge, you can easily add an additional EPROM (ROM port or QL-ROM card) or an additional query for these addresses by modifying the operating system.
 +The older QDOS versions (up to JM) even only check the ROM port ($COOO) and the first upper ROM slot ($COOOO) for extensions. The above restrictions then also apply to all extension addresses from $C4000.
 +
 +=== Connecting the controller card ===
 +
 +With the HDD card one of the Winchester controllers listed on page 1 can be used. The controller has a 62-pole contact plate, which is inserted into the 62-pole plug-in card connector on the HDD card. Make sure that the connection marked A1 on the controller is also connected to the contact marked A1 on the HDD card (the nearest to the QL bus connector). Both cards form a right angle with the sides of the component inside.
 +
 +=== Connecting the hard disk ===
 +
 +On the controller card, a 20-pin and 34-pin male connector are arranged next to each other, to which the hard disk is connected via two special ribbon cables. A possibly existing second 20-pin pin header below the first one can be ignored. The required flat cables are usually included with the hard disk, but can also be obtained from your specialist dealer or directly from us. When connecting, make sure that the pin 1 of the fast plate is connected to the pin 1 of the controller.
 +The system is now complete and can be put into operation.
 +
 +
 +==== THE WINCHESTER DRIVER ====
 +
 +
 +The driver in the eprom on the board adds the new directory device win1 to the QL. Like any other QL directory unit (floppy, microdrive, RAM disk), the hard disk can be used to back up, load, copy files. In addition to the many times higher storage capacity compared to normal 720K-QL-Floppies, a much faster file access is now also possible.
 +The Winchester driver supports hard drives of any size. It has an extended filing system with real subdirectories that are strongly based on the Level-2 FLP system. If you have the Level-2 drivers (GOLD-Card or TrumpCard/QBoard with Level-2-Eprom), some of the additional commands (e.g. MAKE_DIR, but not the extended file attributes) can also be used with the hard disk.
 +
 +=== Formatting the hard disk ===
 +
 +Before the hard disk can be used in the newly installed system, it must first be formatted. For this purpose, the "WINform_exe" program, which formats the disk physically (low-level) and logically, is located on the media which is supplied. WINform is started (with TK2 loaded) with a parameter string consisting of eight plate-specific parameters, each separated by a space:
 +
 +ex flp1_winform_exe; "cyls heads mode clsize rwc pcc interl name"
 +
 +
 +**cyls** Number of tracks (cylinder} of the disk. 
 +heads Number of heads.
 +**mode =** 'M' or'R' determines the controller-dependent recording method (MFM/RLL). 
 +**clsize** specifies how many sectors each 512 bytes) are to be combined into a cluster. A cluster is the smallest amount of storage space that is allocated when a file is copied to the hard disk, regardless of how much storage it actually requires. Since one copy of the FAT (File Allocation Table) is always kept in QL memory, large clusters save memory, but files waste more physical disk space on average. Below 40MB 4 should be used for clsize, above 8, only powers of 2 (2, 4, 8, 16, 32, 64 and 128) are valid.
 +**rwc** is the "reduced write currency start cylinder", from which write current is reduced (see data sheet of the disk), in case of doubt set = 0.
 +**pcc** is the "precompensation start cylinder", from which the length of the inner tracks is changed (see data sheet}, in case of doubt set = 0.
 +**interl** defines the sector offset and should be set = 2 or = 3.
 +name is the medium name of the hard disk up to 10 characters long, which is displayed at DIR.
 +
 +
 +//EX flp1_winform_exe; "615 4 M 4 0 0 2 QLHDD"//, for example, formats a Western Digital WD-362 or Seagate ST-225 and deletes all data stored on it. Formatting takes about one minute per 300 tracks, depending on the number of heads. Then start the program "WINtracks_bas" of the enclosed diskette with LRUN flp1_wintracks_bas to block the faulty disk sectors specified in the defectlist (usually attached to the disk case). The hard disk is then ready for use like a formatted diskette.
 +
 +
 +=== Initialisation ===
 +
 +When the driver is mounted after power-on or a reset, the disk heads are moved to track 0 to check their proper function.
 +If no disk is found or another error occurs, the driver is not initialized and no power-on message appears. If no controller is inserted into the HDD card, the driver remains "stuck" during initialization.
 +
 +
 +=== Automatic Boot ===
 +
 +If a correctly formatted hard disk is detected during the check, the driver searches for the "boot" file and starts it automatically after pressing the <F1> or <F2> key as usual from Floppy or Microdrive. The autoboot routine is already implemented in the QL-internal ROM, whereby QDOS first attempts to load a basic program from a device "boot". If this is not available, the file "boot" on the device "mdv1_" is searched.
 +The previous floppy drivers for the QL use this autostart option as follows:
 +During initialization, the system checks whether a diskette is inserted in the drive. If yes, the floppy driver is first logged on under the name "mdv" (!) and the driver notes that the floppy must be renamed to "flp" the next time it is accessed. QDOS will now search for the boot device and then "mdv1_boot" and load and execute the file "boot" from the floppy. The driver immediately renames the floppy to "flp" and the user doesn't notice anything about the whole procedure. This procedure becomes problematic if there are other autostartable directory devices in the system. The hard disk (and the MOS driver of the QL-ROM card) go another way: In addition to the Winchester driver, the operating system of the HDD card also integrates the "boot" device, a short basic program that tries to load "win1 boot". This avoids name conflicts, since QDOS automatically knows and executes only the most recently entered ROM extension at the highest address, even if the boot device is logged on several times. By selecting the base address of each extension, the user can individually determine from which medium he wants to boot.
 +
 +This inconsistent prevents a floppy from being renamed to "flp" because it has been inserted as "mdv", since QDOS will execute "boot" from the HDD driver and the FLP driver will not be given the correct name "flp" by calling "mdv1_boot". This can only be done the first time the floppy is accessed (which must be done via "mdv"). Therefore insert DIR mdv1_ or FLP_ USE flp into the boot program of the hard disk.
 +Alternatively, the Winchester boot program can use the TK2 function FTEST(\mdv1_boot) to detect a disk inserted in the floppy and start its boot program, which is ultimately the most elegant method for redirected autostart.
 +
 +If the hard disk boot program contains a major error that causes the system to crash or "get stuck" immediately, it can be stopped by repeatedly pressing <Ctrl> & <Space> before executing the first statement. However, it must not have been written without line numbers.
 +
 +
 +=== New Basic commands ===
 +
 +The Winchester driver adds four new commands to Basic:
 +
 +**WIN USE "new"**
 +gives the hard disk the new device name new, so that the fast disk is always used for all subsequent accesses to new.
 +To be able to use programs that are pre-installed for the use of certain units (e.g. flp) without reconfiguration, the name 'win' can be replaced by any three letters or another unit name.
 +
 +**PARK**
 +moves the heads of the plate to the parking position.
 +To prevent the magnetic layer from being damaged by the heads sinking to the plate surfaces after switching off, the heads can be driven onto the (undescribed innermost) parking lane with PARK. In normal operation, this is only necessary for older drives, but in any case before each transport of the hard disk.
 +
 +**SYNC**
 +writes all not yet saved slave blocks to the hard disk.
 +The driver fully utilizes the slave blocks provided in QDOS to buffer data and reduce comparatively slow physical access. Only if the processor has nothing else to do or the memory is used otherwise, the slave blocks are written to disk. This causes a serious acceleration of file accesses, especially when updating the same file, but is fatal if the system crashes or the power fails before all slave blocks have been written.
 +SYNC should always be entered when starting a program that is at risk of crashing.
 +
 +**CALL_S adr[val1][,val2][,val3)[...]**
 +allows the machine language routine to be called at the address adr, similar to CALL. The parameters val1, val2,... are not transferred to the registers, but (in the correct order) written to the stack. CALL_S is helpful for direct sector access.
 +
 +
 +=== The directory of the hard disk ===
 +
 +Since QDOS can only display a maximum of 32767 sectors (=16MB) for a directory unit, but hard disks generally have considerably more memory, the number of sectors in sectors per 10KB (=20 standard sectors per 512 bytes) is displayed in the directory of the hard disk:
 +583/2091 sectors indicates that 11660...11679 sectors of the just under21MB are still free.
 +If the Level-2 Filing system is installed (GOLD-Card, TrumpCard/QBoard with L2- Eprom, see above) this change is not effective. It takes into account the high number of sectors of hard disks, so that QDOS can now also display higher number of sectors. A DIR of the above plate then delivers: 11660/41820 sectors.
 +
 +
 +=== subdirectories ===
 +
 +With the large storage capacity of a hard disk with hundreds of files, the use of subdirectories is unavoidable. In QDOS, the directory name (path} is placed before the actual file name, e.g. "letter_" before all letter files. Directories can also be nested in several levels, resulting in a tree structure. However, you must ensure that the entire path and file name does not exceed 36 characters in length. You should therefore choose short directory names or not too deep nesting.
 +
 +Unlike the Level 2 FLP drivers, the Winchester driver does not require a new Basic command to create a directory. This is inconsistent, but has the advantage that directories can also be created by application programs and not only from the basic level.
 +If a file is created that contains a"&" in its name, a directory with the same name is generated, e.g. SAVE "win1_&newsubdir". All files "win1_newsubdir_" created below are automatically entered in this directory. The command DIR win1_ now shows only the directory "newsubdir"; the files contained in it are only visible by DIR win1_newsubdir_. This prevents the basic directory level from being confused with hundreds of files.
 +Although the Winchester driver is not a true level 2 driver, Filing System 2 also supports the hard disk. If you have a GoldCard or a Trump-Card or a QBoard with Level-2 driver exchange EPROM, the above directory on the hard disk can also be created with MAKE_DIR win1_newsubdir (see flp-level-2 manual). If Filing-System-2 is active, the Winchester directories will also be indicated by an appended "->".
 +
 +A subdirectory can be deleted with DELETE win1_subdir if it does not contain any files (anymore).
 +
 +An individual file can be accessed either by entering the entire medium, path and file name in a less convenient way or by using the TK2 default device management with PROG_USE, DATA_USE, DEST _USE and the commands DUP and DDOWN for changing the directory level (see TK2 instructions).
 +
 +Since many programs (e.g. Quill) do not accept more complex file names and ignore TK2 default devices, a working directory can be set up before the program starts. It is stored separately for each job and passed to child jobs so that a working directory (initially created in Basic) can be changed in the job itself.
 +The working directory is defined by addressing a file with the "$" symbol inserted, e.g.: DIR "win1_quill_briefe_$". If Quill is now started, the driver automatically prepositions the working directory when loading (or saving) the file "Win1_meier1_doc", so that Quill actually accesses "win1_quill_briefe_meier1_doc", which would otherwise not be possible with the file names that are up to 8 characters long in Quill.
 +
 +The workdirectory itself cannot be switched to a higher or lower directory level. It must first be deleted by a file command to "win1_!$" before it can be reconfigured with "$" as described above.
 +
 +If the"..." switch is inserted into a file name, a directory level can be temporarily switched up. If the workdirectory is empty, LOAD loads "win1_basic_progs_$test_bas" in the directory "win1_baslc_progs" and sets "win1_basic_progs" as the workdirectory.
 +MERGE "win1_.._subprogs_proc1_bas" then loads the file "proc1_bas" from the parallel directory "win1_basic_subprogs", the working directory remains unchanged.
 +
 +With"!" as switch the set working directory and any previous name parts can be ignored: LOAD 'win1_egal_!boot" loads the boot program from the root directory (root directory, top level) regardless of which workdirectory is set.
 +
 +
 +It should be emphasized that the working directories are only an auxiliary concept for programs that do not accept long file names or the more practical TK2 default device management.
 +A mixed use (one path half workdirectory, the other via TK2 default device) does not work and always leads to problems. You should therefore work with either the default devices or the work directories.
 +
 +=== Included software ===
 +
 +The data carrier enclosed with the HDD card contains programs and further information required or useful for hard disk operation:
 +
 +
 +**winform_exe**
 +is the program already described for formatting the hard disk.
 +
 +
 +**deftracks_bas**
 +allows the locking of faulty disk sectors after formatting.
 +
 +
 +**winbak_exe, selbak_exe and bakread_doc**
 +are two PD programs for convenient hard disk backup together with instructions.
 +
 +
 +**quillboot_bas**
 +is a demo boot program and illustrates the work with the working directory.
 +
 +
 +**readme_doc**
 +is a Quill document for inventors and describes direct sector access to the disk.
 +
 +
 +
 +----
 +
 **Anleitung für die QL-HDD-Card von Jürgen Falkenberg Computertechnik.** **Anleitung für die QL-HDD-Card von Jürgen Falkenberg Computertechnik.**
 +
  
 ==== EINLEITUNG ==== ==== EINLEITUNG ====
Line 48: Line 262:
 Die Adressierung der HDD-Card erfolgt wie bei allen JFC Peripheriekarten transparent und individuell flexibel durch Schalter. Sie benötigt 16K Adressraum und kann auf einen der 17 Erweiterungs-Steckplätze sowie drei weitere 16K-Blöcke, die von QDOS nicht unterstützt werden im allgemeinen aber frei sind, geschaltet werden. Hierzu ist an den Schaltern 1 bis 5 eine der nachfolgend gelisteten gültigen Kombinationen einzustellen: Die Adressierung der HDD-Card erfolgt wie bei allen JFC Peripheriekarten transparent und individuell flexibel durch Schalter. Sie benötigt 16K Adressraum und kann auf einen der 17 Erweiterungs-Steckplätze sowie drei weitere 16K-Blöcke, die von QDOS nicht unterstützt werden im allgemeinen aber frei sind, geschaltet werden. Hierzu ist an den Schaltern 1 bis 5 eine der nachfolgend gelisteten gültigen Kombinationen einzustellen:
  
-https://qlwiki.qlforum.co.uk/doku.php?ns=qlwiki%3A&image=qlwiki%3Ascan_falkenbergtabelle.jpeg&do=media+{{ :qlwiki:scan_falkenbergtabelle.jpeg?400 |}}
  
 Bei der Verwendung mit anderen QL-Peripheriekarten müssen Sie beachten, dass ein Erweiterungsslot nicht doppelt belegt wird. 512K-RAM-Erweiterungen liegen grundsätzlich im Adressraum $40000 bis $BFFFF und können nie zu Konflikten führen. Durch ihre Konfiguration mit Schaltern kann eine doppelte Adressbelegung mit JFC-Karten auch leicht vermieden werden. Erweiterungskarten anderer Hersteller liegen entweder auf festen Adressen (Eprom-Karten) oder benutzen die automatische Adressierung ab $COOOO und können nur durch eine Modifikation oder über den JFC BUS-Treiber adresskonfiguriert werden. Bei der Verwendung mit anderen QL-Peripheriekarten müssen Sie beachten, dass ein Erweiterungsslot nicht doppelt belegt wird. 512K-RAM-Erweiterungen liegen grundsätzlich im Adressraum $40000 bis $BFFFF und können nie zu Konflikten führen. Durch ihre Konfiguration mit Schaltern kann eine doppelte Adressbelegung mit JFC-Karten auch leicht vermieden werden. Erweiterungskarten anderer Hersteller liegen entweder auf festen Adressen (Eprom-Karten) oder benutzen die automatische Adressierung ab $COOOO und können nur durch eine Modifikation oder über den JFC BUS-Treiber adresskonfiguriert werden.
Line 205: Line 419:
 ist ein Quill-Dokument für Tüftler und beschreibt direkten Sektorzugriff auf die Platte. ist ein Quill-Dokument für Tüftler und beschreibt direkten Sektorzugriff auf die Platte.
  
 +{{:qlwiki:falkenberghdd2.jpg?200|}} 
 +{{:qlwiki:falkenberghdd3.jpg?200|}} 
 +{{:qlwiki:falkenberghdd4.jpg?200|}}
  • qlwiki/qlhdd.1524692789.txt.gz
  • Last modified: 2022/11/05 11:18
  • (external edit)