51

(15 replies, posted in Windows 7 Discussion)

didn't know that UltraISO could do that.  Neat.

I wonder if things like ImgBurn, etc can do that as well.........

52

(15 replies, posted in Windows 7 Discussion)

There are two apps that help with win7 installation from a usb stick.

One is straight from msft, the other is an independent project

http://wudt.codeplex.com/


http://wintoflash.com/home/en/

53

(4 replies, posted in DriverPack Sound)

Here is an 'un-HP-ified' download

http://downloadcenter.intel.com/Detail_ … p;lang=eng

54

(12 replies, posted in Other)

minor nit, to extract Intel drivers to an easily find-able location

intel_driver -a -p <path to extract to>

55

(2 replies, posted in Other)

partition as in a VM or partition as in a 'real' disk partition??

56

(12 replies, posted in DriverPack WLAN)

atheros.cz IS NOT the mfgrs official web site.

uploading a 'fresh' update without prior introduction doesn't inspire a lot of confidence........

The RTM download program ends tomorrow, 20 Aug 09.  Here is the msft link:

http://www.microsoft.com/windows/window … nload.aspx

This is build 7100.  You'll need a Windows Live or Hotmail ID.

59

(9 replies, posted in Windows 7 Discussion)

Yah, got that this afternoon.  I was hung up looking dorectly at the user control panel applet.  That used to work.  I hate it when msft cleans up the gui back doors......

At home I use this option to setup occasional/guest users.  When they aren't here, their uid gets disabled.  Their files/settings/faves are retained until next time.


thanks

60

(9 replies, posted in Windows 7 Discussion)

While a universal ban-your-neighbor button has a certain amount of appeal, I'm looking to create users in Windows Seven but have them be disabled or no-login.  I can do this in XP all day long.  No clue as to how this works in Win7.

61

(9 replies, posted in Windows 7 Discussion)

has anyone found out how to disable individual users?

are you running the VMs on real disk partitions or VHD images?

Back to the matter at hand...

By any chance do you have sata pass-through enabled for your win2k or xp virtual machines?

Set up your system bios (the real system) to whatever is best for Fedora, don't worry about anything related to virtualbox

Get Fedora running as well as you possibly can.  Then lets start kicking win2k and xp into submission as VMs.

whoops, my bad re win2k and xp (and server 2003) drivers.  Serves me right for posting at 2 AM after a hard day of hammering Server 2008 update concepts into noobs heads at work.

Again, sorry 'bout that.

Most BIOS have an IDE compatability setting for their SATA controllers.  Have you tried that?

Driverpacks officially supports XP only.  AFAIK no XP driver will function on Win2k.  There are the beginnings of support for both Vista and Win7 but none for Win2k.

In the runup to Win7 this fall I'm expecting that both XP and Vista will be rapidly abandoned except for hard core enthusiasts.  The immediate effect of this will be the loss of driver support as you are seeing.  Win2k being 3 years older than XP is already in that position.

If you really want to run XP and Win2k on modern hardware, I would encourage you to explore the possibilities of hosting both of those OSs on Fedora under a virtualization product like VirtualBox.  In your case, the immediate benefit of VB is to present a standardized and simplified set of virtual devices and drivers to the hosted operating systems.  Another upside is more precide control of disk space and a vastly simplified boot arrangement.

If you can't stomach Fedora as your primary OS, you can virtualize Win2k and Fedora under XP (and Vista and Win7).  Or under OS/X if you lean that way.

But sorry to say I believe that the days of being able to boot reasonably modern hardware into Win2k are coming to an end.

66

(11 replies, posted in Other)

Guys, it appears as though both of you are having caching problems somewhere along your internet paths.

This is commonly, but not always, caused by mis-configured download managers.

67

(18 replies, posted in News)

w00t!

68

(35 replies, posted in Windows 7 Discussion)

Personally, I would stay away from any leaked release numbered higher than 7229/7231.  Anything above that started off as a virtual hard drive (VHD) which was extracted and heavily screwed with to create an unofficial ISO that is only partially installable.

So if the 'test' release you are working with was ORIGINALLY available from a trusted source as an ISO, go ahead and play if you can verify the hashsums.

But if your play release started out as a VHD, you can be sure that it's been heavily screwed with and by it's nature untrustworthy regadless of who published the download links or hashsums.

69

(6 replies, posted in Windows 7 Discussion)

I just did a clean install of win7 build 7137 to real hardware.  The iso I used (d/l from technet) already had the latest Intel GMA (WDDM 1.1 dx10!) drivers on-board.  I'm assuming that a recent version of ati and nv drivers are there too.

7137 has already been superceeded by three releases.  I have no personal interest in testing builds like 7200, 7201, 7215, etc though.

I'd suggest that no too much work go into a set of Win7 Driverpacks until msft shoves it out the door as a final/gold release.  Things are changing fast and furious with Win7 including driver releases.

"works flawlessly" and "I have no sound" don't belong in the same sentance.

Seems to me that your Vista and XP that are full of crap and have their problems would be working better than the hacked download you don't know how to run.

Fail

71

(2 replies, posted in DriverPack Chipset)

???????

72

(11 replies, posted in Windows 7 Discussion)

Look like msft is updating the driver preload and trimming out more instrumentation.

Let us know if a direct from MSFT download pops up.

I'm very leery of d/l-ing anything that may have passed through Chinese or Russian hands before it hits a torrent.  No offense, but one needs to be aware of where the majority of threats originate.

73

(1 replies, posted in DriverPack Mass Storage)

Those are old drivers.  The current level is 8.8.0.1009 I believe

Well, the names of the 10 core packs are stable so anything that isn't a core pack is by definition a 3pp.

75

(1 replies, posted in DriverPack Chipset)

Have you checked the HP web site for your laptop?

This site doesn't distribute individual drivers.  The contributors here package up similar drivers so that they can be used to create fully updated XP boot disks.

Are you technically able to do this work (slipstreaming) on your own and do you own a valid XP license and do you have valid (ORIGINAL Microsoft ONLY) XP install media?