InterviewSolution
Saved Bookmarks
InterviewSolution
| 1. |
Solve : getting dos to read firewire device? |
| Answer» <html><body><p>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.<br/><br/>DEVICEHIGH=C:\HIMEM.SYS /testmem:off<br/>DOS=HIGH,UMB<br/>DEVICEHIGH=C:\OAKCDROM.SYS /D:mscd001<br/><a href="https://interviewquestions.tuteehub.com/tag/device-11244" style="font-weight:bold;" target="_blank" title="Click to know more about DEVICE">DEVICE</a>=ASPIATAP.SYS /e/v<br/>{IOMEGA SCSI TO ATAPI INTERFACE MANAGER}<br/>"ADAPTER NOT PRESENT"<br/>DEVICE=ASPI1394.SYS /int/all<br/>{IOMEGA ASPI 1394 Firewire; V. 1.06}<br/>"Cannot find valid scsi adapter for ASPI driver"<br/>DEVICEHIGH=C:\EMM386.EXE /NOEMS<br/>DEVICEHIGH=C:\SMARTDRV.EXE /DOUBLE_BUFFER<br/>FILES=30<br/>STACKS=0,0<br/>BUFFERS=20<br/>LASTDRIVE=Z<br/><br/>THERE IS NO RECIPROCAL CODE IN AUTOEXEC.BAT. DOES ANYONE CARE TO TRY TO HELP OUT AND MAYBE PROVIDE SOME SOLID <a href="https://interviewquestions.tuteehub.com/tag/feedback-25484" style="font-weight:bold;" target="_blank" title="Click to know more about FEEDBACK">FEEDBACK</a> WITH THIS PROBLEM?<a href="http://www.techtalkz.com/drivers/6127-lookin-dos-driver-firewire-ieee-1394-a.html"><strong>See The 3rd Post Here...</strong></a>Ok, I went there and used those drivers and all I got was a black screen when I tried to run it. But it would be helpful to know why DOS complains with "Adapter not present" when I try to run the ASPIATAP.SYS file. Is it because I don't have the controller driver installed in DOS?Most likely...yes. Quote from: patio on March 01, 2010, 01:40:30 PM</p><blockquote><a href="http://www.techtalkz.com/drivers/6127-lookin-dos-driver-firewire-ieee-1394-a.html"><strong>See The 3rd Post Here...</strong></a><br/></blockquote> The drivers shown in the 6th Post are the only ones that work for me.<br/>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.<br/><br/>Here is the configuration I am using presently.<br/><br/>Device=C:\Dos\usbaspi.sys e/ w/<br/>Devicehigh=C:\Dos\DI1000DD.SYS /df<br/><br/>Do I need a specific line in the autoexe.bat so it will provide a drive letter?<strong>config.sys</strong><br/><br/>[Menu]<br/>menuitem=1394, 1394 Firewire Mass Storage<br/>menuitem=usbaspi, ASPI USB Mass Storage<br/>menudefault=usbaspi, 30<br/><br/>[1394]<br/>devicehigh=\DOS\himem.sys<br/>devicehigh=\Drivers\aspi1394.sys /int /all<br/>devicehigh=\Drivers\di1000dd.sys<br/><br/>[usbaspi]<br/>devicehigh=\DOS\himem.sys<br/>devicehigh=\Drivers\usbaspi0.sys /norst /v /w<br/>devicehigh=\Drivers\di1000dd.sys<br/><br/>[common]<br/>dos=high,umb<br/>lastdrive=Z<br/>_______________________________________ ______________________________<br/><strong>autoexec.bat</strong> not necessary. "di1000dd.sys" provides the drive letter.<br/><br/>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<blockquote>...DOS will not open any drives that are larger than 2gig....</blockquote> 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.<br/>DOS 8 is from WinME, DOS7.1 is from Win95B, Win98, Win98SE<br/>I wouldn't use anything from WinME. WinME didn't use DOS.<br/><br/><a href="http://www.ntfs.com/ntfs_vs_fat.htm">http://www.ntfs.com/ntfs_vs_fat.htm</a><br/><a href="https://en.wikipedia.org/wiki/Comparison_of_x86_DOS_operating_systems">http://en.wikipedia.org/wiki/Comparison_of_x86_DOS_operating_systems</a>I 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.<br/><br/>C:\Autoexec.bat<br/><br/>echo off<br/>path=C:\Windows;C:\windows\command<br/>\hibinv.exe<br/>call \checksr.bat<br/>IF "%config%"=="QUICK" Go To Quick<br/>set EXPAND=Yes<br/>set DIRCMD=/O:N<br/>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<br/>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<br/>cls<br/>call setramd.bat %Lg l Drv%<br/>set temp=C:\<br/>set tmp=C:\<br/>path %RAMD%:\;a:\;%path%;%CDROM%:\<br/>copy command.com %RAMD%:\ >NUL<br/>set comspec=%RAMD%:\command.com<br/>copy extract.exe %RAMD%:\ >NUL<br/>copy readme.txt %RAMD%:\ >NUL<br/>:EXT<br/>%RAMD%:\extract /y /1 %RAMD%: ebd.cab >NUL<br/>echo The diagnostic tools were successfully loaded to drive %RAMD%.<br/>echo,<br/>IF "%config%"=="NOCD+ GOTO QUIT<br/>IF "%config%"=="Help" GOTO HELP<br/>LH %RAMD%"\::IF MSCDEX doesn't find a drive...<br/>IF ERRORLEVEL 1 SET CDPROB=1<br/>cls<br/>call help.bat<br/>::<br/>GOTO QUIT<br/>:QUIT<br/>call fixit.bat<br/>rem clean up environment variables<br/>set CDPROB=<br/>set CDROM=<br/>set Lg l Drv=<br/>GOTO QUICK<br/>:QUICK<br/><br/>C:\Config.sys<br/><br/>[Menu]<br/>menuitem=HELP, Help<br/>menuitem=CD, Start computer with CD support.<br/>menuitem=NOCD, Start computer without CD rom support.<br/>menuitem=QUICK, Minimal boot.<br/>menudefault=Help,30<br/>menucolor=7,0<br/>[HELP]<br/>device=Oakcdrom.sys /D:mscd001<br/>device=btdosm.sys<br/>device=flashpt.sys<br/>device=aspi2dos.sys<br/>device=aspi8dos.sys<br/>device=aspi4dos.sys<br/>device=aspi8u2.sys<br/>device=aspicd.sys \D:mscd001<br/>devicehigh=ramdrive.sys /E 2048<br/>[CD]<br/>device=oakcdrom.sys /D:mscd001<br/>device=btdosm.sys<br/>device=flashpt.sys<br/>device=btcdrom.sys<br/>device=aspi2dos.sys<br/>device=aspi4dos.sys<br/>device=aspi8dos.sys<br/>device=aspi8u2.sys<br/>device=aspicd.sys /D:mscd001<br/>devicehigh=ramdrive.sys /E 2048<br/>[NOCD]<br/>devicehigh=ramdrive.sys /E 2048<br/>[QUICK]<br/>[COMMON]<br/>files=10<br/>buffer=10<br/>dos=high,umb<br/>stacks=9,256<br/>lastdrive=z<br/>device=display.sys con=(ega ,,1)<br/>country=044,850, country.sys<br/>install=mode.com con cp prepare=((850)ega.cpi)<br/>install=mode.com con cp select=850<br/><br/>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:<br/>ATTRIB.EXE<br/>CHKDSK.EXE<br/>COMMAND.COM<br/>DEBUG.EXE<br/>EDIT.COM<br/>EXT.EXE<br/>EXTRACT.EXE<br/>FORMAT.COM<br/>HELP.BAT<br/>MSCDEX.EXE<br/>README.TXT<br/>SCANDISK.EXE<br/>SCANDISK.INI<br/>SYS.COM<br/><br/><br/>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.<br/> Quote from: Computer_Commando on March 07, 2010, 03:43:11 PM<blockquote>WinME didn't use DOS.<br/></blockquote> <br/>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.<br/><br/>PunkA:<br/><br/>Um, and what exactly would you use mouse support <em>for</em>... you cannot use the mouse at the prompt, just within other programs.<br/><br/>I have no <a href="https://interviewquestions.tuteehub.com/tag/idea-770073" style="font-weight:bold;" target="_blank" title="Click to know more about IDEA">IDEA</a> with regards to mouse drivers; I always use mouse.com included with DOS, but since MS never <a href="https://interviewquestions.tuteehub.com/tag/actually-848884" style="font-weight:bold;" target="_blank" title="Click to know more about ACTUALLY">ACTUALLY</a> 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<blockquote>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? <br/></blockquote> it's not a "hack"... it's two commands-<br/><br/>boot to the floppy and use:<br/> Code: <a>[Select]</a>format C: /s<br/>sys C:<br/><br/>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. <br/><br/><br/><br/><br/> Quote from: PunkA on March 09, 2010, 04:27:24 PM<blockquote>Don't know how that occurred but now I will use the system bios to change it to FAT32. <br/></blockquote> <br/>no you won't.<br/><br/><br/><br/></body></html> | |