@WojtasJD bardzo Ci dziękuję dobry człowieku. :D Troszkę miałam kombinowania, bo na początku nie do końca zrozumiałam o co Ci chodziło, ale też w sumie i tak chyba troszkę inaczej zrobiłam, w każdym razie, co najważniejsze - poszło. :) Bardzo dziękuję również innym osobom, które się zaangażowały w temat. :) config.sys jednak trzeba zostawić w spokoju, ja powywalałam tylko niepotrzebne rzeczy, a w autoexec.bat wywaliłam w pierwszej części kopiowanie command.com, a później, po "wejściu" do RAMDRIVE kopiowałam tylko usbaspi.sys oraz devload.com. O dziwo nigdzie nie dawałam kopiowania command, a działa i nie wywala błędów. I na koniec pliku, żeby załadował sterownik, to przed uruchomieniem MHDD dałam, żeby wyszedł do nadrzędnego katalogu, załadował dopiero ASPI, a później wejście do folderu MHDD i dopiero uruchomienie programu (bez tego ignoruje sterownik). Załączę te wszystkie pliki wraz z instrukcją, żeby w razie, gdyby ktoś miał podobny problem, to żeby już nie musiał się tak męczyć jak my tutaj wszyscy. :) Mam nadzieję, że się komuś kiedyś przyda. PS. Jeszcze mnie zastanawia taka rzecz, bo jak z ciekawości chciałam też przeskanować jakiegokolwiek pendrive'a i u mnie przy włączeniu skanu 2x, MHDD się zawiesza, nic nie da się zrobić (jak na zdjęciu), dopiero gdy wyjmę pendrive'a, którego chciałam przeskanować, to wtedy rusza, ale twierdzi, że są same bad sectory, z tym że to już zrozumiałe, bo skoro już nie ma nośnika, który miał skanować, to będzie wywalał błędy. Natomiast zewnętrzny dysk twardy gdy się skanuje, to cały leci zielonymi bloczkami, odczyt <150ms. :D Czy to jest normalne? http://obrazki.elektroda.pl/8301966600_1501866569_thumb.jpg
Type ALT+F+X to exit Edit
What's New for the Windows 98 Startup Disk?
The Startup Disk has changed significantly for Windows 98. The following
items are new for Windows 98.
- MULTI-CONFIG START MENU
- REAL-MODE CD-ROM DRIVERS
- EBD.CAB FILE
- RAMDRIVE
- WINDOWS 98 STARTUP PROBLEMS
- USING THE TOOLS AVAILABLE ON THE STARTUP DISK
MULTI-CONFIG START MENU
=======================
If you boot your computer using the new Windows 98 Startup Disk, a boot menu
appears allowing you the option to load drivers for the most common CD-Rom
drives or perform a normal clean boot.
After you make your selection, the Config.sys file loads the appropriate
CD-ROM driver (if selected) and then loads a 2MB RAMDrive. The RAMDrive is
used to store all the diagnostic tools necessary to troubleshoot the most
common problems.
NOTE: The RAMdrive may cause your CD-Rom to pushed back 1 drive letter. If your
CD-Rom is usually drive D:, it will now be Drive E:.
REAL-MODE CD-ROM SUPPORT
========================
The Windows 98 Statup Disk includes generic ATAPI IDE & SCSI CD-ROM drivers
that allow your CD-ROM to function at Dos when the Windows 98 GUI is not
available.
NOTE: Not all CD-Rom drives are supported. If your CD-Rom drive does not
function with these drivers, you must use the drivers that came with your
CD-Rom drive.
EBD.CAB FILE
============
The Ebd.cab file is a compressed file whose contents are extracted to the
Ramdrive during the startup process. The table below identifies the files
in the Ebd.cab file.
File Function
Attrib.exe Add or remove file attributes
Chkdsk.exe A simpler and smaller disk status tool
Debug.exe Debugging utility
Edit.com Real-mode emergency text editor
Ext.exe New, simple file extract utility
Format.com Disk format tool
Mscdex.exe Microsoft CD-ROM file extension for MS-DOS
Scandisk.exe Disk status tool
Scandisk.ini Disk status tool configuration file
Sys.com Transfers system files and make disk bootable
Uninstal.exe A tool to remove Windows 98 from the system and return the
system to its previous state
CREATING A RAMDRIVE
===================
The RAMDrive is created during the processing of the Config.sys file and is
2MB in size. The Ramdrive is created using system RAM to emulate a physical
Hard Disk. Without creating the RAMdrive, we would not have enough space on
a single 1.44 meg floppy disk to contain all the diagnostic tools as well
as the CD-Rom drivers.
WARNING: Since the RAMDrive is created during the processing of the Config.sys file
and uses System RAM, it is only temporary. It will disappear if you restart
your computer normally.
LIST OF ALL COMPONENTS ON THE EBD
=================================
The following table describes the function of each file copied to the EBD.
File Function
Aspi2dos.sys Real-Mode Adaptec CD-ROM driver
Aspi4dos.sys Real-Mode Adaptec CD-ROM driver
Aspi8dos.sys Real-Mode Adaptec CD-ROM driver
Aspi8u2.sys Real-Mode Adaptec CD-ROM driver
Aspicd.sys Real-Mode Adaptec CD-ROM driver
Autoexec.bat Startup batch file
Btcdrom.sys Mylex/BusLogic CD-ROM driver
Btdosm.sys Mylex/BusLogic CD-ROM driver
Command.com Command interpreter
Config.sys Loads the device drivers
Drvspace.bin Microsoft DriveSpace compression driver
Ebd.cab Cab file containing extract utilities
Ebd.sys File identifying the ESD
Extract.exe File to expand the Ebd.cab file
Fdisk.exe Disk partition tool
Findramd.exe Utility to find the RAMDrive during startup
Flashpt.sys Mylex/BusLogic CD-ROM driver
Himem.sys XMS Memory Manager
Io.sys System boot file
Msdos.sys Boot option information (paths, multiboot, and so on)
Oakcdrom.sys Generic device driver for ATAPI CD-ROM drives
Ramdrive.sys Creates a Ramdrive during startup
Setramd.bat Searches for first available drive to be a Ramdrive
WINDOWS 98 STARTUP PROBLEMS
===========================
This section includes some common troubleshooting steps that can be used
when it's necessary to use the Windows 98 Startup Disk. These steps are
designed to get the user at least into Safe-Mode where you have access
to Windows 98 extensive HELP system to further troubleshoot any issues.
Starting Your Computer in Safe Mode
-----------------------------------
There are several reasons why Windows 98 may fail
to start properly. The first step in troubleshooting
is to try starting your computer in Safe Mode. If
Safe Mode works, you can then use the extensive Help
system and troubleshooters located in the Start
menu/Help option.
& gt; & gt; & gt; To start your computer in Safe Mode:
1. Remove the Startup Disk and restart your computer.
After the computer restarts but before Windows begins
to load, hold down the CTRL key until the Microsoft
Windows 98 Startup Menu appears. (If you are running
Windows 95, press the F8 key at the " Starting
Windows 95 " prompt.)
2. From the Startup menu, select Safe Mode.
If you can start your computer in Safe Mode, use
Windows 98 Help to resolve your original issue.
Setup Fails and the Computer Will Not Start
-------------------------------------------
There are a few common reasons why Windows 98 Setup
may fail to complete successfully. The following
section explains what you can do to recover from
these situations. For more information on other
Setup problems, see the Setup.txt file in the
Win98 folder of your Windows 98 CD or Setup Disk #1.
If you encounter any of these error messages while
running Setup:
* Invalid System Disk
* Incorrect MS-DOS Version
* Missing or Corrupted Command.com
* Compression Driver errors
It is likely that your computer's startup drive may
need updated system files. You can use the SYS command
to copy the needed files to your computer.
NOTE: If you are currently loading compression software,
you will need to know your host drive letter. This is
typically H. If you are not loading any compression
software, then you will need to SYS your C drive.
& gt; & gt; & gt; To use the SYS command to copy system files to your
computer:
1. Restart your computer using the Windows 98 Startup
Disk, select option 2 on the Startup menu, and then
press ENTER.
2. At the A:\ prompt, type: SYS X: (where X is your
Host or Startup drive).
3. If the procedure is successful, a " System transferred "
message appears. If it is not successful, check to be
sure you are typing the correct drive letter for your
Host Drive.
IMPORTANT: If you have installed software that came with
your hard drive, be sure to read the documentation that
describes how to start your computer using a floppy disk.
Antivirus Software
-------------------
If antivirus programs are left running during Setup,
they may prevent Setup from properly updating the system
files. If this occurs, disable or uninstall the antivirus
program, and then run Setup again.
NOTE: Some computers have built-in antivirus software.
This built-in software should also be disabled before
running Setup. If the software is left enabled, you
may receive a warning message informing you that the
Master Boot Record has changed. If you see such a
message, you MUST accept these changes or Setup may
stop responding.
Setup Stops Responding During Hardware Detection
------------------------------------------------
If Setup stops responding while it is detecting the
hardware in your computer, turn your computer off and
wait a few seconds, then turn it back on. You may need
to do this several times, because Setup could stop
responding during several different detection modules.
NOTE: Use the power switch to turn your computer completely
off. Do not use the reset button or press CTRL+ALT+DELETE
to restart your computer.
If Setup still fails to complete successfully, it may be
necessary to start your computer in Safe Mode so that
you can view the Help topics associated with hardware
detection.
Compressed Drives Not Mounted
-----------------------------
There are several reasons why compressed drives may
not be accessible. If your Windows directory is on a
compressed drive that is not mounted, you will not be
able to start Windows. If you suspect problems with your
compressed drives, try using Scandisk to fix them.
From the A:\ prompt, type:
Scandisk /Mount X:
where X is the drive letter of the compressed drive.
ScanDisk will then attempt to repair any errors and
mount the drive.
If there is not enough memory to check your compressed
drives, see " Installing Windows 98 from MS-DOS, " in
the Setup.txt file on Setup Disk 1 or the Windows 98 CD.
USING THE TOOLS AVAILABLE ON THE STARTUP DISK
=============================================
This section decribes how to use some of the utilities
included with the Windows 98 Startup Disk. To run each
program you should do the following:
1. Put the Windows 98 Startup Disk in the floppy disk
drive, and then restart your computer.
2. At the Startup menu, select option 1 or 2
(depending upon whether you need CD-ROM access),
and then press ENTER.
3. At the MS-DOS command prompt (A:\), type the name
of the utility you wish to run, and then press ENTER.
SCANDISK.EXE and CHKDSK.EXE
----------------------------
These two programs are useful for checking your hard
disk for errors. If you suspect there may be file
corruption or other problems with your hard disk(s),
run ScanDisk to check for and repair errors.
To check all your hard disks for errors, type:
Scandisk /all
To perform a full surface scan of your hard disk(s) for
maximum protection against data loss, type:
Scandisk /all /Surface
NOTE: You may receive errors about Long File Names. The MS-DOS
version of ScanDisk can only detect problems with long
file names, it cannot fix them. To correct these types of
errors, you must run ScanDisk from within Windows 98.
NOTE: If you have any compressed drives, you may receive an
error message stating that there is not enough memory
to check your compressed drives. To solve this problem,
try starting your computer with the Windows 98 Startup
Disk, as described in Step 1, earlier in this section.
Select option 2. This may allow ScanDisk enough memory to
check your compressed drives.
If ScanDisk is unable to check your drives, try using
CHKDSK.EXE instead. CHKDSK will check for cross-linked
files and lost allocation units.
SYS.COM
=======
The SYS command is used to copy system files from one
disk to another. Your computer needs these system files
to start.
& gt; & gt; & gt; To SYS your C drive, type:
SYS C:
and then press ENTER. After a few seconds, a
" System Transferred " message appears.
The following files are copied to your hard disk during
the SYS procedure:
* IO.SYS
* MSDOS.SYS
* COMMAND.COM
If the SYS C: command does not work and you have a
compressed drive, you may need to type the drive letter
of your host drive. With the DblSpace or DrvSpace programs,
the host drive is typically designated drive H. If you are
not sure of the drive letter, run ScanDisk and see if it
prompts you about your compressed drive.
FDISK.EXE and FORMAT.EXE
------------------------
FDISK and FORMAT are utilities necessary for installing
a new hard disk in your computer or for starting over
fresh with a clean disk. FDISK is used first to create
a partition and then FORMAT is used to make the partition
available for use.
WARNING: Using FDISK incorrectly can destroy all data
on your hard disk. If you are unsure of how to use FDISK,
consult your computer documentation.
You can use the Windows 98 version of FDISK to create
FAT32 partitions on drives over 512 megabytes in size.
FAT32 reduces the cluster size for large drives and allows
you to create single partitions on drives over 2 GB.
To view your current drive status, type FDISK /STATUS
at the MS-DOS command prompt.
After you have partitioned a drive using FDISK, you will
need to use the FORMAT command. To format a newly
partitioned drive, type:
FORMAT X:
Where X represents the letter of the drive that you
want to format.
If you want to format drive C, you need to make this
disk a system disk so that your computer can start. To
do this, type /s at the end of the FORMAT command. For
example:
FORMAT C: /s
System Startup files will be automatically copied after
your drive is formatted.
CD-ROM Drivers
--------------
The Windows 98 Startup Disk includes a set of generic
CD-ROM drivers. These drivers work with most IDE ATAPI
and SCSI CD-ROM models.
If your particular CD-ROM drive does not work with
these drivers, you will need to use the drivers that
came with your CD-ROM drive.
Following are some known issues about the CD-ROM drivers:
1. CD-ROM drives connected to sound cards may not work
properly.
2. Early proprietary CD-ROM drives (for example, Mitsumi,
Panasonic, Sony) may not work with these drivers. Some
older IDE controllers may fail as well.
3. The SCSI drivers on the Startup Disk support most
Adaptec, Buslogic, and Mylex adapters. Some other
SCSI CD-ROM drives may not work with the drivers on
the Startup Disk.
4. If your SCSI controller is configured for a non-default
I/O range, the drivers may not detect your SCSI card.
Consult your SCSI driver documentation for the default
I/O ranges for your card.
5. Drivers are not included for any PC Card (PCMCIA)
CD-ROM drives.
UNINSTAL.EXE
------------
If you need to remove Windows 98 from your system, you
can use the real-mode uninstall utility included on the
Windows 98 Startup Disk.
IMPORTANT: If you did not choose the option to " Save
System Files " during Setup, then you will be unable to
use this utility.
& gt; & gt; & gt; To use the uninstall utility, perform the following
steps:
1. Restart your computer with the Windows 98 Startup Disk,
select option 2, and then press ENTER.
2. At the MS-DOS command prompt, type UNINSTAL, and then
press ENTER.
NOTE: If you see the message " WINUNDO.DAT is missing or
corrupt, " you cannot uninstall this version of Windows 98.
EXT.EXE
-------
The EXT command is used in conjunction with the Extract.exe
utility to make it easier to extract Windows 98 files to
your hard disk. You can use this to replace missing or
damaged files.
This utility is extremely useful if you are receiving errors
during startup about missing files, or execution errors such
as General Protection Faults or invalid page faults.
& gt; & gt; & gt; To use Ext.exe to extract a file, perform the following
steps:
1. Use the Startup Disk to start your computer. Select
option 1, and then press ENTER.
2. Make sure the Windows 98 CD is inserted in the drive.
3. Type EXT at the MS-DOS command prompt, and then
press ENTER.
4. Follow the prompts to indicate the location of the
Windows 98 Setup files, the files you wish to extract,
and the location in which you want to place the extracted
files.
NOTE: If your CD-ROM drive letter is E, then type the location
to the Setup files as E:\WIN98.
NOTE: If you wish to extract more than one file at a time, you
can use wild card characters.
1. Pod³¹cz Pendrive / kartê SD*
2. Uruchom HPU (jako admin) i wybierz powy¿szy nonik
3. File system: FAT32, [v] Quick Format, [v] Create DOS startup disk
4. Jako DOS startup wybierz folder DOSWin98
5. Z folderu mhddFiles przekopiuj wszystkie pliki na nonik
OPCJONALNIE - usuwanie atrybutów z command.com
Uruchom [Win+R] CMD - & gt; attrib -h -s X:\command.com
(X - litera nonika)
* HP USB w Windows 10 mo¿e nie widzieæ karty microSD, ale bez problemu widzi w Windows XP
English documentation has been moved to http://mhdd.com
English FAQ: http://mhddsoftware.com/forum/viewtopic.php?t=4261
Also try new MAN command in MHDD - it works in both languages.
Russian documentation is on http://mhdd.com/ru/
Russian FAQ: http://mhddsoftware.com/forum/viewtopic.php?t=3468
Also try new MAN command in MHDD - it works in both languages.
Please use MAN command in MHDD to see manual for batches
USBASPI is a 'universal' driver for many different USB Mass Storage drives
with different chipsets, such as Intel, VIA, NVIDIA, Ali and SiS chipsets.
Especially USB Flash drives should work fine with this driver.
But note that this driver is actually a 'converter', i.e. Convert USB
devices to SCSI/ASPI devices, so you also need to load some universal
SCSI/ASPI driver after USBASPI in order for the devices to work correctly.
The driver scans all three USB controller specs by default.
Panasonic USBASPI.SYS Switches:
Here are the known valid switches identified so far with the Panasonic(TM)
v2.20 USBASPI.SYS driver in CONFIG.SYS:
device=[{path}]USBASPI.SYS [/e] [/o] [/u] [/v] [/w] [/r] [/l[#]] [/f] [/slow] [/nocbc] [/norst] [/noprt]
You can specify more than one controller type (e.g. /e /u).
This switch can also be used to force slower speed operation on high-speed USB
controllers & devices. The driver will scan for all types of USB controllers,
so use these switches to specify which port types to enable. This allows for
faster USB scanning.
By specifying /u or /o and omitting /e, it forces Full-Speed mode on High-Speed
devices. But a Low-Speed (LS) or Full-Speed (FS) device cannot be made to run
at High-Speed (HS).
/e
EHCI, for enabling only USB 2.0 controller
/o
OHCI, for enabling only add-on/onboard USB 1.1 controller
/u
UHCI, for enabling integrated USB 1.1 controller
In verbose mode:
USBASPI displays details on controller type and USB devices it detects.
It displays the vendor & product ID codes, the controller address range
(memory map or I/O port map) of controllers, and the connection speed code
for each device.
/v
Verbose, shows USB details - excellent troubleshooting tool
These switches modify driver actions:
/w
Wait, displays prompt message to allow swapping/attaching of target USB device
/l#
Luns, to specify highest number of LUN assigned, default /L0
/slow
to enter SLOW down mode, gives longer delays when scanning USB devices
/nocbc
for NO Card Bus Controller, to disable detection of USB on CardBus slots
/norst
for NO ReSeT, this is useful when legacy USB devices
(e.g. a USB keyboard or mouse) had been pre-initialized by the BIOS so
by preventing a USB reset, these devices would still function after
USBASPI.SYS has loaded.
This switch is typically used on portable systems with an external USB floppy
drive connected to the single USB port for boot-up. Used in conjunction with
RAMFD.SYS so after the boot floppy is copied to a RAM drive, (and after the
/W pause...) the USB floppy can be removed, and the target mass storage device
can be attached and detected
/r
Resident, allows driver to stay resident in memory when USB floppy drive is
detected.
There are a number of switches whose specific function is still unknown.
Please post your discoveries in the USBMAN end-user forum, or the Computing.Net
DOS forum.
/noprt
Have found that on some systems with USB on Intel chipset (1.1 or 2.0), if UHCI
is normally I/O mapped, using this switch causes USBASPI.SYS to " hang " while
detecting host controllers. Could it be to force I/O port addressing mode?
/f
/p=xxxx
As per F2H documentation, this sets the I/O port address, but have been unable
to get this to work on standard desktops. Could it be for CardBus?
Since USBASPI.SYS just maps a USB storage device to an ASPI device,
an additional driver is needed to map the ASPI mass storage to a DOS drive
letter.
Unofficial MS-DOS 5/6/7/8 + Windows 3.1x/9x/ME Panasonic native DOS USB driver
USBASPI.EXE (USBASPI.SYS) 2.28 Fix
NOTE:
Provided 'as is', without any warranties, expressed or implied.
Use at your own risk!
REQUIRED:
Motherboard BIOS + chipset with USB support.
MS-DOS 5.00, 6.00, 6.20, 6.21, 6.22, 7.00, 7.10, 8.00, FreeDOS, DR-DOS,
PC-DOS, Open DOS, Novell DOS, ROM-DOS or similar.
Windows/WfWG 3.1x, Windows 95, 98, 98 SP1, 98 SE or ME.
OLDER:
Included here are also older versions of USBASPI.SYS driver:
- USBASPI.SYS v2.27
- USBASPI.OLD v2.26
To use v2.26, just rename USBASPI.OLD to USBASPI.SYS (make sure to rename or
move to another directory newer USBASPI.SYS v2.27 driver first).
INSTALL:
Run USBASPI /? from any DOS prompt to learn its command line parameters.
******************************************************************************
ASPI Manager for USB mass-storage Version 2.28
(C)Copyright Panasonic Communications Co., Ltd. 2000-2007
Usage:
DEVICE=[Path\]USBASPI.EXE [/e] [/o] [/u] [/i=dddddd[,dddddd][-dddddd]]
[/l=dddddd] [/lat=hhhh] [/nocbc] [/noprt] [/norst]
[/nols] [/r] [/p=hhhh] [/slow] [/v] [/w] [/w]
[/w=dddddd]
Switches:
/e enable EHCI controllers only
/o enable OHCI controllers only
/u enable UHCI controllers only
(default is /e /o /u)
/i= decimal memory address(es) or ranges for OHCI controllers
/p= hexadecimal port address for UHCI controllers (if *not* set by BIOS)
/l= decimal LUN (max. 6)
/lat= hexadecimal PCI latency (max. 0xFE)
/slow use slow mode
/v use verbose mode
/w pause *after* controller initialization
/w /w pause *before* controller initialization
/w= ?
/nocbc no cardbus controller -- & gt; no detection of cardbus controllers
/noprt no protected mode -- & gt; use BIOS (int15 ah=0x87) for transfers
/norst no controller reset
/r use controller reset (default)
/nols ?
******************************************************************************
Then add a line for it to your CONFIG.SYS. Reboot.
Example:
DEVICEHIGH=C:\USB\USBASPI.EXE /w /w
Uses upper DOS RAM if loaded with DEVICEHIGH in CONFIG.SYS (upper memory
manager required in CONFIG.SYS):
http://www.mdgx.com/newtip20.htm#9SMM
http://www.mdgx.com/umb.htm
MORE INFO:
USBASPI.EXE is a modification of the recently released Panasonic native DOS
USB driver USBASPI.SYS ver 2.28.
I found a reference to that new version on a recent MSFN post:
http://www.msfn.org/board/index.php?showtopic=40561
http://www.msfn.org/board/index.php?showtopic=114868 & pid=753965
The modification was necessary as I experienced system lockups on PCs where
the BIOS supports some USB mass storage devices, such as USB floppy drives,
USB ZIP drives and USB CD-ROM drives, but, for example, not all USB memory
sticks or hard drives.
With the command line switch /w the driver now pauses *after* the USB
controllers have been initialized. When USB mass storage devices are connected
at that point, the lockups no longer occur.
The original functionality, that is, the driver pauses *before* the
controllers are initialized is still possible with the following command line
switch:
USBASPI.EXE /w /w
When the driver is invoked as USBASPI.EXE at any DOS prompt, it does not load
as a driver and the internal stack space is not needed. I used that space to
include a brief description of the command line switches as far as I know
their functionality. This addition does not use any DOS memory or increase the
file size (important for boot floppy disks!).
I managed to create DOS 7.10 boot disks (floppy and CD-ROM) combining
USBASPI.EXE successfully with DI1000DD.SYS or NJ32DISK.SYS (my preferred
driver) or ASPIDISK.SYS (ver 4.01b). I use such boot disks to run Norton Ghost
(ver 8 and 11). I did notice that some memory sticks are not recognized by the
Panasonic driver (ver 2.20, 2.24, 2.26 and 2.28) if they are connected to a
USB port with some UHCI-only controllers. They work without a problem under
Windows or with the Panasonic driver on ports with EHCI controllers.
I do not have PCs with OHCI-only controllers to test.
FYI:
- DOS Boot, Disk + USB Drivers, Info + Guides:
http://www.mdgx.com/drv.htm#DRV