Search options (Page 7 of 14)

And the Troll has resurfaced! With your type it's not good enough to leave well enough alone. You linked to a warez/ptp site. That's not allowed. You could have just stated what you said in the quoted text and would not have been in violation of the rules of the forum.

In regards to the legality of the Driverpacks, as far as I know there hasn't been even one cease and desist letter to pull one driver from the packs. If there was we would certainly comply. We aren't really doing anything differently than driverguide.com, drivershq.com, pcdrivers.com, etc. We are packaging the files, editing a couple lines in the INF to clean them up because of bad coding and hosting the driver itself. We aren't modifying the actual drivers sys/dll/cab code at all which would certainly be illegal.

Hi Doody,

Honestly the easiest way to do it is described here...
http://forum.driverpacks.net/viewtopic. … 585#p29585

You need to contact Acronis in order to add drivers to your Acronis boot disk. We don't have a way to do it. IF you have an account you can contact them through it. If not then I suggest you buy a copy.

This is what teamwork is about! I'll try and test it out at some point.

Galapo, could you add an option to mount a VMWare image and use that for the target?

Ian, you can change one number in the reg binary of the msoobe registry key and call the msoobe activation and it will ask for a new number.

http://support.microsoft.com/kb/328874

With sysprep.exe you can use -mini -reseal for re-entering the activation key.

You've certainly got your skirt in a bunch huh? Talk about a grammar Nazi, geez. I can cherry pick your incorrect grammar and sentencing structure as well. You're just arguing and it's not helpful.

Though, I'm fairly positive that my 10 years of professional/business computing experience (and many more non-professional years), and continued experience, gives me warrant to make substantiated claims about certain things regarding the operating systems we have used, currently use and will acquire.

The point I was making was and is from a business stand point, and perhaps, therein lies the problem. Microsoft will be end life cycle on Windows XP, at least 32bit, soon. We don't use or support 64 bit in our environments and I have not seen a need to deploy it. Perhaps I was too general in saying 'XP was going away'. A mute point, but I never said that XP 64bit was itself going away soon. But when one goes the other is usually short to follow.

We can also all just keep plugging along on Windows 2000 or 98, too! And why not? If you don't see a need to upgrade then don't. But the world around you will. And as unfortunate as that is, that's the way it is.

To quote, "There is no need to upgrade AT ALL. XP x64 will be running JUST FINE for years on end, and I see no reason to stop using it if it's THE BEST O.S. on the market right now." Seriously, really, honestly, more and more software will come out that will abandon support for OS's past. Years to come you will have a piece of software you will want or have to use that will need some newer OS. It's quite obvious to me that you fit into one of these roles: you haven't been in the IT business at all or a very short time or your a regular consumer or kid trying to make a 'point' or some computer science major who thinks he knows how the world works.

By the way, I never claimed to hate XP 32 or 64 bit. In fact I love XP in all forms. Nor do I feel it particularly necessary to upgrade to Windows 7 or Vista. But, Windows 7 is hardly untested and bloated. And it will/should be out by end of year. Microsoft cannot afford to make the same mistake twice. The MS behemoth will die and people will continue to use XP 64bit "for years on end", "bloated" Vista and never upgrade, forever.

Honestly, you still sound like a troll, arguing over silly things that'll obviously get the goat of many here. Still, what are you going to to about helping with getting 64bit drivers for XP? Donate all your time and money? And this was one of the other points I was making. The majority of users are with 32bit XP right now and we only have so much voluntary, unpaid staff. So instead of fighting over it, help.

And stop making up fake statistics it's really "dumb".

Meow, your just going to have to accept at some point that XP is going away, like 2000, 98, 95, 3.1 before it. Windows 7 will be the cats meow, pun intended. It's Vista, but better. Vista is to W7 like ME was to XP.

Yes, Driverpacks currently supports XP. But now driverpacks are starting to support Vista too, eventually Windows7. I don't see the justification of adding 64bit for a smaller base of users than the those using OSX.

I digress, I think that more people would use XP 64bit if the drivers/software was more readily available. I just don't see us having the unpaid, voluntary, manpower to accomplish the task of also doing a set of 64bit drivers.

Stop getting all pissy about it and DO something about it Meow. I can google search a whole bunch of XP 64bit websites too! So why don't you start working on drivers for mass storage 64bit. Because as of right now all you sound like is a troll.

So, now, basically we run OSP on a live system, turn the machine off, capture the image, then deploy the image, turn the newly deploy workstation on?

What about some help

http://support.microsoft.com/kb/q176695/
http://freenet-homepage.de/gborn/WSHBaz … itWin3.htm
http://www.astahost.com/info.php/Window … t4290.html
http://www.codeproject.com/KB/dialog/Ra … ticle.aspx
http://www.vbaccelerator.com/home/vb/ti … rticle.asp

What about WMIC (WMI Console)

WMIC OS Where Primary=TRUE Call Reboot

or with Devcon.exe (non-distributable)

devcon reboot

WSH VBS

Set OpSysSet = GetObject("winmgmts:{(Shutdown)}//./root/cimv2").ExecQuery("select * from Win32_OperatingSystem where Primary=true")
for each OpSys in OpSysSet
 OpSys.Reboot()
next

Found here http://www.robvanderwoude.com/shutdown.php with other examples

Good find bud! That might actually work nicely. I wonder if we could instead load it into an SDI and boot the cd without even having to setup another partition?

Described here using RDPath - http://technet.microsoft.com/en-us/sysi … 63892.aspx
and
http://msdn.microsoft.com/en-us/library … ed.5).aspx
http://www.msfn.org/board/index.php?showtopic=118332

So perhaps the option is to on the next boot have the system load BartsPE (as small of a load as possible) from the drive itself, have Galapo's utility run automatically (set HAL and mass storage) and reboot the machine?

OT: Or do something with WIM and RIS

http://technet.microsoft.com/en-us/libr … 22358.aspx

Sounds good I'll check them out. Thanks!

Hi Doody,

My program is called FindHWIDS. However, I do not use regular expression to find the HWIDS. Mainly because of how the INF files are created and the ability to filter what your looking for.

You might find RogueSpears tool helpful in the regular expression area, which IS called ListHWIDS.vbs, located here http://forum.driverpacks.net/viewtopic.php?id=3148 . He hasn't updated it in a while and it's essentially broken.

Though, I don't know if I feel comfortable giving my code away to a non-regular. What are you looking to use the code for?

Also, for anyone interested, I'm going to be adding code to check for HWID strings that might have a continuance of hwids using the backslash symbol inline. Documentation says that it'd be a backslash and line feed (@LF), the next line will be a comma then one (or more seperated by comma's) hwids.