Jump to content

GoogelchenTheGreat

Member
  • Posts

    14
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

About GoogelchenTheGreat

Contact Methods

  • AIM
    MarcusAurelius84
  • Website URL
    http://
  • ICQ
    17767031

GoogelchenTheGreat's Achievements

0

Reputation

  1. now that i used repair console to overwrite both files, i get the same message and error code, only that user32.dll and KERNEL32.DLL are now involved. And hey, that is where the fun begings. Where by any chance can I download linux isos?
  2. Hi Guys ... I recently reinstalled my Windows XP - installation went fine, XP2 Install, too. Since I am, as my american fiends call me, a german vermin, I of course use Windows XP Pro German. I have installed the lates update pack from Winboard.org; dont know whether you are familiar with it. Anyway ... after installing it and restarting my PC, it gives me a nice, dirty little bluescreen. Never seen anything like it before. Since it is in German, I'll try to translate as good as I can ;-) "STOP: c0000269 {Illegaly moved a System-DLL} The system-dll "user32.dll" has been moved in memory. The Task kann not be completed properly. The file was moved because, "C:\Windows\system32\ntdll.dll" is using an adress area that is reserved for Windows-System-DLLs." And then something weird after the dot "Besor %S %S" Does anyone of you have a clue, what this may have been caused by? Know that it must be something out of the update pack ... Will, of course, reinstall - but: I dont know which update caused the problem. With 45 Updates being in the update pack, I dont really feel (you may understand) like trying each after another. Any ideas, suggestions? Id be thankful - Googelchen
  3. down nto the ring of fire ... for almost a day now ... hope the scriptkiddies didnt make it fall :-(
  4. As far as I'm informed, better not, otherwise you may go apply the driver packs one more annoying time *grins*. See, NLite changes a lot of inf-files significantly, so you may not want to mess with nLite after applyig the drvpcks.
  5. Here is the newest Version of the hpt3xx dirvers 2.351 I have edited your slipstreamer along your suggestion and, with the newest driver, it works. It is hower important, to have the newest bios version at hand and applied, otherwise you may get some problems since the bios version is not backwards compatible with older drivers :-( If anyone needs the newest bios version for ABIT KT7A-Raid, just drop a line, I could send it to you, taking no responsibility as to how you apply it or if u fry your motherboard *lol* Hope that is a slight help to you :-) Googelchen ps: attaching the zip does not work, contact me if u still need it
  6. Sry - didnt read that ... Of course it is referenced to a hpt3xx. That is because I reinstalled the real driver so that Windows would work faster. --> The driver installed by DPMStorage I don't have installed anymore. But anyway - the hwids are the correct ids for HPT3XX :-) Goog.
  7. Hi Bashrat :-) Just wondered, whether you have already done something about the hpt3xx and ahpt/rhpt problem that we reported earlier? Didn't hear back from you for a while, so I wondered if I could help you any further and if the hwids I posted were helpful for you? All my regards & thanks Goggelchen :-P
  8. Hi - I am German and use WinXP German ;-) Since I seemed to have used an english version of the updates provided to slipstream them into WinXP with NLite, most of my Windows is now in english. That is not a problem, the mix of both languages, english and german, is annoying ;-) Since I dont want to reinstall - is there a possibility, to use some kind of language pack? Where would I find such a thing, if it exists (google wasnt helpful) Thanks for help ;-)
  9. Voting with my wallet won't be a good choice at this time *grin* - the ABIT KT7A-Raid was big in 2001. I still use it and I still think it is a good choice. The reason why I wanted to use the driver packs: **** **** **** - my floppy drive is broken and I can't install the drivers in any other way. Whooohooopsey ;-) You see ... I was desperate *lol* Googelchen
  10. In fact, he has - but there was no real answer to the problem. Why, I don't know. :-) :-P
  11. Ah well. Respectfully speaking, I can understand scp2 quite well though I may disagree with a few nuances of his post, I could generally sign it. I also think he has written that post regarding our "trouble shoot session" which quickly got out of hand, timewise and effortwise. Until we found the error together, it was a long road to go. See, we have discussed the matter on the phone, and I have to agree to his point looking forward to a stable release. The logic chain of thoughts being the following: I use driver pack to adore your work - I save time - it works like a charm - I am happy with it. Wonderful - that is, I assume, your intention by creating this driver pack. Now, if there is an error that seemed to be known to you (sticky thread of scp2 refering to ahpt drivers) and you did not solve it: I get bluescreens - I use even more time to get it to work - I get frustrated :-D - I die *lol* The purpose of the driver packs - at that point, is obsolete. This - and I really mean that - is the point that bothers me. You may, of course, add as many drivers, as you want, but I think if there is not the newest, BUT a working driver, this makes ppl happier than (in my example) bluescreens at GUI Boot of Windows. So much to explaining scp2 - I hope that you understood it okay, it is not to be understood along the lines of being biatchy or unthankful, it is more along the lines of - here is something that I as a user would much rather prefere over the other. Okay? :-) Regarding my help with the hpt3xx problem, I am, as I promised, up for any support that you ask me ...
  12. Hi Bashrat - it is on Abit KT7A-Raid. I think User scp2 had described the problem earlier but it apears that you have not found a solution for it? (I'm refering to the sticky thread open at the top of MassStorageDrivers regarding hpt3xx) He had the same problem on the same board that I use. With the newest driver packs it uses "rhpt"-drivers in textmode as I described. Those are giving me bluescreens as I had stated earlier. When I used the older MasStrgDriverPack, whose version number I have referenced earlier, I think, this error does not occur but: I have the same problems about hibernation, scp2 described. That, after all, is not the big problem. The problem were the bluescreens using the newest driver pack. It took me at least 30 tries to figure all that out since I did not really look at which driver was used (I assumed everything is all right, since the drivers installed automatically with the DrvPack Installer and all worked like a charm) So much for descriptive purposes :-) If you need any more help - I would glad to be there for any open questions!
  13. Okay - here you go! These are the newly installed raid-drivers because I had the same problem as scp2 about hibernation etc. there must be something wrong; now they are installed all right, so I guess the hwids are okay, too! Have fun, looking forward to a reply Thanks! hwids.txt
  14. Hi Bashrat & everyone else! I have recently downloaded your driver packs to use them. Everything went fine with slipstreaming etc - coming right to the point: The hpt3xx.sys is not used for my Raid configuration. I have a highpoint 370 controller which comes along with the ABIT KT7A-RAID motherboard. After having some phone calls with scp2 (his username here) we found a significant problem with the driver pack for mass storage Version: V5.07.1. Everytime I installed with the newest version, it gave me bluescreens when windows wanted to start up for the first time. I could not quite figure it out until I noticed, that the driver used to access the controller is "rhpt"-something. (right in textmode of setup when to enter the partition, its size etc) So I figured there must be some kind of error. Unfortunately this error is so significant that you cant even enjoy the richness of Bashrats work. I would love to use the newest driver packs as well but I had to switch back to an older one, in which the problem does not exist, hpt3xx is used correctly, making it possible to start windows and continue with installation. The driverpack that works okay for me is: DriverPack_MassStorage_V505 - it seems the error introduced itself later on ... Maybe this helps tracking the error? If I can be helpful to find the error I would gladly be willing to help. Just drop a line
×
×
  • Create New...