| 1. |
Solve : getting dos to read firewire device? |
|
Answer» Hi I've not made any progress with this endeavor. I am trying to get dos to run firewire 1394b devices. Here are the codes I have tried so far and the error messages when they load at the startup. See The 3rd Post Here...The drivers shown in the 6th Post are the only ones that work for me. Sometimes it doesn't find the drive the 1st time, so I just reboot and it will find it the 2nd time.I have temporarily suspended the firewire-dos project because of unresolved issues with those drivers. I am now trying to use dos-usb configurations. I got the Panasonic drivers USBASPI.SYS and DI1000DD.SYS in the configuration menu. It detects my usb flash drive device as EHCI, but how do I assign it a drive letter so I can get DOS to access it? I tried DI1000DD.SYS /dh but it just said 'invalid drive specification.' I want to be able to use DOS to copy my external IDE hard drive to the partition on my pc that dos doesn't reside in. When I am done, I want it to look like C:\DOS and D:\Win2K on the internal scsi drive. Of course it will have to be formatted with Fat32 as DOS won't read NTFS. I changed the bios reading from legacy floppy to FDD but it really didn't change anything. Help, cause I am stymied again. Here is the configuration I am using presently. Device=C:\Dos\usbaspi.sys e/ w/ Devicehigh=C:\Dos\DI1000DD.SYS /df Do I need a specific line in the autoexe.bat so it will provide a drive letter?config.sys [Menu] menuitem=1394, 1394 Firewire Mass Storage menuitem=usbaspi, ASPI USB Mass Storage menudefault=usbaspi, 30 [1394] devicehigh=\DOS\himem.sys devicehigh=\Drivers\aspi1394.sys /int /all devicehigh=\Drivers\di1000dd.sys [usbaspi] devicehigh=\DOS\himem.sys devicehigh=\Drivers\usbaspi0.sys /norst /v /w devicehigh=\Drivers\di1000dd.sys [common] dos=high,umb lastdrive=Z _______________________________________ ______________________________ autoexec.bat not necessary. "di1000dd.sys" provides the drive letter. Well after some research, I made some useful discoveries. First, I was invited to include in a batch file various usb drivers. USBASPI0.SYS; USBASPI1.SYS; USBASPI2.SYS; USBASPI3.SYS; USBASPI4.SYS so DOS can cycle through each one and use the one it chooses. The second revalation comes in the knowledge that DOS will not open any drives that are larger than 2gig. Since my cloned hard drive is over 10gig, that option is dead. Maybe I'll just end up putting LinuxMint on the extended drive instead. Quote from: PunkA on March 06, 2010, 02:21:29 PM ...DOS will not open any drives that are larger than 2gig....I don't know where you got that "fact", but it's not true. I have a 60GB USB drive and it works just fine with DOS 7 (Win98SE). I also have a USB/1394 120GB combo drive using the same DOS version.Alright, I've been wrong before. So I decided to scrap MSDOS6.22 and install 8.0 that I found on the web in winimage. I guess I am just stubborn. If anyone wants the link, just let me know. I didn't realize that your hard drive size should not be larger than 2gig to load it. DOS 6.22 is FAT16, DOS 7.1 is FAT32; that explains it. DOS 8 is from WinME, DOS7.1 is from Win95B, Win98, Win98SE I wouldn't use anything from WinME. WinME didn't use DOS. http://www.ntfs.com/ntfs_vs_fat.htm http://en.wikipedia.org/wiki/Comparison_of_x86_DOS_operating_systemsI suffer from the same affliction as Oscar Wilde. I can resist anything except temptation. I went copied the DOS 8.0 files to my C: drive. I would still like to be allowed to access my external hard drive with its fw interface. It gives me a choice of cd rom support at the start up. But no choice for a mouse pointer. C:\Autoexec.bat echo off path=C:\Windows;C:\windows\command \hibinv.exe call \checksr.bat IF "%config%"=="QUICK" Go To Quick set EXPAND=Yes set DIRCMD=/O:N set Lg l Drv=27* 26 Z 25 Y 24 X 23 W 22 V 21 U 20 T 19 S 18 R 17 Q 16 P 15 set Lg l Drv=%Lg l Drv % O 14 N 13 M 12 L 11 K 10 J 9 I 8 H 7 G 6 F 5 E 4 D 3 C cls call setramd.bat %Lg l Drv% set temp=C:\ set tmp=C:\ path %RAMD%:\;a:\;%path%;%CDROM%:\ copy command.com %RAMD%:\ >NUL set comspec=%RAMD%:\command.com copy extract.exe %RAMD%:\ >NUL copy readme.txt %RAMD%:\ >NUL :EXT %RAMD%:\extract /y /1 %RAMD%: ebd.cab >NUL echo The diagnostic tools were successfully loaded to drive %RAMD%. echo, IF "%config%"=="NOCD+ GOTO QUIT IF "%config%"=="Help" GOTO HELP LH %RAMD%"\::IF MSCDEX doesn't find a drive... IF ERRORLEVEL 1 SET CDPROB=1 cls call help.bat :: GOTO QUIT :QUIT call fixit.bat rem clean up environment variables set CDPROB= set CDROM= set Lg l Drv= GOTO QUICK :QUICK C:\Config.sys [Menu] menuitem=HELP, Help menuitem=CD, Start computer with CD support. menuitem=NOCD, Start computer without CD rom support. menuitem=QUICK, Minimal boot. menudefault=Help,30 menucolor=7,0 [HELP] device=Oakcdrom.sys /D:mscd001 device=btdosm.sys device=flashpt.sys device=aspi2dos.sys device=aspi8dos.sys device=aspi4dos.sys device=aspi8u2.sys device=aspicd.sys \D:mscd001 devicehigh=ramdrive.sys /E 2048 [CD] device=oakcdrom.sys /D:mscd001 device=btdosm.sys device=flashpt.sys device=btcdrom.sys device=aspi2dos.sys device=aspi4dos.sys device=aspi8dos.sys device=aspi8u2.sys device=aspicd.sys /D:mscd001 devicehigh=ramdrive.sys /E 2048 [NOCD] devicehigh=ramdrive.sys /E 2048 [QUICK] [COMMON] files=10 buffer=10 dos=high,umb stacks=9,256 lastdrive=z device=display.sys con=(ega ,,1) country=044,850, country.sys install=mode.com con cp prepare=((850)ega.cpi) install=mode.com con cp select=850 There was not a mouse driver included with the copied boot disk files to the C: drive so is it possible to import a driver to have mouse support? Also DOS 8.0 created a D:\ drive for diagnostic tools called D:\ MS-RAMDRIVE. These are the files it displays in D: ATTRIB.EXE CHKDSK.EXE COMMAND.COM DEBUG.EXE EDIT.COM EXT.EXE EXTRACT.EXE FORMAT.COM HELP.BAT MSCDEX.EXE README.TXT SCANDISK.EXE SCANDISK.INI SYS.COM And what about the matter of getting usb and firewire detection and assigning drive letters? Will aspi1394.sys, di1000dd.sys and usbaspi.sys, still do the trick here? At least now I have FAT32 interface going. Quote from: Computer_Commando on March 07, 2010, 03:43:11 PM WinME didn't use DOS. Windows ME is still based on a DOS core exactly like windows 95, 98, and 98SE. MS just hid the option to boot into MS-DOS mode. PunkA: Um, and what exactly would you use mouse support for... you cannot use the mouse at the prompt, just within other programs. I have no IDEA with regards to mouse drivers; I always use mouse.com included with DOS, but since MS never ACTUALLY released any version of DOS beyond 6.22 and they are in fact hacked versions of the boot disks that are created by windows I don't know what would be included with them.Ok, so Mr. Billy Boy decided to X the bootable version. Does that mean a hack doesn't exit to override it so that it will boot from the hdd? I checked the format and somehow it was still formatted for FAT16. Don't know how that occurred but now I will use the system bios to change it to FAT32. Quote from: PunkA on March 09, 2010, 04:27:24 PM Ok, so Mr. Billy Boy decided to X the bootable version. Does that mean a hack doesn't exit to override it so that it will boot from the hdd?it's not a "hack"... it's two commands- boot to the floppy and use: Code: [Select]format C: /s sys C: Additionally what I was saying had nothing to do with legal issues or anything like that, necessarily- I was just pointing out the fact that what you are using is a boot disk, and only includes the "bare necessity" external commands- no surprise that mouse.com is not considered a necessity. Quote from: PunkA on March 09, 2010, 04:27:24 PM Don't know how that occurred but now I will use the system bios to change it to FAT32. no you won't. |
|