STOP 0x00000024, 0X0000024, 0X24, NTFS_FILE_SYS Error Code. Applies to: Windows XP and other operating systems. This stop error means that your ntfs file system is corrupt (damage in the file system, bad hard drive data, corrupt SCSI or IDE drivers or a corrupt ntfs.sys file).

Try a different PC just to test (not a VM). Try a new source for your build. Try Easy2Boot with UBCD4win on a thumb drive if your  machine boots to USB.

you failed to comply with rule #1 so I lack the info to provide full support.  For example. did you do your PE builds with XP or 2k3? what Service Pack level? What are the HWIDS of the target system?  my favorite analogy here is - you might as well ask me why your car doesn't start, my guess would be just as good. I don't even know if you have a car at this point. Then you asked what we needed, we already told you this, when you signed up you checked the box and agreed that you read rule one, results are always better when we read the directions

I would try a newer PE build, based on nt6. Glad to help with this 10 year old software but... the newer stuff is better.

2

(1 replies, posted in Windows 10 Discussion)

SamLab still is doing packs.

The need is not what it was in the NT5 era. dealing with drivers is seamless and simple with DISM.

Great to see you around again!

Jeff

3

(2 replies, posted in DriverPack LAN)

DriverPacks.net has never supported x64 drivers for NT5 platforms.

So... don't know where to find them. 

Some of the included drivers may or may not support x64, if they do it's unintentional and not supported.

x64 in XP was not well implemented, or supported, by MS or the community at large.

Best of luck

the DriverPack-17-Online_395285083.1492980021.exe is not created by us. released by us, or supported by us.

If you need our support you MUST be using one of our official releases offered here
http://driverpacks.net/downloads

Please ask for help from whomever you received the file from.

Thank you.

really?

nice big_smile

why is the "component" code duplicated?

edit NM x86 and x64  ... duh

If enough people ask... maybe.. probably not. have you contacted them about it?

Really nice pickup frankyer!

you might have gone on to explain that the f7 key will disable the ACPI HAL and, in THEORY, load the standard HAL.

I personally have not tried this with BARTPE and am curious if it works @BartPE.

@ heypilee More info here https://support.microsoft.com/en-us/hel … windows-xp

Techdud added a newer version of 7zin to BASE 10 and unofficially beta released it. (he just substituted the new version).

It's around here somewhere, however Techdud has been MIA for a year or more.

No new "official releases"

Jeff

10

(5 replies, posted in Windows 10 Discussion)

Please start a thread and include good details

11

(4 replies, posted in Hardware)

I assume that we are talking about a USB keyboard and mouse?

I assume that you have not done a cold reboot. (full power off of PSU).

Did you try BIOS factory settings reset? (update?)

Some MBs allow charging of devices when the CPU is technically off. this would create a situation where USB KB and Mouse do not reset with the system. (Bios setting)

Long time no see, Welcome Back!

Happy Holidays Damnation!

Jeff

I will have to test it to see... Sounds like an error in the massStorage.ini file... I may not have time until first of the year.

TY for reporting your issue

Happy holidays!

Yes

14

(1 replies, posted in Hardware)

I don't know why you want an active hub (a switch) vs a passive hub.  Knowing that would help us to help you.
"serious problems" is rather vague...
there are print server devices already... Print server devices on google

those are basically smart USB hubs... does that help?

http://forum.driverpacks.net/viewtopic.php?id=4422

This is a FAQ

You can NOT write the image file to the drive that you are imaging...

they call that cyclic redundancy, they call that cyclic redundancy, they call that cyclic redundancy, they call that cyclic redundancy.

big_smile

oh my... downloading

Very helpful botus...

Thank you

Jeff

frankyer,

Dibya is very active with several other projects... He is helping us because it compliments his other work. Please be patient with him and us. We all want the same thing! Since we are all donating our time it is especially important to seem grateful rather than needy. Think this way, How can I help, rather than, why isn't  my free stuff done yet?


TY

Excellent post Botus,

Added code tags for you...

Hmmm, might be a need for script to run an installer. In XP we do this with the DriverPacks Finisher. As far as I know it has not been needed with NT6.  They have taken most of the work out of adding drivers these days.  Try downloading the latest driver from the AMD website << AMD 64 bit reference drivers for example Radeon Software Crimson Edition Beta looks good? >> and install them on a clean installation. Does that work?  (is this a 64 bit machine?)

21

(6 replies, posted in Hardware)

Nice... Thanks for following up!

Jeff

Duly noted. Have a great day.

You are welcome sir!

But I will be doing that a lot more as you dive in. Just ask anything if you are not sure or stuck.

99% of the time, the only stupid question is the one not asked.

NP I have trained the best. It's tricky to get it right because it doesn't work the way you would think it would. Once you get it down then it is not so bad. Replacement drivers are always the ones every one screws up, and boy does it cause issues.

the starter course is here... http://forum.driverpacks.net/viewtopic.php?id=2461

this is helpful too... http://forum.driverpacks.net/viewtopic.php?id=445

there is more when we get there... I can always bat cleanup on a nightly (test pack) if you think you have it ready. big_smile I am a busy boy but if you can get 90% of the way there i can tackle the last 10.

Jeff

PS Mass storage is the hardest pack by far... if you can do Mass then it's all down hill from there big_smile

You are correct. It fails because the ISO is not mounted ofter the reboot. So files are not found.

Try adding the OEM folder to the root of your thumb and see if that makes it all flow nicely.
Or copy the OEM folder to C:\
- it will need to be deleted later

Welcome to DriverPacks.net