the baker at jury lane

Hi,

Im back and pleased to announce that i am on windows 7!
and it is working perfectly! the whole, delete,format thing worked like a charm.
the Only thing i did differently was:
instead of deleting it,then formatting i just formatted it..
AND VIOLA!

halifax1

That works too, but sometimes that creates a small-sized hidden partition that is not usable for Windows.

Still, it's not a large enough size to matter.

Glad you got it working great and are on Windows 7

WeAreNotAlone

EDIT: After typing up the below- I see you've already installed the RC.

Info below is for reference purposes on what someone should do/consider if they have a machine that has a WARRANTY.


i just bought A new PC and it came pre-loaded with Windows XP and want to replace XP with RC 7100



Repeat after me... New doesn't mean "Good"....

Until the machine is proven "good", if you have a hardware warranty thru the manufacturer I'd keep XP on it... and run a Dual-Boot, Or make arrangements to image the hard drive so unit can be restored to as-shipped condition.

Why? If you do have a "issue" (EG: The hardware is off-spec) tech support will be basing their procedures off the OS installed on the machine....

Translation: Tech support will require you to run their custom xyz app, or do xyz procedure to verify the machine is truly hardware defective BEFORE a RMA can be issued. This generally meaning their app or procedures are tied to the OS the unit shipped with.

(Additionally note from a warranty perspective that you may be given "grief" if you let slip to tech support you're running a OS the unit didn't ship with... Best if you do have a HARDWARE problem to re-image the drive to the OS the unit shipped with if you need to RMA the unit /obtain support! Is this fair? / think about it from their end. )


* * * * * * *

As a rule I'd run the machine in a Dual-Boot Configuration for 30-days, before wiping the pre-installed OS (or the pre-installed recovery partition) off the machine...

After that time I would delete whatever OS, resize partitions as needed.

(I'd image the drive so the unit could be restored if needed for warranty purposes.)


PS Installing a new OS is a good time to partition the hard drive, installing the OS in a seperate partition from your DATA.

Whatever you do create a separate partition for your DATA....


Translation: A fool installs DATA on a OS partition...

Putting your DATA on a OS partition is like having irreplaceable items/ pictures that came /were passed down from your great-great-great-great grandmother/ father in your kitchen (or other place of high fire risk)... and then crying when the kitchen catches fire and everything is destroyed.



.

TwoCables

Damn, and I thought every single one of my replies were enormous and highly-detailed. I guess I have competition now.
w00t! Now that's what I call epic win.

__________________

the baker at jury lane

OMG what the !@#@%$% Did He just SAy??????
Twocable:no one could ever match your amazing novels,and skills to turn 1 line into 50...

Daney

If you built the system yourself, ignore the highlighted stuff.

If you purchased the PC from a shop, ie. Did not build it. He means that if your PC fails, and is still under warranty it will be easier to return and get a repair on if it breaks as it will be "un-touched". However, if you've changed the OS it may void the warranty but I'm unsure of this.

__________________
Steam ID: prodaney
Goal by end of 2010:
50,000 Points | Current: 12,423

WeAreNotAlone

Re-read the post again. Daney below understood...



Correct....


*****


What is all this talk about a new machine not being "good" until it's been run for 30-days...
Hey it's "new" so it's got to be "good".

"I don't understand"

Units can be defective out of the box (DOA), and fail without warning in the early period of ownership.

In all manufactured products there is something that's called:

"The Infant mortality period (IFR)"

As it pertains to electronics- a device in the early ownership / run-time period can die without warning...)

Here's a graph to illustrate:


Infant Mortality Curve - Failure Rate vs. Time




OK, so what should I do?

Upon receipt of a new machine:

Get your head straight, Do NOT assume the machine is "GOOD" (Defect FREE). Assume instead that the machine until it's been run for 30-days and has passed "Stress-Testing", and the "Burn-in" period is not defect free" and the unit could drop dead without warning.

How do you test /certify the machine is "good/defect" free?

1: By running the machine under load @125C for 168 hours... as per MIL-STD-883 "Test Methods and Procedures for Microelectronics"

