Search options (Page 126 of 213)

not enough memory to load ntfs is an error generated by trying to load too many drivers at one time...

if you enable a driver for win2k then you must disable at least one other...

(useing the mass storage INI setting disable if OS = )

either Jake missed adding the tag... or you enabled one that was disabled

I stickied this so i will remember to do it...

thanks for reporting everyone... i can't fix it unless i know its broke...

Reporting is so very important!

Have a great day!

OK...

I have found the issue with the backup mechanisim for removing the \D\ folder

the line entered into the runonce key was

cmd.exe /c "if exist C:\D  then rd /s /q C:\D"

"Then" is a valid Autoit syntax - but is not valid for CMD

this is corrected in the 'head' version and will be included in the next release...

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

Duplicate post closed.

this problem has already been reported by the testing team...

Use the official release...

its always nice to get feedback... thanks

good points Level

you forgot to mention that a winnt.sif on a floppy takes precedece over the one on the CD/DVD.

so the simple way to have both is to have a winnt.sif or txtsetup.sif on a floppy that does not contain the [Unattended] section.

put the floppy in for attended
don't use it for full unattended

this is belived to also work for usb flash drive but this is unconfirmed...

SI 3xxx series were fubar for an entire year...
SI 3112 for example conflicted with its own RAID and AHCI versions...

the list does not stop with these examples they are just a small cross section off the tops of our heads...

They will be released when they are stable...

We DO NOT want people useing unstable packs in production.
What good is an updated driver if it crashes your machines...
Go with the older drivers that work... that is why we released them, they are stable
We are not about being current if the current drivers are BUGGED... and they are
when the providers get thier sh*t together then we will release them, and not before.

If you ahve an issue with a particular driver then report it...
since you have reported no bugs i can asume they are fine as is.
(having an older version number is not a bug - it's smart - because we don't cause problems for our users.)
we have doezens of people reporting bugs everyday with the test packs... we dont release bugged drivers and we never will.

if you are sad because we dont have any finals then complain to the providers (Please)
If they put out junk that is up to them but we won't pass those on in our packs...

what good is it to have the latest driver if it kills your (or someone elses) machine?
We are not about bragging rights (my driver is newer than your driver)

do you flash your bios on your PC just because they ahve a new version - if you do you're a bonehead
the only reason to do either of these things (new driver or new BIOS) is if You Are Actually Haveing an issue that the new driver fixes.
(please refer to the fact that you have not reported any issues - and therefore don't have any - and therefore an update is not required)

they will be made available to you when they are stable...
I, like you, also hope that will be very soon - but it wont happen until it's reliable.

That is in your best interest... and is why we have the following we have... we are reliable.

Be 'Cool' and don't use betas in production

It is not possable to avoid a drive letter search after the initial reboot (in your case)
because the way your drive letters change we also can't do something simple like searching z~a instead of a~z
(which is the simple and obvious choice) because sometimes your ODD is first and sometimes it is last...

you can not perform a drive letter search because your bios will not allow us to correct for your issue.
- disabling the card readers is (should be) a bios function-
initialy assigning them in the same order as the OS will after the install may not be possable

not being able to disable is a BUG in the BIOS of the laptop and as such needs to be corrected by them...
they may even have a work around they recommend
- certainly they have to preload them at the factory
  How do they do it??? 
Perhaps you can talk to someone in the config shop.

options

BIOS Fix from OEM

Insider secret from OEM config shop

Copy all files to laptop HDD during textmode
$OEM$\$1\  is copied to %SystemRoot% at textmode
Hint M1 uses $OEM$\$1\ folder...
useing this method your files will always be at %SystemRoot% and no drive letter search is needed at all...

put a disk in the readers!!!

There is a way to specificaly assign drive letters during the install but i do not remember the details...
It was somewhat complex.
It was somthing like - seeding a file that is normaly created during the install. that file containing a cache of the currently assigned drive letters. (hack the OS)

I dont know how much you make an hour but a new laptop that works is starting to look cheap LOL

it has nothing to do with the packs - Your I386 folder is corrupted
the OS File system is corrupted - not DriverPacks

you have orphaned entries in your dosnet and txtsetup files and probably a few more i can only guess at

I make a copy of my source just before i add DriverPacks... then if i want to make changes i make a new copy of the before DriverPacks folder. and i modify that copy then add DriverPacks. you could use the DriverPacks BASE to remove DriverPacks by selecting no packs to slipstream. I wouldn't - I would do as i indicated make a new copy of my pre DriverPacks folder.

so AGAIN you dont have a DriverPacks issue - you have a corrupted I386 folder (corrupted source)

you need to copy the files off a Install CD and re add all your updates and patches and nLite whatever
This is your "clean" source...
then copy that clean source folder -
and add DriverPacks to the copy.

if you need to do updates or whatever make another copy of your "clean" source.
if you ONLY need to update DriverPacks then you can reuse the previous DriverPacks folder.
if you need to change anything else except DriverPacks then you need to use a fresh copy of the Clean source...
or use DriverPacks BASE to remove DriverPacks
- note: YOU CAN'T REMOVE DriverPacks FROM A CORRUPTED SOURCE
- You also cannot successfully remove DriverPacks if your I386 folder is modified after DriverPacks is installed
   (because this will orphan any added files or servicepacks or any other changes
    when DriverPacks BASE restores the backup files it created before you made the changes,
    and once they are orphaned you have garbage.
    and if the backups DriverPacks creates are not found the files will get orphaned and this also destroys your copy)

you need to START OVER from Scratch - and don't modify a source after you add DriverPacks - or you will be starting over again!

from your log above

2008-11-01 07:50:01 : <PREP> Neither txtsetup.org or dosnet.org was found. The removal of
2008-11-01 07:50:01 : <PREP> any Service Packs we may have added with Driverpacks was skipped

Both of these files would be created when M2 was installed
so since m2 was installed
(your log     2008-11-01 07:50:02 : <PREP> Replaced original setup: method 2 was used previously.)
and these files were not found you now have junk...

you can't modify the files after DriverPacks (except to update DriverPacks) if you do, you willcorrupt your source (and you did).

Your log does not lie - i am not going to debate this with you...

i have given you the answer

Your source is Corrupted, Junk, Toast, fried, spent, gone, done, history...

Start over. i can't make it any clearer than that...

a long overdue upgrade... Welcome to the testing team sir!

DPs_BASE.log and HWID's ?