| Page 10 of 49 |
|
|
 Posted: Tue, 14th Nov 2006 23:33 Post subject: |
|
 |
| Tutukun wrote: | | so can anyone show me some screenshots of teh 3D desktop they've talking about? Not some screenshots from google, but screenshots from your PC |
Trust me, it's nothing special.
"3D" is such an exaggeration, it's sad.
You basically see a bunch of representations of your apps tilted on a 3D-plane.
And that's it.
|
|
| Back to top |
|
|
|
|
|
| Back to top |
|
|
|
|
|
| Back to top |
|
|
LeoNatan
Banned
Posts: 73193
Location: Ramat Gan, Israel 🇮🇱
|
| Posted: Wed, 15th Nov 2006 00:13 Post subject: |
|
|
| dominae wrote: | I don't care about what you -think-, the reality is that the VISTA install fubars the drive-lettering if you install it outside of eg. a present XP-installation (such as booting from the CD, and hoping it will work).
I installed VISTA again from within XP, and it kept the drive-lettering.
No amount of talking you do will make what I experienced first-hand not reality.
"Oh, I ate a sandwich today."
-NO IT'S NOT POSSIBLE! I AM A SANDWICH-PROFESSIONAL! YOU CAN'T EAT SANDWICHES TODAY!!11one! |
Seeing as you are the only idiot getting this, and the level of your conversation, I now know how it was possible.  You are just a moron that doesn't even know how to install Windows. |
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Nov 2006 00:20 Post subject: |
|
|
| lnatan25 wrote: |
Seeing as you are the only idiot getting this, and the level of your conversation, I now know how it was possible. You are just a moron that doesn't even know how to install Windows. |
The level of my conversation, is because you're a stubborn fool who can't realize fact.
FACT is that devices have labels, TRUTH is, yes, you can change these in windows. But they will retain an order based on data such as which device is Active, and which is not.
For instance, in nearly 90% of the cases the Windows drive will have the letter: C:\ , but not always. And changing it is not always feasible. (eg. the boot device and the root device cannot be changed in Windows after you've installed it, for obvious reasons).
However, there is also a logical order, that is set out of Windows. That can be reconfigured in a tool such as Partition Magic.
This is why when I changed the Active device from the one VISTA set, and changed the order of the drives to what I had prior to installing VISTA, XP started to work again.
Oh, you're wrong. There's plenty of people who have had these issues. One other already in this thread.
I fixed my issues. Using this method, but you can continue to spread desinformation if you want to.
|
|
| Back to top |
|
|
LeoNatan
Banned
Posts: 73193
Location: Ramat Gan, Israel 🇮🇱
|
| Posted: Wed, 15th Nov 2006 00:33 Post subject: |
|
|
The only way to change internal hdd (physical) numbering is to swap the ide/sata cables or if bios supports it (not many do). Each time you install a new Windows from scratch (boot from cd/dvd), it sets the install drive as C:\ with no importance to the physical location of the drive. If you run the install form another Windows installation (upgrade or clean install), it will do its best to preserve the drives lettering for the ease of migration to the new windows (2000, XP or Vista). Even if it doesn't keep the old lettering, it is only for the new installation. Old ones are not modified, because old registry is not modified. This is true for Windows 2000 and XP, and from what I've seen Vista as well.
This is a FACT, known for years, and proved right with years of experience.
B2/5536/RC1/RC2 installers all worked that way. If MS fucked the RTM installer badly, whatever, but it seems highly unlikely.
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Nov 2006 04:12 Post subject: |
|
|
Yes, I am quite aware that you cannot change the physical numbering.
However, there is information written in the allocation tables and MBR of each drive that signifies whether a drive is, for instance Active or not.
But it also affects the labels of drives.
If you are not aware of it, there was something prior to Windows, called DOS. It did not have any registry running it's way to handle device orders, and you still could change the devicenames.
And they are not necessarily tied into the position physically on the hardware. They can be changed, and when this is done - it affects how each hard drive is labeled and functions - outside of Windows.
This debate is tiresome.
Primary data reaffirms it,
you're walking on thin ice. Time to step back?
I also think fisk should be unbanned.
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Nov 2006 11:09 Post subject: |
|
|
You guys talking Software mode, Cable Select, Hardware changes or Subst ?
he he... Never mind...
Wanted to know if there was lots of extra Goodies in Vista ???
Sorta like XP had lots more goodies compared to Win2000...
|
|
| Back to top |
|
|
LeoNatan
Banned
Posts: 73193
Location: Ramat Gan, Israel 🇮🇱
|
| Posted: Wed, 15th Nov 2006 12:15 Post subject: |
|
|
dominae, read, learn and STFU:
| Quote: | Drive naming scheme
Under Microsoft's DOS operating system and its derivatives drives are referred to by identifying letters. Standard practice is to reserve "A" and "B" for floppy drives. On systems with only one floppy drive DOS permitted the use of both letters for one drive, and displayed prompts to swap disks. This allowed for copying from floppy to floppy (this wasn't a very fast method though as it generally ended up asking for disk swaps far more often than really needed) or having a program run from one floppy whilst having its data on another. Hard drives were originally assigned the letters "C" and "D", but as support for more hard drives became available this developed into assigning the primary partitions on each drive (DOS only allowed a single active primary partition per drive even though the partitioning system allowed for more) letters first, then making a second pass over the drives to allocate letters to logical drives in the extended partitions. Letters for CD-ROMs, RAM disks and other things were allocated after the hard drive partitions. This was often done simply in the order the drivers were loaded, although many drivers could be specifically instructed to take a different letter. Network drives were usually given letters much further on in the alphabet by the network driver software so that they were generally out of the way of this system.
Because these letters were used directly by normal applications (unlike the /dev/* names in Unix-like operating systems), the addition of an additional hard drive could be disruptive to applications, which then required reconfiguration or even reinstallation. This was especially true if there were logical drives in an extended partition on the original hard drive and the new hard drive had a primary partition, as it would then cause the logical drives on the first hard drive to change letters. However, even if the new hard drive had only logical drives in an extended partition it would still disrupt the letters of RAM disks and CD-ROM drives. This disruptive system persisted through the 9x versions of Windows but NT adopts a slightly different system. It uses the traditional rules when first installing but after that it tries to preserve the letters of existing drives until you change it. |
Only ASSIGN command could hand drive letters to drives. ASSIGN was used to temporarily assign a drive letter to one of the drives, in case a program could only write to D:\ for example. Now, I know FDISK couldn't hand drive letter, so care to enlighten us? How could one change drive letter in DOS so they would stick after reboot?
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Nov 2006 13:57 Post subject: |
|
|
So the 2099 work around works?
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Nov 2006 14:46 Post subject: |
|
|
| lnatan25 wrote: |
Only ASSIGN command could hand drive letters to drives. ASSIGN was used to temporarily assign a drive letter to one of the drives, in case a program could only write to D:\ for example. Now, I know FDISK couldn't hand drive letter, so care to enlighten us? How could one change drive letter in DOS so they would stick after reboot? |
eg.
PQMagic.
End of Bullshit.
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Nov 2006 16:26 Post subject: |
|
|
did the 2099 trick work? anyone....
and i have seen posts on this MSDN patch thing, that supposedly removes the evalu thing in the right corner. You are supposed to patch the iso file before you burn it (i think...might not have the exact proceedure correctly...only looked at the post once). That is what posted, the MSDN patch removes the evaluation copy.
So, replacing those two files with the moded pkeyt and the other works? and keeps it running.
MS closed the beta program, and no longer issues keys...will the one in the package still work with activation?
I am starting to get confused by all the contradictory info out there.
Do we need to do the 2099 thing first?
As i understand it...patch the dvd file first..burn it, .then boot from dvd....
and do not enter serial number...once in vista..copy the two files in safe mode, and reboot, run the slui (or what ever it is called) and activate?
yes?
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Nov 2006 16:45 Post subject: |
|
|
So the bottom line is, install the BILLGATES-release with RC1 key, and wait for a decent crack to come?
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Nov 2006 16:53 Post subject: |
|
|
| ttboy404 wrote: | did the 2099 trick work? anyone....
and i have seen posts on this MSDN patch thing, that supposedly removes the evalu thing in the right corner. You are supposed to patch the iso file before you burn it (i think...might not have the exact proceedure correctly...only looked at the post once). That is what posted, the MSDN patch removes the evaluation copy.
So, replacing those two files with the moded pkeyt and the other works? and keeps it running.
MS closed the beta program, and no longer issues keys...will the one in the package still work with activation?
I am starting to get confused by all the contradictory info out there.
Do we need to do the 2099 thing first?
As i understand it...patch the dvd file first..burn it, .then boot from dvd....
and do not enter serial number...once in vista..copy the two files in safe mode, and reboot, run the slui (or what ever it is called) and activate?
yes? |
If the 2099 trick works you do not have to activate.
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Nov 2006 17:03 Post subject: |
|
|
Well Vista just closed here and asking for a new key, indeed nothing seems work again, even not overcopying the 2 files, something seems be locked.
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Nov 2006 17:03 Post subject: |
|
|
| ttboy404 wrote: | did the 2099 trick work? anyone....
and i have seen posts on this MSDN patch thing, that supposedly removes the evalu thing in the right corner. You are supposed to patch the iso file before you burn it (i think...might not have the exact proceedure correctly...only looked at the post once). That is what posted, the MSDN patch removes the evaluation copy.
So, replacing those two files with the moded pkeyt and the other works? and keeps it running.
MS closed the beta program, and no longer issues keys...will the one in the package still work with activation?
I am starting to get confused by all the contradictory info out there.
Do we need to do the 2099 thing first?
As i understand it...patch the dvd file first..burn it, .then boot from dvd....
and do not enter serial number...once in vista..copy the two files in safe mode, and reboot, run the slui (or what ever it is called) and activate?
yes? |
As WalkerBoh and heckknow posted
1. If you use BILLGATES release, do the MSDN patch to the ISO and burn it
2. Set 2099 in bios
3. Install BILLGATES or WINBETA release with the key in the NFO (NOT beta/rc1/rc2 keys)
4. Change date to normal in Vista
5. Wait for the proper crack
The MSDN patch doen NOT remove the evalution copy watermark.
What MSDN patch does is replacing some beta files included in the BILLGATES image to MSDN official(?) RTM files.
(WINBETA release doen NOT require the MSDN patch.)
"Vista.RTM.en-US.Evaluation.Copy.Desktop.Watermark.Patch-Roger525" does remove the evaluation copy thing.
Last edited by kkm1206 on Wed, 15th Nov 2006 17:18; edited 1 time in total
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Nov 2006 17:05 Post subject: |
|
|
thank you...
so skip the raven and IND "fixes" for now then..
ty
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Nov 2006 17:15 Post subject: |
|
|
| ttboy404 wrote: | thnx...this is starting to get confusing...
since the the ING and raven cracks look much the exact same...but they are not actualy cracks...but a temp workaround using beta files...
I understand the 2099 thing should kinda out smart the limits...
but do you need to do that with the other stuff? or will 2099 thing prevent the deactivation in 2007 when the beta keys are sched to expire.... |
If 2099 work around works, then you don't need to apply the IND or RaVeN released cracks.
2099 thing just extend the 30day limit until activation to unlimited days
I think it's some kinda bug, and it's gonna be blocked in the future
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Nov 2006 17:31 Post subject: |
|
|
did MS fire off a auto-update to deactivate it maybe?
I am sure they are working on stopping this...
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Nov 2006 17:52 Post subject: |
|
|
| kkm1206 wrote: | | ttboy404 wrote: | thnx...this is starting to get confusing...
since the the ING and raven cracks look much the exact same...but they are not actualy cracks...but a temp workaround using beta files...
I understand the 2099 thing should kinda out smart the limits...
but do you need to do that with the other stuff? or will 2099 thing prevent the deactivation in 2007 when the beta keys are sched to expire.... |
If 2099 work around works, then you don't need to apply the IND or RaVeN released cracks.
2099 thing just extend the 30day limit until activation to unlimited days
I think it's some kinda bug, and it's gonna be blocked in the future |
It's not a bug. Simply windows register the installation date a when you are 30 days over that date it freezes.
|
|
| Back to top |
|
|
segobi
Posts: 1565
Location: FBI Cybercrime div.
|
| Posted: Wed, 15th Nov 2006 17:53 Post subject: |
|
|
| ttboy404 wrote: | did MS fire off a auto-update to deactivate it maybe?
I am sure they are working on stopping this... |
are you sure ? I think they are happy if anyone uses vista right now...companies will wait a long time until they upgrade to vista ... there is no current need to do that...and its expensive...
Most users will be the ones who get a copy of vista with their new pc...in 6-12 month most people will switch to vista..when there is more software for it...and games require dx 10 or so...
|
|
| Back to top |
|
|
|
|
| Posted: Wed, 15th Nov 2006 17:57 Post subject: |
|
|
I just waited a few days since release to even look into the whole hot vista thing..I am still downloading it right now.....it has kinda been confusing....now where near as simple as getting a simple keygen
no I am not sure at all....not at all....
just saw an "official" statement from MS, saying they would deactivate the beta keys...dated on wed (today) on a web post, they stated these new copies would be of "limited" value.
i am currently looking at disabling the WGA thing now as well...and something called Orca.exe. Orca is a msi editor, it seems microsoft has published a program that edits Msi files...and you might be able to remove the validation check..MS has posto on editing the msi files and a way to remove the whole process i think...but it is prob xp tho..and just looking at it now. Orca is part of sdk tools....and is designed for xp and vista...trying to get a hold on it now...just to see what you can do with it...I may not be smart enough to use it, and don't know if it will help the vista thing.
don't know if this will be of any value to the whole vista thing tho.
|
|
| Back to top |
|
|
|
|
|
| Back to top |
|
|
|
|
|
| Back to top |
|
|
|
|
|
| Back to top |
|
|
|
|
|
| Back to top |
|
|
LeoNatan
Banned
Posts: 73193
Location: Ramat Gan, Israel 🇮🇱
|
| Posted: Wed, 15th Nov 2006 19:22 Post subject: |
|
|
Try taking ownership of them in Properties -> Security and then giving yourself a Write permission.
[EDIT]duplicatev, you beat me to it... 
Now about this 2099, does it work if I don't enter a key in the install?
|
|
| Back to top |
|
|
segobi
Posts: 1565
Location: FBI Cybercrime div.
|
|
| Back to top |
|
|
Parallax_
VIP Member
Posts: 6422
Location: Norway
|
| Posted: Wed, 15th Nov 2006 19:23 Post subject: |
|
|
Can you buy me one too, segobi?
|
|
| Back to top |
|
|
segobi
Posts: 1565
Location: FBI Cybercrime div.
|
|
| Back to top |
|
|
| Page 10 of 49 |
All times are GMT + 1 Hour |
