Re: Windows Xp Sp3 Sata Iso
Indira Rossetto
I started out with Windows Home Server. It worked great until it was discontinued. Eventually I migrated to WSE 2012R. It worked fine but keeping in mind my WHS experience I decided to upgrade. I eventually chose WSE 2016 since 2019 did not allow for remote desktops. The initial install to WSE 2012 from WHS went flawlessly. When I did the upgrade to 2016 the system crashed. I have no idea why. It took some time but I found my data, reconfigured it, replaced the expansion card, replaced the Mobo, and now I am adjusting my storage pools. I have added 2 x 4TB sata drive and an 8tb sata drive. The mobo and the OS both see the drives just fine. I configured the Adaptec 7805 raid HBA card to be a HBA passthrough for my drives. Disk management had no problem with the drives. My client PC's using a remote desktop sees the drives properly. It is just that every time I try to add them to a storage pool I get an error message. At first I thought it was the 8tb causing problems but when it is not included in the pool it makes no difference. The 2 x 4tb drives are errored as well. I read somewhere that raid bus drives cannot be added to a storage pool. I can't seem to get rid of the raid bus designation. I did a lot of research before I bought the adaptec card and it should work. Do I have to delete the drives from the Server operating system? Then let the OS find them, hopefully on the sas / HBA bus? What do I do now? I look forward to your help.
Mobo is Asus Server model P5BV-E/SAS with 8 GB of onboard Ram (old but works great otherwise) It has a Xeon x3360 2.85 gigahertz processor
Originally in the 2012 build it had a cheap sata expansion card in a similar board but I believe the system crashed when the add-on board blew a rail. My new power supply is the best available, no issues there.
System works great but I can't seem to increase the storage pool.
I did cheque out the drive due to the age of the Mobo. Asus Saud the card is compatible. As I said the problem lies in WSE 2016. the drives are seen by the OS. I am looking to see if there is something along the lines of deleting the drives from windows, turning off the system rebooting and letting the OS find the drives after the system reboots. I also read in another forum that registry changes can affect bus recognition. I can assure you I did check hardware compatibility. Sadly after I bought a Supermicro card was useless to me as it only works with their motherboard. Lesson learned. Sadly. I truly believe the issue lies in the OS configuring drives and artifacts having left on the system after initially loading the card in raid setting. Now corrected but I can't seem to get rid of raid bus designation. As stand alone drives they all work great. I just lose the redundancy that comes with storage pools. At worst I can use them as drives without back ups.
Deleted the drives in question from disk manager and device manager. Rebooted system. OS allowed me to integrate the drives into the storage pool. No further problems with OS. WSE 2016 works well. All is good. Thanks for your efforts.
MSFN forum pages have all the necessary info on the topic. (Software tools as well.)
On one of my PCs, I was using the Terabyte Plus Package by R. Loew for a while for the same purpose but later, for the sake of simplicity, placed an IDE HDD as primary master and booted 98SEtoME from there.
^ I just use DOS from 98SE with FAT32 partitions since it offers native support for it... I have used a single fat32 partitioned 80GB HDD without any problems whatsoever for several years now... the only "problem" is that most programs will report free space as 2GB only, but that is to be expected since they are not fat32-aware...
New information:
I finished installing Win98 on the IDE drive. Next I wanted to use the SATA (formatted with FAT32) to store all the installers for programs I plan to add. When I connected the SATA drive I encountered a screen telling me something about child devices mixing 32-bit drivers and compatibility drivers, this is unsupported, Windows will now use only compatibility drivers for all child devices. When Win98 rebooted the SATA drive was accessible as D:\, however the optical drive will no longer show up within Windows even after the SATA drive is remove. And I don't know how to switch back to 32-bit drivers. If the same occurred when the SATA drive was being used to boot I understand why it would freeze at screen it did.
The closest that can find is ATA/IDE Configuration.
DISABLED: All IDE resources disabled.
LEGACY: Up to 2 IDE chanels enabled for OS requiring legacy IDE operation.
ENHANCED: All SATA and PATA resources enabled.
I have this set to Enhanced. I don't to see a way to configure SATA separately.
For an individual drive connected through SATA I have options for:
Type [Auto] [User]
LBA/Large Mode [Disabled] [Auto]
Block Mode [Disabled] [Auto]
PIO Mode [Disabled] [0] [1] [2] [3] [4]
DMA Mode [Auto] [SWDMA0] [SWDMA1] [SWDMA1] [MWDMA0] [MWDMA1] [MWDMA2] [UDMA0] [UDMA1] [UDMA1] [UDMA3] [UDMA4] [UDMA5]
S.M.A.R.T. [Auto] [Disabled] [Enabled]
All of them are set to Auto.
Using Acronis Disk Director 10 I created 1 partition that is hidden with 20GB of unallocated space before it. Windows 98 formatted and installed to the unallocated space. I later plan to delete the hidden partition, make a backup partition at the end of the drive, and resize the main partition to fill the remaining space. Having done this many times before with Windows 98 makes me think there is something special about SATA that is causing me to encounter roadblocks now (see new information above). Currently the partition is only 20GB.
...The closest that can find is ATA/IDE Configuration.
DISABLED: All IDE resources disabled.
LEGACY: Up to 2 IDE chanels enabled for OS requiring legacy IDE operation.
ENHANCED: All SATA and PATA resources enabled....
Give the LEGACY option a shot. The manual for one of my older sata motherboards indicates something like this setting for W98se. It constrains the number of channels but allows it to work. However you may be out of luck without an IDE Mode for the sata setup - that setting is the usually the kicker. Track down a PDF for your motherboard if possible.
Switch IDE configuration to "Legacy", you should get an option to swap in the SATA connections as either your primary or secondary IDE controller instead of one of the PATA channels like below. Set it to one of the last two options.
Technical Background: Intel ICH5 boards predate AHCI, so they normally present on the onboard SATA connectors as a 3rd IDE controller, but at a non-standard hardware address (nevermind that there is official IDE assignments for this setup, just not very supported) . Windows 2000/XP has no problem with this as its IDE driver supports non-standard resource assignments. Windows 98's driver only recongizes IDE devices at the traditional hardware addresses (1F0h/IRQ 14 and 170h/IRQ15). The BIOS legacy setting gives you the option to map in the SATA ports as either the primary or secondary IDE channel and disables the PATA channel normally used. You can't use all three channels in Windows 98 as a result.
It does work in DOS however, since the Int 13h routine in the BIOS supports the drive (so you can boot off of it in "Enhanced" mode). Thats why the Windows 98 install worked fine, but it locked up when starting Windows. Control was passed from Int 13h to Windows' protected mode driver and it chocked.
I thought Legacy would disable SATA entirely. What it does is give me another menu item.
Legacy IDE Channels [PATA Pri only] [PATA sec only] [PATA Pri and Sec] [SATA P0/P1 only] [SATA P0/P1, PATA Sec] [SATA P0/P1, PATA Pri]
I'm continuing with SATA P0/P1, PATA Sec. Hopefully this will also take the IDE setting into consideration.
With that option, the SATA connectors become the primary IDE controller, the primary PATA channel on the motherboard will be disabled. Your drives on the secondary PATA channel will continue to work as usual.
I don't want to hijack this thread but since we're on a 'W98se on modern PC' kick - how about pci-e? Getting a pci-e video card running has been the big stumbling block for me: 7800GTX/256mb pci-e in my case. Is your board AGP or pci-e [or both]?
I wouldn't call the Intel D875PBZ modern. It's a Socket 478, Pentium 4. The two SATA connectors on it were a surprise. It's AGP with 5 PCI slots. Still quite an improvement from the board I was using before it.
I'm dueling it out with a similar pci-e setup right now. Yes the motherboard and other hardware are 10-15 years old, but even that's but quite a bit past W98's "serve by" date... On the bright side XP runs absolutely great on this rig so if I don't succeed in my quest for a W98se "monster" I'll have a pretty neat soon-to-be retro XP rig.
After running infinst_enu.exe there were 2 dozen or so New Hardware Found boxes and now the system has been stuck on the Windows is shutting down screen for the past hour. So I'm going to say that wasn't the right driver either.
With all the custom packs and other win9x update projects out there someone needs to fix some the driver issues so that sata and pci-e works out of the box. There are modded versions of xp out there that have native sata drivers (sp3) already included. It is annoying to have a 9x5 series board yet 9x doesn't support pci-e.
Please look on the Dell site for the latest Renesas USB 3.0 drivers. I don't know if this will fix your issue specifically, but I was seeing errors and issues with components not being recognized when plugged into my USB ports. I could see the secondary drive when plugged into a USB port, but not when set up on the secondary sata port, although the uefi (bios) would see it upon initial boot. After trying numerous things to fix it, I tried updating the USB drivers. Note that with my issue, I would see in settings that a USB device was not recognized and deleting the drivers for this, then searching for a new device would cause it to reappear. This only happened after installing the drive. After finding the Renesas driver and installing it, no more USB errors and the drive was visible to windows. I hope this works for you and helps others with similar issues. Dell does not provide the drivers when you look for drivers for your specific laptop. You have to search for it as I mentioned.
d3342ee215