risk_reversal

Well you could always try the Puppy suggestion or maybe SwissKnife For me this result has placed the external enclosure itself at the top of the hit list and would trigger my getting another one as my remedial strategy to cure this ill. Please correct me if I missed this in an earlier one of your posts but the Memorex flash drive is the only usb device that you have connected to your system (apart of course from the AcomData) ie have you tried your friend WD external on your system. Good Luck

Following your post I think that you can probably scrub out most of my earlier reply. Interesting though that your external enclosure is problematic on your pc and your friend's when the drive is connected during the boot process (hope I understood that correctly). If so try another usb device as per Multibooter's suggestion and boot system to see if error repeats. Good Luck

Sorry misunderstood that it was a USB cordless. In which case turning the turning USB Keyboard Support to BIOS would not likely make any difference. So BiNG has issues on both rigs. For complete clarity you are obviously running BiNG from a floppy ie to the dos interface. I guess that only leaves the external itself as the culprit ie chipset issue or perhaps the partitions on the external are corrupted in some way (can't see how it would give the results you have though). The way I would have proceeded if it were my external hard drive is as follows. 1. As per Multibooter, try another usb drive (disk or flash) on your rig and see whether the problem remains (and use BiNG also). 2. Remove the hard drive from the AcomData and replace with another and test. Have a look at Puppy, it's not difficult and won't take up any time. PuppyLinux.com. It's a small download 95Mb (make sure that you check the MD5) burn to ISO and just boot from the CD (For version go for a retro version with the older kernel say v4.1). Connect you external to Puppy at the Desktop and you will see it appear on the desktop (sda1). Find GParted in the menu and it will show the partitions. Make sure you unmount any drive prior to removal or shutdown (right click unmount, mounted drives have a green spot on them). You will also be able to access all files and folders on ANY hard disk on the pc. Great for solving issues. As a last thought on this. Your usb enclosure has a chipset (I have a Nexstar3 IDE with chipset Cypruss AL2PT) and perhaps your enclosure's chipset is the culprit and the common denominator. I appreciate that this is an irritating problem for you. It would drive me nuts also. Good Luck PS. when connecting the external are any other usb peripherals connected.

About a year ago I searched this very topic on this forum. The many posts to be found confirmed this. I purchased an external enclosure with a 250gb HDD and have had not probs. The HDD has a single partition has about 90gb left (so I am well over the 128GiB limit). In which case, then you would have had a 128GiB capacity limitation imposed but the mobos IDE controller. I guess that you can probably connect your external to a mobo with usb2.0 and use BiNG to extend the extended partition to occupy the whole amount. I use BiNG but have never tried using it with an external on usb 1.x. Boot with BiNG with the external disconnected and after BiNG has loaded connect the external to a usb port. Failing that you could boot with a Puppy Linux Live CD and use GParted (partition utility). After Puppy has booted and you connect the usb drive Puppy will detect it. I have an old Dell with usb1.x and Puppy finds the external. Many ways to get around the 128GiB limitations which are listed on this forum. Personally, I use 2 250Gb sata drives in a dual boot system with 98SE/XP. I overcome this by using the Promise controller which loads it's own drivers. Could always just to into Device Manger and fix the drive lettering for the external... My clear understanding is that there is no uninstall for NUSB. But I guess that if you deleted all the items listed under Universal serial bus controllers in Device Manager (inc usbstor.inf), this may work. You will need to post this as a new question. I would be interested in the replies. Mutiple devices on the usb bus can at times become problematic. Cordless usb mice for me are a nono. I use ps/2 and that will not change anytime soon. Are you also using a powered usb hub. This may help. In respect of usb clashes, my understanding is that if you have 10 usb devices, each is not assigned a separate IRQ, it is the usb bus that has that function, if you see what I mean. Now your usb controller may be clashing with something else eg I had a NIC which would lock up when using my usb printer. Move the card problem solved. But you do need to know the IRQ shares. A guess, maybe the usb enclosures's chipset has issues.....I don't think it's to do with the 4 logical partitions. Well personally I have been having a fun time figuring out how to get a wireless NIC to operate with WPA encryption on 98se. Have now solved that issue but was a bit tedious. Good Luck PS Not sure. If you have a usb wireless mouse should this not be enabled? If you want to try setting to BIOS but feel edgy, why not disconnect your hdds and try it at least there will be no harm done. You can just boot to a dos floppy or maybe a Puppy Linux Live CD.

In the first instance, have you tried setting Support to USB Keyboard to Disabled. I must admit I never allow my external hdd to be connected to my pc at boot (if they merely contain data). Much prefer to just connect it afterwards. Avoids any possible problems and much safer in my opinion. External usb enclosures are not subject to this barrier. Hdds are allowed up to 4 primary partitions. One of those primary partitions can be an extended partition containing a number of logical partitions. Creating an extended partition on the external hdd allows for greater flexibility ie the set up that you have. But you could just as easily created 4 primary partitions. NUSB v2.x installs just the usb drivers and works with usb1.x and usb2.0. NUSB version 3.x add usb2.0 drivers also but you have to uninstall your usb2 controller driver prior to it's install. I have usb2.0 on my mobo(s) but use NUBS v2.x as the mobo's usb2.0 controller is working fine with no issues. Can't see why it is a problem to just disconnect via the NUBS systray icon. I also occassionally forget and sometimes get a BSOD. Does this have anything to do with the fact that the external HDD has an extended partition rather than a primary one. I very much doubt that. I will have a stab at this one. WD retail external enclosures have proprietary data back up software. If your friend also has system restore turned on, I am guessing that the freeze is due to XP trying to reconcile the contents of the system information folder (system restore) from the WD with your drive and it is getting confused. If I have understood your question correctly. Bottom line, safer to have the external hdd disconnected at boot. Your friend's set up works but the potential for errors to occur is in my opinion great. Good Luck

Many thanks for the registry entries eidenk as well as for the prog. all the best Cheers

ZA v6.1.744.001 is the last one that supported 98SE. I am running it on an other pc with no issues. The only thing that needs to be done is REM out a line that ZA adds to autoexec.bat (you can even delete it). Personally, I find that it does not slow the system down at all apart from at shut down. Adds about 5-6 secs. System boots to desktop with full internet in 57secs. Try it out but before download the how to remove instructions. I also tried Kerio 2.15 the last free version (which works on 98SE). Small footprint, light on resources but from my extensive readings the raw version needs more detailed rules than the very lax default ones. At least that is what I understood. There are many posts about from people who have created rules and which you can just plug in eg as per below. http://www.wilderssecurity.com/showthread.php?t=219203 Good Luck

Many thanks for your reply MDGx. Well it seems that the registry hack for this will not work and will have to resort to individual folder as per your advice. In respect of drive icons ie HDD, opticals & A:\ I was using this registry hack which I found and which I am sure you have seen before and seems easier. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrenTVersion\Explorer. If a subkey named driveicons is present, open it; if not, right-click in the right-hand pane, select New | Key and name the key driveicons. Under the driveicons key, find or create a subkey named C (or the letter of the drive whose icon you want to change). And under this C key find or create a subkey named DefaultIcon. Double-click the (Default) entry in the right-hand pane and set its value to the full pathname of the icon-holding file, a comma, and the icon index. [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\explorer\DriveIcons] [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\explorer\DriveIcons\C] [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\explorer\DriveIcons\C\DefaultIcon] @="C:\\WINDOWS\\Desktop\\Xpicons.dll,8" etc for other HDD, opticals and floppy Many thanks for your help

Trying to change the folder icon but running into problems. I found a post which gave the 2 following locations which need to be changed. [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\explorer\Advanced\Folder] "Bitmap"="C:\\WINDOWS\\SYSTEM\\SHDOC401.DLL,4" [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\explorer\Advanced\Folder\Hidden] "Bitmap"="C:\\WINDOWS\\SYSTEM\\SHDOC401.DLL,4" I pointed to the new *.dll with correct dll,x (ie C:\Windows\Desktop\Xpicons.dll,3 but the folders remained unchanged. In the first instance are the above 2 registry locations correct? Many thanks

FYG, even on another mobo which is usb 2.0 enabled, I also installed NUSB v2.4. Reason being that I have a Via based board and the installed USB 2.0 controller drivers where working fine and I did not want to change that. Upshot is that the v2.4 NUSB driver also work fine on that board.....

Time to boot 57s. Goes through Promise controller bios (which adds about 5-7s) and then boot manager. Time to shutdown 12s (with internet connected). Delay caused by ZA firewall which adds about 4-5 secs to process

I have a usb 1.1 mobo running NUSB v2.4 with no issues. I saw no need to install v3.x which adds drivers for USB 2.0 controllers (plus has a slightly more comprehensive .INF file which can just be copied over). v2.4 was the last version which had just the generic usb drivers. On my set up has detected Corsair 1Gb & 4Gb flash drives and 250Gb external HDD amongst others. Link to other NUSB versions below http://www.technical-assistance.co.uk/kb/usbmsd98.php Good Luck

Many thanks for your reply Mijzelf. Also apologies for posting in the wrong forum. Cheers

A quick question please in respect of the size of the HDD cache. Is there a maximum HDD cache size requirement that exits for 98SE. My current HDD has an 8Mb cache. If I change my HDD to one with a 16 or 32Mb cache, there is no reason to assume that this will not work. Apologies for perhaps asking a silly question Many thanks Cheers

glocK_94, many thanks for letting me know that you had the same issue with your Shuffle + Winamp under XP. At least now I know that the winamp plugin is responsible and I can look for another solution. I have taken your advice and looked at both Yamipod and Anapod. Anapod seems fine, although the main draw back with the free version is that you can only copy one song at a time. Yamipod also worked but required an installation of Quick Time. FYG I installed Quick Time Alternative and Yamipod seemed happy with that. Cheers

I am having problems with 98SE and the above combination. I have NUBS 2.4 installed which correctly detected the ipod. A 1Gb Shuffle 2.0. I installed Winamp v5.35 (amongst others) with the Portable Device Support ie ml_pmp. Winamp detects the ipod Shuffle and I can copy songs onto the Shuffle without issues. If I unplug the Shuffle the songs will play. The problem I am getting is as follows. When the ipod is connected to Winamp if I delete any songs they show as being deleted within Winamp but still remain on the Shuffle. Winamp also shows the ipod with less available space. I have read post about ipods doing this and it apparently relates (I think) to the database file being corrupted the files is Tunes.DB. I am getting this with a freshly restored ipod so the problem begins immediately. In the first instance, I was wondering (a longshot) whether it might NUBS creating this problem. Also is anyone using NUBS with Winamp and any ipod getting this? I did try to install the NUBS + Winamp + ipod on another clean 98SE system with the same results. I tried several versions of Winamp with the included ipod plugin (ml_pmp), 5.32 worked fine but same issue as 5.35. 5.24 locked up virtually immediately. I also tried the ml_ipod plug in on v5.13, 5.24, 5.32 & 5.35 which resulted in Winamp giving the same error namely that 'Winamp has caused a stack error in module Kernel32.dll at 017F:BFF7429F". I tried googling this but no results. I also go this identical error message on two 98SE systems. An unusual problem but I would welcome users comments as to whether they have experienced any similar issues. Many thanks for any info provided Cheers

I must admit that having used various versions of PM over the past 6-7 yrs, I have never had one instance when PM held back unpartitioned free space that I could not use in the way that you have described. The only stipulation that I understand exists is that PM requires partitions be <90% full. Cheers

I dual boot 98SE/XP on my pc but generally boot into 98SE. My system specs are: Mobo: Asus A8V Deluxe Rev2.0 (VIA K8T800Pro) CPU: AMD SD4000+ (single core - overclocked by 20%) VGA: BGF 6800GT (AGP) OCZ 1Gb Ram (dual channel) The system boots very fast and once loaded it is really quick and very stable. EDIT: SecondEditor, I take it 98SE cannot recognise both cores of your AMD x2 cpu....

My experience with PM is as follows. Started used this prog pre Norton when it was still made by PowerQuest. Version 6 was the first one I tried. PowerQuest stated that this version was tested with HDD up to 40Gb. I used v6 on 60Gb HDDs and had no problems. When I upgraded a 60Gb HDD to a 120Gb HDD and used v6 to transfer info (60gb ->120gb) it caused errors which resulted in corruption of the MBR of the 120Gb HDD (according to PowerQuest support). After several failed attempts with v6, I purchased v8 (still from PowerQuest) and there were no errors. v8 was apparently safe with drives of 160Gb. About 2 years ago when I purchased a SATA 250Gb HDD and bought PM8 from Norton this worked fine. However, I always run PM from the dos diskettes and do not install the prog. It much easier that way and in any case even if the prog is fully installed it will still reboot to dos to make any changes. The only thing I do install is the boot manager BootMagic on the first primary and active partition. And for total clarity, you can use PM on a new drive to create a partition and format it too by way of the dos diskettes. I also find it a lot faster than FDISK. I have also tried BiNG (free version) which can handles extremely large HDD. It also works in dos mode and it is also fine. There are of course many more. Good Luck

I have no HDD attached to the mobo's IDE (PATA) controllers. My 250Gb SATA HDD is connected to a SATA port of the on board Promise SATA controller. When the post sequence begins, it shows the main 'post' screen relating to the AMI bios. The AMI bios only detects the (2) optical drives which I have connected to the IDE connectors. Then the Promise bios in turn posts with the info which I listed above. In my Device Manager, when viewed by connection, I have and entry headed Win98-ME Promise SATA378 IDE Controller, and if I expand this I get the following ST3250823AS (ie my HDD model) The reason I have my HDD connected to the on board Promise SATA controller instead of the VIA SATA controller (VT6420) is because my cpu AMD SanDiego 4000+ is o/ced and on this mobo the VIA SATA controller cannot handle o/cing and leads to HDD corruption. I hope that I have clarified the point. The reason for this thread is because I want to add another HDD to this system (which has been fuly functional since I built it just over 2 years ago). I wanted to attach the new HDD to the on board Promise SATA controller which has 2 SATA ports / connectors and wanted clarification in respect of issues with 98se as I stated in my earlier posts. The info which I would appreciate and which Eck brought to my attention is confirmation (or not) that my current set up is free of the 137Gb limitation imposed natively by 98SE. Apologies if I had not clearly explained myself previously. Many thanks for your help. Cheers

Many thanks for your replies. Ok so just to be clear for a PATA HDD the following applies As regards SATA, have some confusion. My system currently as follows Asus A8V Deluxe Rev2.0 Via K8T800Pro with VT8237 Southbridge Via Sata Controller Promise SATA controller (on board) Seagate 250Gb SATA HDD After fresh install of 98SE: 1. I installed the 98SE Promise SATA Controller driver in folder 378ATA (this enables the Promise controller to run in non raid mode). In Device Manager, I have an entry headed SCSI Controller and if I expand it says Win98-ME Promise SATA 378 IDE Controller. 2. I installed the Via 4-1 v4.43 In the main bios I have disabled the Via SATA bios and enabled the Promise bios and selected it to run in IDE mode. So when system boots, the main bios shows, then the Promise bios which shows the following: SATA 378TX2 Plus Bios version 1.00.0.33 DO ST3250823AS 232Gb ULTRA DMA 6 IDE BUS MASTER ENABLED Now am I to understand from you comment Eck that the 98SE 28bit LBA drivers are not being used and instead the Via / Promise Sata Controller drivers are being used instead ie the Promise SATA controller is acting in the same way as a PCI ATA card and adding 48bit LBA functionality. If what I have said above is correct Eck, then I am more confused when you say Many thanks for your help Cheers

Many thanks for your reply Mijzelf. I do use partitioning software PM8 and BiNG, however I am conscious of where I situate partitions. I was aware of this patch but I have not found any info that using this patch would present no issues on my set up: K8T800Pro board with a Via Chipset (VT8237 southbridge) running a SATA HDD from the on board [sATA] Promise controller in IDE mode. Your clarification in respect of the 137Gb single disk limit will be fine for me (for now at least). Many thanks again for helping me to clear up my confusion Cheers

Many thanks for yor reply Mijzelf. So for clarity, you are saying (and as an example) that I could hook up 4x 200Gb HDD on my motherboard's IDE controllers, partition the 4HDDs to 120Gb as per schematic below and 98SE would have no problem. HDD1 120Gb Primary active partition 98SE HDD2 120Gb Extended Partition (visible) HDD3 120Gb Extended Partition (visible) HDD3 120Gb Extended Partition (visible) So when I boot into HDD1, 98SE will work without any issues and see the 4 other extended partitions. Is this correct? So for clarity, 98SE has problems addressing space above 137Gb on any single disk but can work in the example described above. In this particular example Sandisk and Defrag will also work without issues because the partition sizes are <128Gb. Have I understood this correctly now please? Many thanks Cheers

I just need to be clear on the following please. Native 98SE has 28 bit-LBA support and therefore has issues with any partition (or multiple partitions) greater than 137Gb. Is this correct please? So for total clarity corruption will occur with native / unpatched 98SE if: 1. A system has a single visible partition >137Gb 2. A system has two or more visible partitions (ie primary/active and an extended) >137Gb. 3. A system has two or more visible partitions >137Gb on multiple HDDs. I guess the question I trying to ask is that irrespective of the number of HDDs or visible partitions, 98SE cannot address single or combined partitions >137Gb, irrespective of the partition's location. Many thanks for any info provided Cheers

Many thanks again dencorso. That works for me.