QLA2100 FC HBA - can't boot Windows XP.
This is page 2 of the discussion. Read the opening post
Hardware
This is page 2 of the discussion. Read the opening post
by mirobg
This is not a driver for XP - it just let you change some of the QLA2100/2200/2300 setting to optimize performance/memory use.
Thank you.
by fadbel
I have a possible solution,having browsed through your lengthy responses from others. (You are really a determined person!)
When I installed XP Pro on my system, I initially set up a dual-boot operation and set my second drive (D:) as the XP operation. The C: drive is actually my boot drive (all boot files reside there) and I operate from my XP, D: drive. The installation will still try to access your D: drive during the install/reboot, but it will still be booting from the smaller IDE C: drive. This may work of you haven't tried it yet. All drives are FAT32, but they are all visible from XP NTFS drives if you want to set it up that way. Just thought I'd put in my 2 cents.
Luck, Frank.
by mirobg
It works this way, i already tried, but the performance was so bad i returned to W2K after few days.
Thank you.
by orpheum
hey
i've been thru something similar recently. what i did was hooked up a different hdd (hdd1)into the same server, installed xp, then hooked the problem drive (hdd1)in as a slave and booted on a ghost 2003 floppy. i cloned hdd2 with the successfulxp install from hdd1 and removed hdd1 from the machine. this is the only proven way i have found to overcome hard drive compatibility problems with xp. when i rebooted with the cloned drive (hdd2), xp immediately "found new hdwre" and installed drivers. try this method and i hope you succeed like i did. my crisis kept me up for 2 days. fix the wanker and get some sleep, man. ghost 2003 floppy must be created with pc-dos support. if you're unfamiliar with the process, i'll walk you through it over an im session. if you need the app, i'll get it over to you (wink wink)it's really a matter of just cloning the xp install without actually going through the install process and hardware compatibility screens.
by mirobg
by puntim
I've just read all the way through the various answers and comments, sad eh? Has any one ever got a reply from MSOFT?
Anyway to the point of my reply. No where could I find a statement about which version of XP is in use. I only ask because I hadalmost identical problems with some lowly Adaptec 1200A's using XP SP1 but no trouble using original XP or XP plus SP1!
Just a suggestion and I admire your persistence
Regards
by mirobg
All started with original XP, after that i tried with XP + SP1, someone suggested to streamlined XP SP1 and i did - but the end result is always the same - wont boot. Microsoft say QLA2100 is XP competable - nothing more. I send them 2 times emails about my problem and never got anything back.
Thank you.
by enserng
Having read all the various suggestions, here are some more ideas for you to try...
1. Realize you have sent email(s) to Microsoft with no response.
Is the system in use at an enterprise, or is the system a "personal" one?
The reason for asking is that if the platform is in use at an enterprise--- Ask the Microsoft sales representative for your enterprise about the drive and driver. If you do not work in the IT department of an enterprise, find someone who does and ask that they ask the sales representative about the issue. Have found that the sales representatives like to keep receiving their percentage and most are interested in keeping paying customers (the bigger the better) happy.
2. Check the scheduling of any Microsoft events near your location and speak to the Microsoft "technical" person on hand. If there is one, ask that they follow up with you in person at work or at least via the telephone. Be sure to get their phone number and email address sothat you can call them if they do not call you within a reasonable time frame.
(Continued...)
by mirobg
by enserng
3. You could always call the "fee for service" Microsoft technical support line-- having not checked the Microsoft Windows XP Hardware Compatibility List (HCL) for the specific make and model -- whoever you speak to, keep mentioning that the make and model are listed within the HCL (if the drive make and model are listed without any modifiers i.e. only for storage, not as primary boot, et cetera).
4. Post some messages and get a group together who would be willing to support the production of an XP-enabled driver. Once produced, post numerous messages on shareware, windrivers.com, or other sites that you have the driver and either give away or charge a small fee to other people who want or need the driver. You could always find a developer who would be willing to trade their time for some time of yours, depending upon what you do, their usual rate, et cetera.
If the make and model are on the HCL, you should only need to do such a thing if Microsoft flatly refuses to support the drive. AGAIN, use the phone and call-- send messages to every Microsoft regional and industry-specific manager who's address and, or phone number you can find.)
4. Try contacting a nearby college or technical school's computer scienceor IT related department and ask if any of the instructors or higher-level students would be willing to produce a usable driver as a project or a small fee, work-study credit, et cetera.
Since the company has discontinued direct support, you can either try some of the above or wait and hope the next release fully supports your drive, as suggested by a previous responder.
Hope this helps and best of luck!
Nikk
by enserng
by mirobg
So far i know only for one more person that use FC HBA for workstation - its just too expensive toy to play with - so i dont think i can convince anyone to develop driver.
Sys admins from the computer college i contacted had no idea what im talking about ( FC HBA )and after long explanation they started laughing at me ( !?! ) for trying to use server storage system in workstation - they dont think this is possible despite the fact that i have it, and it works :o)
Thank you.
by enserng
Think the QLogic site says it best, when getting to any information on the two QLA 2100 types, the page says:
Resources for QLA2100 (Retired)
If you have exhausted all avenues - seems you have tried most... (not sure if anyone suggested) you could always plunk down a couple more bucks for a small fc-based drive to boot from. You would then have the fibre speed operating system and storage you desire without simply lagging away from an IDE boot device.
That way, when the next server or workstation versions do not even recognize the existing 2100 drives, you will have a starting point for a new storagew set. :-)
Hope this helps, and good luck.
Nikk
by mirobg
by enserng
Sorry for the misunderstanding, meant you may want to purchase an additional host bus adapter (HBA) and a single drive that you know XP will recognize as a boot device- at least a single drive adapter is cheaper than a dual.
Since you stated that XP does recognize your current HBA, once up and running from the new HBA and drive, you could then use the adapter for storage with the slowest drives you currently have. Not exactly what you want to do, but considering the situation...
Have been there before, that is for sure. Had a hard drive fail on a laptop with no floppy, et cetera. Had the emergency repair information on a CD that connects via a PC/MCIA card, but guess what- the non-manufacturer PC/MCIA card was not recognized by the bios as a possible boot location connector. Ha, so sad. Had to get a newly imaged drive and lost a bunch of work.
According to Qlogic, the 2200 and 2300 series support boot with XP, see the following URL: http://download.qlogic.com/bios/3505/bootsupport.pdf
Be sure to post if you find a better solution.
Hope this helps, and best of luck,
Nikk
by mirobg
by orpheum
by mirobg
by rrv
Connect another normal working harddisk in your computer. install windows XP and make it active partition. add this QA hard disk as slave to it. then do windowsupdate at http://windowsupdate.microsoft.com. you will get your XP driver for your QAhard disk. find that driver from windowsupdate folder in the working XP harddisk or find the driver. copy it in a floppy or CD. remove that hard disk. make this QA hard disk as active partition and master. remove the other hard disk. boot yourcomputer in safe mode. install the driver which you got now. restart. You are there. All the best.
RV
rv_ooty@hotmail.com
by mirobg
When you use Fibre Channel devices, there no such thing as "master" and " slave" - there is ID like with SCSI.
I tried this with IDE drive running XP and QLA only as storage, but Windows update dont have any new drivers for it.
Thank you
by phil.hall
Wow, this is a wacky problem, isn't it?
Ok, try this: Put in the QLA drive and install Win2000 on it, then get a copy of the Windows XP Professional Upgrade CD and upgrade your copy. of 2000 to XP. *Theoretically* this should work as if the driver exists under 2000 and the upgrade isn't able to locate an XP specific driver, it *should* default to the 2000 one.
Worth a try at any rate...
by mirobg
Yes, but unfortunately, it stay only "Theoretically".
I did that, and it was working fine all the way till it was ready for final reboot. I was all excited that i finally did it..and than it crashed..exactly same way as always..error 7B, unknown hardware. I thought i did something wrong with , because it never went that far any other time, but on second run it did exactly the same thing - worked with upgrade from 2000 Pro to XP Pro till the last reboot, and than crashed...
Thank you
by phil.hall
Ok...Plan B...
Reinstall Win2K on the system, then update the controller driver with this one (http://download.qlogic.com/drivers/2222/QLA2100-W2K-v7.05.05-DS.zip), then upgrade to WinXP.
Try that.
by mirobg
Im afraid that was Plan A - i tried with v7.5.5, v7.5.2 and v7.4.4 - dont work.
Thank you
by csmith
If you want to use XP as the OS, it looks like you have two options.
First, get somebody to write the driver.
Economics dictate against this, unless you can find a student/sucker.
Second, setup the boot drive as a stub.
When you replied to question number twenty six, I realized that something had gone wrong.
The boot drive should be as useless as the BIOS once the system is booted. (All BIOS routines are bypassed (handled in OS code) by XP)
When you reported that the system was slowed down by the boot hard drive, I realized that XP was not bypassing the boot drive completely.
Where to start troubleshooting?
The obvious place is in the TEMP directory and in the disk cache.
For the disk cache you may have to use a tool such as Cacheman. (Free download from cnet.com . Cnet is the parent of TechRepublic.)
If the problem persists with read/writes to C: , then the trick of giving the FC as the install directory during the initial installation is next.
(This trick of using D:\Windows as the install directory has been around since at least Win98. Helps, when a slow boot drive resides with a "added in" faster drive, and it can't be changed. Usually a $ consideration.)
IF this solution can be made to work, you have your fonts, and the only cost is a normal speed boot.
I admire your persistance, but you are up against the collusion of Microsoft and the semiconductor industry, to sell more hardware.
Regards, Chris
by mirobg
Hehe, thats right - i am. I paid fair amount of money for this setup and i want to use it, not pay for another one. And, as it looks, im loosing.
When i set up IDE HDD as boot, i moved page file on FC drive and it didnt help much.
Setup could not finish when i tried to boot from c: IDE drive and install XP directly on d: FC drive.
Thank you.
by mallardtooxx
Okay now this is a tricky one so follow the instructions closely.
First, reformat the drive (this will just make you feel better). Then remove the thing, throw it on the ground, stomp on it, hit it with a hammer, burn it with an acetylene torch, fly it from a kite and get it struck by lightning, bury it for three days in the soil of your native home, dig it up and move it around to the front of your driveway and run it over with your car.
Second, remand yourself to Windows 2000 pro until longhorn hits, if there is no driver for it then you know you have an unsupportable device in which case you need to move on from it to the next best thing. since it is retired you will never really get it to be updated.
third, disregard this entire diatrabe You already know all of this. Sadly it is a life lesson, you will have to upgrade if you want to use XP. I once paid $174 for 4 megs of parity ram but I only could get one stick. I think I still have it somewhere, unused and in the package because I got the stick and then the manufacturer went out of business Ironic isn't it?
-duck
by mirobg
by mallardtooxx
Okay now this is a tricky one so follow the instructions closely.
First, reformat the drive (this will just make you feel better). Then remove the thing, throw it on the ground, stomp on it, hit it with a hammer, burn it with an acetylene torch, fly it from a kite and get it struck by lightning, bury it for three days in the soil of your native home, dig it up and move it around to the front of your driveway and run it over with your car.
Second, remand yourself to Windows 2000 pro until longhorn hits, if there is no driver for it then you know you have an unsupportable device in which case you need to move on from it to the next best thing. since it is retired you will never really get it to be updated.
third, disregard this entire diatrabe You already know all of this. Sadly it is a life lesson, you will have to upgrade if you want to use XP. I once paid $174 for 4 megs of parity ram but I only could get one stick. I think I still have it somewhere, unused and in the package because I got the stick and then the manufacturer went out of business Ironic isn't it?
-duck
by mirobg
by amoeba1
O.K., I'll admit it. I'm crazy. Yep, can't help it. Read through all the post and comments, if I wasn't crasy before, I certainly am now. Of all the comments,I failed to see any that suggest updating the Bios on the HBA, if there is an update. Now one of two things will go wrong,
1. No Bios for the HBA
2. It will make mattes worse (no longer work with 2K).
Good luck and hope to see you in the assylum ;{>
Ray
by mirobg
Never found anything about BIOS update. I guess others did not too, thats why no one mention it.
Thank you
by csmith
I looked at this problem more at a later time.
You can not set C: up as a stub.
Phooey!
The other possibility, (and where the heart of the problem is), is to rewrite the boot order of XP.
Yeah! Right! That's worse than writing the driver.
So, no easy solution so far.
Comment:
Paging file? XP can only address 4 Gig of RAM.
On a high powered workstation, we would normally install that much.
Getting rid of paging helps speed and stability, because of the problems in the Windows memory managers.
Not having to worry about paging means one less opportunity for the Memory Manager to get confused.
Regards, Chris
by mirobg
Well, i sure dont have 4GB RAM, just a modest 1GB , so i guess i still need my page file.
And when it try to boot and fail, the page file dont exist yet.
Thank you
by csmith
OOps, sorry. not clear enough.
The comment was a side comment.
The pageing file is not connected the driver problem.
Part of the problem why the Win2K driver can not be recognized early in the WinXP boot is because the module load order is different in WinXP than the load order in Win2K
Another comment:
WinServ2003?
Have you had time to check it out?
I have not. I was at Cebit (Germany) and MS had a large display promoting WS2003.
Unfortunately I was so busy with other commitments there, that I could not take the time to determine what was real, and what was hype.
The uptake rate for WS2003 seems to be much higher among NT users than Win2K users, but we are only one VAR, and it also may be part of the normal software upgrade cycle.
Anyway: It may be worth looking into.
You could have your fonts, and a new OS?
Will it work? Good questions.
Regards, Chris
by mirobg
I didnt, main reason its server, not workstation, but i may at least see if it will work.
Thank you
by csmith
Something else I forgot to mention about Windows Server 2003: Speed.
It appears that Microsoft has seen the IBM ad "They stole all of the servers." about server consolidation.
They appear to have noticed that this is a significant trend.
They also appear to have noticed the growing use of LINUX on servers.
I have heard that they have reacted by actually addressing their bloatware problem, and that WS2003 is better and faster as a result.
So there is hope.
Regards, Chris
by timwalsh
You would think that after a year, if there was an answer available, you would have gotten by now. Of course, since you have rejected all answers, there's now one to award points to anyway.
It's time to close this question.
by ironeagleone
by ryannsit
7b stop errors are also caused by conflicting devices. This is entirely possible with an incorrect driver.
I can't manage to read all of the replies all the way down, but have you considered removing all of your "extra" cards/drives except for the bare necessities?
You could also try disabling sync negotiation in the SCSI Bios.
Just a few random thoughts.
by ryannsit
And by the way.
You're looking to get work done faster.
With all the time you have spent on trying to get it to work, you could have done that work 5 times!
;-)
by schefer
Here's what I would do. I would use a fast scsi drive for the boot drive and put the OS there and nothing else. Then install your apps (photo shop, etc. on the QLA drive. I would also move the swap file over there. When you install software other than the OS make sure you change the install location for c:\.... to whatever drive the QLA is designated as.
Moving the swap file to the faster QLA drive will dramatically reduce the hits on the slower drive and will result in much better performance.
I've noticed that you rejected most of the ideas so I assume that you really want to use this drive as the boot device. I don't see that ever happening but I think you can get the performance you are after with XP if you try my idea.
by mirobg
by jammer1957
The only way I can see you using the fonts in XP is to use your 2000/OS and install Virual PC.
Then install XP with the Virtual PC program and then you get your fonts.
As far as a driver for XP is conecrned, you will never see it unless you write it yourself.
Jammer
by mirobg
Its getting too complicated for my taste :o(
Thank you.
by wlbowers
Try this site. There is a driver and configuration utility. Don't know if you have or can use it.
http://www.cc-solutions.com/drivers.html
Good Luck Lee
by mirobg
Unfortunately, i already had it and it dont work.
Thank you
by phil.hall
Ok, here's a nother one of my patented wacky ideas! ;)
Install Windows XP on a different drive. Then obtain and install VMWare on Win XP. Once you have XP installed with VMWare, install to the new VMWare virtual sytem Windows 2000 and have that version of 2000 access the QLA. That will work...unfortuately it's a really convoluted method of accomplishing your primary goal for accessing the QLA.
Other than this I'm running out of ideas.
by mirobg
Its getting too complicated for my taste :o(
Thank you.
by jammer1957
by mirobg
by syadm
Step 1.
Buy a horseload of lottery tickets and win a big heap of $.
Step 2.
Buy Qlogic.
Step 3.
Make the whole Qlogic team write
"I will never be nasty again" on the parking lot.
Step 4.
Fire all exept those who can write a driver.
Step 5.Make the remaining crew write a new driver in VI-editor (with white background).
Step 6.
Test the driver and when it works, sell Qlogic to the Chinese government as marshall aid.
/Tom
by mirobg
I like this best so far :o)
Thank you
I think you should first make a few admissions - state the facts:
1. There is no driver available anywhere for your particular drive to work with your particular operating system.
2. There will never be a driver available anywhere for your particular drive to work with your particular operating system.
3. You're willing to jump through fiery hoops to get your hands on a driver for your particular drive to work with your particular operating system.
Therefore, if number one and two are true, then you have to rely on number three. We've all heard the old adage about turning a lemon into lemonade, so look for the opportunity here, not the obstacle. This question has been open for well over a year. In that time, you probably could have taken a class (or a couple of classes) to learn how to write your own driver. Yes, it would have cost some $$, but you could have then turned around and profited from your new found knowledge. After all, if there's a need that you have, chances are others have it as well. (Find a need and fill it.) Well, this need has been knocking on your door for a long time.
If you do a search for writing device drivers or writing custom drivers, you'll get a lot of hits which will undoubtedly spark some ideas on how you can figure out for yourself just how to get this thing written. If an investment is required, go ahead and invest in it (invest in yourself), then turn around and sell it to others who have the same need.
Here's a possible start:
"Writing Drivers for Mass Storage Devices"
There ya' go - you get your driver AND you get paid for doing it.
by mirobg
I don't have time to do that, but its a good idea.
Thank you
For everybody who think that i should close this question - i am looking for solution for my problem, and i cant understand what is the problem with this being over a year - i still don't have working solution. I don't care for points or anything else - ill gladly will give all my point to anyone who gave me solution i am looking for. I don't want to install VMware, Virtual PC, another SCSI controller, EIDE harddisk or boot from floppy - is it that hard to understand that?
If you don't have solution im looking for, how do you know somebody else don't have it and he is just about to become member, read my question and give me the solution? I could not findany limit - how long, now many answers etc. If i miss something , please let me know.
Hey mirobg,
In reference to your comments in my answer (number 78, I think), you're right. Keep this thing open as long as you need to. And you're correct in thinking a new member might see it and come up with a solution. Be advised, however, if it goes too long without any activity it may auto-close, so you may want to bump up the points or add some comments or something from time to time to keep it going.
Good luck. I hope you find something that works But it's way beyond my limited knowledge and ability.
by mirobg
by dadavis5th
You may have better luck doing the following.
1. Create a NT bootable disk with NT drivers for your controller.
2. Format the drive FAT32
3. Install XP, hit F6 and use the NT not the 2000 driver for the adapter. Also select to use existing partition format (FAT32).
Sometimes NTFS can be quirky and this may help.
If that does not work use a 3rd party util to format and create a floppy boot disk or create a dual boot with XP being the second partition and NT the first.
Alston Davis
by mirobg
Tried all this - no luck :(
Thank you
by aaelwyn
I am not sure if this will help but i had a similar problem trying to install a Maxtor (don't say it :) Diamondmax Plus 9 120gig 7200 2mb 8.5ms ATA133 Quiet! under WinXP during installation.
During the installation, WinXP would find the drive, partition and format and then freeze as the format finished exactly one hour later. i had the drive replaced with the same result.
After the freeze, i owuld reboot and the setup somehow would continue on this incomplete format of the drive but then konk out at the point where files start being copied with the same 7B error.
I think it had something to do with the size of the drive, anyway, i fixed the problem by booting winxp up on a 20gig, slaving the 120 and running Partition Magic 8.0 (as nothing else even DOS would format it) to finally place an NTSF formatted partition on the drive. After running the install again, it worked :/
by aaelwyn
I am not sure if this will help but i had a similar problem trying to install a Maxtor (don't say it :) Diamondmax Plus 9 120gig 7200 2mb 8.5ms ATA133 Quiet! under WinXP during installation.
During the installation, WinXP would find the drive, partition and format and then freeze as the format finished exactly one hour later. i had the drive replaced with the same result.
After the freeze, i owuld reboot and the setup somehow would continue on this incomplete format of the drive but then konk out at the point where files start being copied with the same 7B error.
I think it had something to do with the size of the drive, anyway, i fixed the problem by booting winxp up on a 20gig, slaving the 120 and running Partition Magic 8.0 (as nothing else even DOS would format it) to finally place an NTSF formatted partition on the drive. After running the install again, it worked :/
by mirobg
It is not the size of the drive that is the problem - i tried with 9.1 GB and 36.4 GB, Seagate and Fujitsu, never had problem with format, but still always end with 7B error.
Thank you
by netguru
by cartoon
I don't know if this will work. I'm no tech man but it might help. If it won't work when you flash your bios, try the partition software that comes with linux. Don't like xp any way.
carterbe@optusnet.com.au
by driv
Well you almost tried everything...
1st: Have you tried Adaptecs Windows ASPI Package Support? Their driver will replace XP's and then you may not experience the incompat issue.
http://www.adaptec.com/worldwide/support/suppdetail.html?sess=no&language=English+US&cat=%2fProduct%2fASPI-4.70&prodkey=ASPI-4.70
2nd: I personally agree with Answer 83 and would use Win2003 (if you have it)
Good Luck.
by adambolter
by udovik
What type motherboard in your PC?
Try SUPERMICRO or AOpen.
Some problem i had with XP and hardware.
by p. dickason, cne, mcse, cca
by jmills00
I would try submitting the information to windows support and see if they have a signed drive that will work on it because they may have a drive that has been signed for something else that may work. If that doesnt work then i would go thru and check the HCL and get something that does because down time cost money.
joel
by old tech guy
When I tried to use a huge drive I had the same problem with W2K. I got an IDE card from Promise that had to booted BEFORE my OS. That got around the whole OS recognization problem. The card is
Win2000 Promise Ultra100 TX2 (tm) IDE Controller
The additional benfit was that I could hook another three drives to the card and I was using a faster bus speed to connect them to the Mother board since the built in IDE ports were actually slower than the PCI bus on this computer.
You also want to make sure that your BIOS is updated on the system (both the cards BIOS and the PCs hardware) because 10K and 1G sounds pretty new--and fast!
Good luck!
by old tech guy
by mirobg
by mirobg
This discussion is closed to new replies.
Sort by Trending