As most people ( And OEMS's ) cannot do this running the machine under real life loads, and testing with STRESS-TESTING, or BURN-IN APPS is the next best thing.
Machine is only considered good if it has passed the Stress-Testing", and the "Burn-in" period and makes it to 30-days.

Note: You don't run the Burn-In apps for 30-days straight! The point is to "load-down" the machine to push the components to the limit so marginal, or defective components surface during your "return period"... Or early part of the warranty...

I just bought a new machine that has a WARRANTY, or I have a RETURN window in which I can swap the unit out for another, or for another model- And I'd like to delete the OS the unit shipped with- and install another. What should I do if I'm within my return /warranty period?

A: Until the machine is proven (has been run 30-days and has been "Stress-Tested /Burned-in"), you should run a "Dual-Boot" so you can boot to the "As-Shipped OS" in case you have to contact the OEM for tech support. Doing so will allow to to interact with them as needed /run whatever apps they require you to run to "test" the machine.

B: Have in place a plan to restore the unit to * "As-Shipped" condition.. Or at least re-image the as shipped OS in case unit needs service/ needs to be swapped out for another model *

*Some OEM's will require you to restore the machine /and or run their custom apps that proves (to them) the hardware is bad before a RMA /Warranty /Support ticket is issued.)

*Having a way to restore the unit to the as-shipped OS greatly simplifies being able to swap the unit for another.

To this end. do not blow away the FACTORY RESTORE PARTITION... It comes in handy if they require the OS on the machine for testing /service and comes in handy if you're doing a RETURN /SWAP.

Consider also "imaging" the hard-drive... via Acronis True Image.


Where can I find these Stress-Testing, and "Burn-In" apps you're talking about?

GOOGLE is your friend... Here's one link to get you started though:

Burn-in, Benchmarking, Stress-Testing Apps:


Burn In/Stability
Prime95
Orthos
SuperPi Modded version (multi core support)
Memtest86
OCCT

http://mybroadband.co.za/vb/showthread.php?t=95177




*****


SUPPORTING TECHNICAL INFO: - to prove the above points:

Link to book on the Infant mortality period (IFR):

http://books.google.com/books?id=vzy...esult&resnum=2



The Bathtub Curve and Product Failure Behavior
Part One - The Bathtub Curve, Infant Mortality and Burn-in
http://www.weibull.com/hotwire/issue21/hottopics21.htm
The Bathtub Curve and Product Failure Behavior
Part Two - Normal Life and Wear-Out
http://www.weibull.com/hotwire/issue22/hottopics22.htm



SUBJECT: SCREENING ELECTRONIC COMPONENTS BY BURN-IN.


Burn-in is a common term in the electronics industry and is the holding of an electrical device at an elevated temperature for a specified number of hours, generally with bias and an electrical load applied. (Bias is the application of an external d.c. voltage to set the upper and lower operating limits of a device) This is done in an attempt to stress all elements of the device at maximum rated operating conditions in order to reveal all stress and time dependent failure modes. In effect, burn-in is an accelerated aging process and is used particularly for semiconductor devices such as transistors, integrated circuits, etc.



Experience has shown that an electronic device will most likely fail in the early part of its operating life if it is prone to failure. The failure rate then levels off throughout the device's normal life and again increases when the device becomes old. The early part of the device's life is called the infant-mortality life stage. Those devices that make it through burn-in should, if they are operated within rated limits, have low and predictable failure rates.



MIL-STD-883 "Test Methods and Procedures for Microelectronics" is a military standard by which many semiconductor device manufacturers test their devices.

MIL-STD-883, Method 1015, Burn-in Screen, states that burn-in is performed for the purpose of eliminating marginal devices, those with inherent defects or defects resulting from manufacturing aberrations which are evidenced as time and stress dependent failures. In the absence of burn-in, these defective devices would be expected to result in infant mortality or early lifetime failures under normal use conditions.



Burn-in may be accomplished in-house or by an outside testing facility. The components used by a firm may be purchased with burn-in performed by the component manufacturer. The firm may then perform another burn-in prior to integrating the components into the firms equipment or device. The equipment or device may then receive burn-in as a completed device.

Note for us PC users with a "New-Computer", xyz electronic device- because most of us don't have ovens as described below- the next best method is to run the device - if it makes it to 30-days the device is considered "good"...

Burn-in is normally accomplished in ovens or chambers that will maintain the devices at specified test temperature and provide access to specified electrical connections. The burn-in arrangement should include a monitoring system which will record temperature, time, and bias voltage through-out the burn-in test period to ensure these parameters were maintained within specified limits. Burn-in time and temperature may vary but burn-in temperature is normally 125 C with an initial burn-in time of 168 hours.



.

TwoCables

Is it just me, or is this getting way more complicated than it needs to be?

__________________

WeAreNotAlone

1:There is nothing complicated in replacing XP with WIN7 on a brand new pc as the OP was desiring.
The only thing you may have to do is to re-confiqure the bios to look at the DVD drive for the install media (Win7 Disc), reboot the machine with the disc in the drive, run the installer selecting to blow away the existing partitions /and or overwrite them... and Bingo 20-25 minutes later you have WIN7 installed.


2: The point of my post was to bring to the forefront "Warranty Concerns"- for those who may be considering "messing" with a brand-new machine.

(A previous poster had brought up this issue and I was trying to expand on that for the benefit of someone at a later date who has not heard of Infant mortality period (IFR) as it pertain to electronics.)


3: Anyone that has a brand-new Pre-Built (OEM) machine is a fool if they have a warranty/return period to "blow-away" the "As-Shipped" OS / and or Restore partitions right away as it complicates getting tech /warranty support....

The point of my post being:

A: Just because something's "new"... it's not "good" (proven) until it's been run for several weeks..(30-days) .OR run in a oven /chamber @125C, for 168 hours under load.

B: Run a DUAL-BOOT for the first 30-days until the hardware is proven.

C: Have a plan in place to restore the unit to the as-shipped OS if needed during the balance of the warranty period.



.

SuppA-SnipA

wow
he-who-types-a-lot
in a nutshell: its a brand new system for the OP, don't erase the hard drive / partition unless you can fully restore it to its original condition, in case should you have to RMA it.

__________________
We are the Red Tide - The Official S939 Appreciation Club and Knowledgebase - Canadian OCN Club - -Mozilla Firefox Club-