piikea
Content Type
Profiles
Forums
Events
Posts posted by piikea
-
-
Related to the initial issue of this thread -- (& this may be a crazy / stupid question) but it is it possible to convert 1 partition of this 1TB ext HDD from FAT32 to NTFS? (Not necessarily as a permanent "configuration" but for data transfer to an NTFS HDD).
Yes, it is possible to do it. Win XP offers an app to do just that without loosing any data (which name is convert.exe) and Partition Magic can do it, too. Or you can simply reformat it (losing all data inside the partition). You can reformat each partition independently, as many times as you wish, without affecting the other partitions. However there is no need to do it for the reason you stated, unless you're dealing with files > 4GiB (-1byte, to be exact)... Else you can move data freely between NTFS and FAT-32, in either direction, without problems.
Well great. In was under the impression you couldn't just add data (mp3's, etc.) from FAT-32 system onto an NTFS system. If I get a new system I'd probably want to use NTFS but still be able to play my current mp3's on my old computer as well as put them on to the new one as well. I was envisioning having to convert the drive and it's data to NTFS from FAT-32. I'm glad I won't have to do those step!!
Thanks
0 -
I've used the Panasonic drivers floppy's w/ NG 2003 many times in the past & they "work" or enable my ext 80GB HD to be seen (& imaged to / from). However as you said it won't recognize larger drives (a 1TB ext HD in my case). They have at times been awfully finicky. Just the other day I had to use them & for some unknown reason it would only recognize the ext HD once out of about 10-15 tries. I was able to image a partition to the ext HD but then was never able to get it recognized subsequently to restore said image to the computer. I finally had to copy the image to my 2nd int HD which is of course recognized in NG & restore from there.
Unfortunately I can't provide answers or solutions
others probably will though!0 -
Related to the initial issue of this thread -- (& this may be a crazy / stupid question) but it is it possible to convert 1 partition of this 1TB ext HDD from FAT32 to NTFS? (Not necessarily as a permanent "configuration" but for data transfer to an NTFS HDD).
0 -
That's good to know that option (iv) works.. thanks! I've created a custom CONFIG.SYS file with multiple menu items for the various driver combinations and I'd like to edit it to add the additional options but I'm not sure if there's a limit for the number of menu items. I'll have to do some research into that.
Have you run into the "divide overflow" error cited earlier? The only time I've encountered that was trying to access a 1.0 TB external HDD. Every driver gave that error except ASPIDISK.SYS as I recall. I think you said you've successfully accessed a 1.5 TB external HDD?
Maybe you can post your "custom CONFIG.SYS file"? I was unsure if it would work properly with all the drivers (i) through (iv) all on the same floppy(s).
0 -
IF the 1TB ext HDD is going to be "iffy" or less stable/reliable it isn't worth the headache.
True. But even if you decide to sell it and maybe get another one, perhaps smaller... or none at all, in any case, now you know all you need to partition / format your next HDD to suit perfectly your needs. During the 1 TB disk tenure with you you probably learned many things you'd never envisaged you one day would. So it's not a total loss.
BTW, I'd give options (i) and (ii) a try. I think ASPIEHCI.SYS/GUEST.EXE may work.
No, not at all. I am still using the 1TB drive for data storage so I am grateful to have it (& for everyone's help here in formatting it, etc). Ideally I could also store system back-up image on it but I can continue using the 80GB ext HDD for that. I will still fiddle around w/ the various driver combo's & post results if I am successful!
0 -
Here: dosdrvr.exe... You'll get to a page in Japanese, but the drivers are in English..... ......Once you get dosdrvr_exe, don't run it, but instead open it with 7-zip or WinRAR and grab ASPIDISK.SYS v. 4.01b from inside it. You need to improve your Google-fu, piikea!
My previous Google-ing had only found discussions of the problem & links that didn't work. I did get to Adaptec site initially as well but even then couldn't locate it! Not sure I would've discovered it inside dosdrvr.exe.
Anyway, I hoped Prozactive's experience would've been a "quick solution" to mine but aspidisk.sys ultimately did not work in my case. Same "overload" error.
I will still have to try another combo.
EDIT:
Or better yet stick w/ my current back-up "protocol" which uses the Panasonic USB Drivers disks & an 80GB ext HDD - I know it works properly (since I have had to use it a couple times to restore my system). IF the 1TB ext HDD is going to be "iffy" or less stable/reliable it isn't worth the headache.
0 -
A "divide overflow" error is usually caused by a HDD that is too large for the driver(s), usually DI1000DD.SYS. I've experienced it when using a 1TB external HDD. As I recall, ASPIDISK.SYS was able to handle the drive but not DI1000DD.SYS or NJ32DISK.SYS.
Given this is dealing w/ the same size drive.....& potentially a shortcut to try before resorting to the more involved trial & error ones. Problem is I can't anywhere to download APIDISK.SYS. I've found it discussed alot but no one ever mentions where to get it & if they do the link is outdated, etc.
0 -
Yes. From DOS, I suppose.
Try:
(i) ASPIEHCI.SYS (v.13 09-May-2003) + GUEST.EXE (v. 8.5 or later)... the IOMEGA drivers
(ii) USBASPI.EXE (Panasonic, v. 2.28) + DI1000DD.SYS (Novac, v 2.00)... the "Motto-Hairu" drivers.
(iii) ASPIEHCI.SYS (v.13 09-May-2003) + DI1000DD.SYS (Novac, v 2.00)...
(iv) USBASPI.EXE (Panasonic, v. 2.28) + GUEST.EXE (v. 8.5 or later)...
(v) try all the above with previous versions of USBASPI.EXE (v. 2.26) or USBASPI.SYS (v. 2.24, 2.20, 2.15 and 2.06)...
(vi) try DUSE.EXE (I haven't got *any* experience with it).
I "think" the set of 2 floppy's I've been using is " (iii) " - although they are the "Panasonic" drivers(?). There only .sys files on them, i.e., no .exe's. It shows as v. 2.06 & Ver 2.00. I switched v. 2.06 with v. 2.20 which didn't work either. Also got an error:
Available ID = 0
Your program caused a divide overflow error.
If the problem persists contact your program vendor.
Rather than complicate matters - suffice to say that version doesn't work. I will have to try some of the other versions & see.
Thanks
0 -
Notwithstanding any aversion to Symantec products - does anyone have any idea on getting the 1TB ext HDD to be "seen" in Ghost?
0 -
The BSOD's are fewer these days so am I leaving well enough alone for now. I was using Ghost 2003 w/ my other ext HDD (a WD 80GB) with a so-called "Universal USB 2.0" drivers set on floppy's which does enable Ghost to recognize it but this new 1TB ext HDD isn't. Looking into possible solutions where I originally got the floppy's many years ago but figured I'd ask here in case someone has an easy answer!
As rloew mentioned in an earlier reply about an enclosure's possible limitations - idk all the specs on this one but it's an EAGLE E series 3.5" sata to usb 2.0 external hdd enclosure (supposed to "work up to 1TB").
0 -
Are you stopping (using the Safely Remove Hardware, in the system tray) the removable media before actually disconnecting it?
Yes & it behaves properly as if disconnection occurred correctly.
In any case, explicitly flushing the removable drives before removal should help if the case is the one described in KB284969... and Mark Russinovich's Sync does exactly that, so here's another thing to try.This mentions Client: Windows XP or above & Server: Windows Server 2003 & higher.
Holding off on these 2 updates for the moment.
BTW -
The latest BSOD showed: " error : 0D : 0068 : 000029EA " Which may or may not be the same or related to the VxD one.
To jaclaz - -
I'm no fan of NAV or Roxio either. My suspicion is WMP (which has some connection to Roxio but it also is in a Logitech [webcam] folder so I don't want to remove it completely) however, instead of those 2. Also I would have to completely uninstall NAV to get rid of everything that has nav in the filename - some 20 objects (dll's, .vxd, .sys, .exp).
0 -
OK. Here's my shortlist of possible problem candidates:
Yep they are all legit & on system before 2008.
IPVNMON = Visual Network Monitor
RT WINDOWS = REALTIME EXECUTIVE
Most NAV related tho' the 2 above I'm not sure what they are (exc. maybe VPN related & Real Player related "thing") but they been there.
They almost always occur after having had an ext HDD connected then dis-connected but usually not until I go to reboot. It has happened a few times going from 1 partition to another in Windows Explorer as well - in which case the BSOD is immediate. Neither scenario occurs every time so isn't reliably re-creatable....if that's even a word!
0 -
Your BSOD is related to a VxD... So, get the fantastic APSoft VxDView, and install it. Then post the full list of loaded VxDs it'll provide you. Let's see what we do find out.
0 -
If you were able to substitute USBHUB20.SYS in windows (i. e.: windows didn't prevent you from doing it), It should be enough. But do check its version (by right-clicking on it, then going to "Properties", then "Version"), to make double sure you actually had success at substituting USBHUB20.SYS. If so, the occasional BSODs you're still experiencing may be related to other sources, but if the frequency of the BSODs is less, at least part of the problem is solved.
Yes, I renamed the existing one then added it & rechecked - it IS 5.0.2195.6891.
(idk if it matters but USBHUB.SYS is 4.90.3000.0).
Strangely the BSOD's don't occur right when the ext. HDD (or drives) are "disconnected" - only later, whenever it is I go to restart. Sometimes it will be the BSOD as attached here. Other times it will be one saying "disk write error" (idk if any "write errors" actually occurred or not).
I'm pretty sure the BSOD's are related to the 1TB ext HDD (required) changes since I'd been using my other ext. HDD and a Card Reader for several years w/o ever having a BSOD. No matter, it is a fairly "manageable" problem.
0 -
The active copy of USBHUB20.SYS is located in C:\WINDOWS\SYSTEM32\DRIVERS.
You should rename it (say, to USBHUB20.VIA), not delete it, just in case.
Then you add the USBHUB20.SYS v. 5.0.2195.6891 from NUSB33.
This should be all done in True DOS (i. e., after booting from a floppy).
Other copies of USBHUB20.SYS may exist, and ought to be findable by searching, but are not the active one.
I did this in Windows but still get blue screens occasionally. Don't know how to in True DOS so ill just let it go & live w/ it. It's not that big a deal to work around.
BTW, if you are in doubt whether more RAM is beneficial or detrimental, the simplest way to establish it is by (I) timing some assorted events like opening IE to the default page, opening a Word document and/ or an Excel spreadsheet, and other things relevant for you to create a benchmark and then (II) removing temporarily some RAM and timing your benchmark again. Then you'll know for sure, specifically for your case.
Perhaps I will attempt this when I have enough free time & am feeling daring.
Thanks
0 -
Did you do this:
As for the BSODs, my guess is the USBHUB20.SYS v. 4.90.3000.1 installed by USB20DRV is great for VIA chipsets but not so much for Intel chipsets, which is your case. I'd like to substitute it for the one present in NUSB 3.3, which is v. 5.0.2195.6891. You can extract it from the NUSB33 installer by opening it with 7-zip. But it's best to install it from true DOS.and nothing changed?
I haven't yet. Couldn't remember where to put it & couldn't locate the answer amongst the threads about it. Also, I am getting less blue screens & so was leaving well enough alone for the moment. It may be rather non-scientific, but in my subjective experience w/ this computer, it will balk at changes (& other things) but often adapts over time & works ok without further intervention.
* On a side note -
I have had doubts since installing extra RAM beyond 512 that it is either:
actually not being "used" - or - perhaps there is a "memory leak"
since the computer seems, if anything, slower. Especially the internet loading webpages which all the usual remedies has not improved and is not the connection as all speedtests overtime show consistently proper speeds. This "slowness" is even after reboots when system resources are 84% available.
Anyway, if anyone has any opinions please provide. Perhaps a new thread would be in order?
0 -
When did the BSODs start happening? After adding USB20DRV or even before it you did already have them? You may be having BSODs for more than one reason... is the message in the BSOD's always the same?
No, never had this issue at all before the changes made to try & get this ext HD going. You know I hadn't really paid close attention to what the blue screens actually said because they seem to be the sort of generic ones that don't tell you much except maybe a long string of random numbers/letters & saying press Ctl Alt Del to restart, etc. I will take note next time it happens & see.
0 -
Well after 6 days worth of Thorough Scandisk-ing the drive is up & ready. Thanks to dencorso, jaclaz & others who have helped along the way.
Now to try & deal w/ the frequent bluescreen errors I'm getting now. It has happened at various times: sometimes connecting, sometimes disconnecting, also w/o any ext HD connected & I'm accessing different partitions on the int HD's. Also several times after disconnecting it & using computer for awhile then go to restart it will happen & basically freeze the computer.
0 -
You can do one then do other things for a couple of days before checking the second and so on... Why do all 3 in a row?
True. I will have to do a few things in between but I am in somewhat of a "hurry" to transfer some stuff to the ext HD since my internal HD's are filled to the hilt & as things are I cannot add anything nor do much w/ no space to work with. This whole process is going to take even a bit longer. (As well as the BSOD's, Usher's Tweak, etc.)
0 -
It's tough....I can do very little on the computer in addition to that right now& its like molasses slooooow. I could try Norton's Scandisk on the next one - I don't recall if that's any faster or not.
0 -
At the present rate it is going to take 2 days EACH to Scandisk the (3) 300GB partitions.
0 -
No, I'm not doing anything w/ it just yet.
0 -
See my previous post - was called away suddenly before I was able to finalize it.
OK, got it & extracted. I had been looking in nusb.zip from a thread in this forum. I can't do anything w/ it at the moment since Scandisk is running on the ext HD. Was just getting a head start by locating & getting it for future use. I can go ahead & replace the file just can't reboot to see what happens.
0 -
I can boot w/ a floppy for substitution. Is 7-zip different than say winzip? Not familiar w/ it. Will have to wait since I won't be able to restart etc w/ Scandisk running for 300GB's at a time!
There's no hurry. It can wait. 7-zip does about everything WinZip does and then some. It's quite possible WinZip is enough for the task. Then again, 7-zip is a powerful freeware you ought to add to your toolbox, IMHO.
Tried locating NUSB 3.3 to download & try & extract the driver or .sys file but haven't found it.
0
others probably will though!
Ext HDD's greater than 137GB under Win ME
in Windows 9x/ME
Posted
I was getting similar BSOD's w/ my ext 1TB HDD with WMe OS too but was never able to resolve the issue. I've since added XP onto the same PC & using same ext HDD has no issues. Unfortunately I had/have no solutions I can provide.....sorry!