[Kriptical]

Originally Posted by Tomcrit

I am not sure if i am reading correctly but why did you make the whole E drive a Docs folder. If the move doesn't create a folder I.E
When moving move to E:\MYDOCS

then make a folder called My Docs on that drive and target that folder to be the doc folder. Possibly windows handles my docs folder differently which is why it appears to do nothing with all of those game files inside it.

I dont recall exactly but when I clicked the My Documents folder and hit move thats how it happened. I was expecting it to put the My Documents Folder and its contents on E: rather than kind of make the whole drive My Documents. Have to admit it looked odd when it happened but I figured that was what you guys were talking about and since I'd never seen//done it before just figured that was 'ok.' /gulp. I have a ton of music on it atm, there is probably enough room on the Raptor to fit it if I /copy it over but not for much longer

So by your commment it appears as if I should have seen something like E:My Documents rather than E: with the contents of My documents inside ? Also, if this is incorrect how would you suggest 'fixing' it. I've tried renaming the HD My Documents even (lol..) and no joy. I suppose I could create a folder in E: name it "My Documents" and put all of the other folders in this one ? At this point its looking as if this issue could occur again. I just dont get how if Im in Control panel, or My Computer or something and click My documents it takes me right there but this is somehow borked \

[rhagz]

Put simply, you probably don't want to move that folder. It's going to cause all kinds of conflicts and I think there is a new standard where software is compelled to use My Documents to store .ini files and save games and other assorted junk. Some things apparently don't like saving some things to one drive when everything else is on another. Maybe they will patch the game to address it, but it's not a common scenario so probably isn't a priority.

[Kriptical]

Originally Posted by rhagz

Put simply, you probably don't want to move that folder. It's going to cause all kinds of conflicts and I think there is a new standard where software is compelled to use My Documents to store .ini files and save games and other assorted junk. Some things apparently don't like saving some things to one drive when everything else is on another. Maybe they will patch the game to address it, but it's not a common scenario so probably isn't a priority.

err crap...so how would you go about fixing it. I dont have a restore point. If there's too much info on E: could I make a folder, put all of the music in it then reformat and install window's on C: deleting all of the other folders except the one with the music in it of course. Currently, C: is just window's and all that good stuff. No biggie wiping that. The music collection is really the only thing I really really need to protect on this rig atm. Thanks again for the advice if this set up is 'odd' and going to cause problems I really want to get it fixed ASAP. Thanks again.

[rhagz]

There are ways to move it properly, but it sounds like you didn't do it. You can't just click and drag.. it takes a little more. If you have room on the main drive you may want to try moving it back and getting everythign working in factory install condition then use a guide like: http://www.solo-technology.com/blog/...uments-folder/ to try it properly.

This works well in XP, but if you are using Vista that is the OS that has issues apparently.

[Kriptical]

Originally Posted by rhagz

There are ways to move it properly, but it sounds like you didn't do it. You can't just click and drag.. it takes a little more. If you have room on the main drive you may want to try moving it back and getting everythign working in factory install condition then use a guide like: http://www.solo-technology.com/blog/...uments-folder/ to try it properly.

This works well in XP, but if you are using Vista that is the OS that has issues apparently.

Hmm ya thats how I pretty much did it but somehow the name My Doc's didint go through, just made the whole drive it. Guess I borked something somewhere. Moving it back to default now. Wel'll see how this goes Thanks for the help

Edit: it said it couldnt move a few files and borked the move back before it moved everything over. It said I could still access the files on E: and I can and everything looks ok there, the My Doc's is back on C: and appears to have created a My Music there, leaving the other one as Administrator's Music. Think everythings ok? Im going to try to install that game on c: and see what happens. Hard to say but looks ok atm.

[Kriptical]

Just wanted to say thank's, migrating My Doc's back seemed to C: seemed to do the trick. Thankfully it managed to fix all of the game's issues.

[rhagz]

Originally Posted by Kriptical

Just wanted to say thank's, migrating My Doc's back seemed to C: seemed to do the trick. Thankfully it managed to fix all of the game's issues.

Glad it's working. I would say just manually copy any files that didn't get moved that you need to save then reformat the drive and start clean with it. You can still use it for basic storage, you just probably should make custom folders that may not be accessed the same way clicking Docs -> Music would be. Could always make a custom shortcut though and place it on the desktop or in the Doc's folder.

[Kriptical]

Ran into a little problem with wiping the drive, the music files are > than the Raptor. Being that things are seeming to run fine, do you think its ok if I wait a month or so to pick up an external HD(Planning to do that around that time anyway for back up purposes) then load the tune's on there, frag E:, put it back and go along with things. Or do you think that the drive could have something else "wonky" with it and I would be putting my collection at risk and should just go grab one. ($ is fine, wife faction ...lol pretty good but would be better in a little ) Thanks again.


P.S. If any of you live near Philly I'm buying beers one of these days!

[rhagz]

Nah, if everything is working fine it should be fine.. you just will have to deal with a split up music collection for a while.

[Kriptical]

Originally Posted by rhagz

Nah, if everything is working fine it should be fine.. you just will have to deal with a split up music collection for a while.

Cool, cool, its actually not so bad, the only thing thats annoying atm is when using services like URGE it autodownloads to My Music. While being able to set that DL to a specific location would be great I can live with moving it. Would certainly be cool if Microsoft was as nice about moving the My Music folder as the My Document's but what can ya do

[Slide]

The drive manufacturers are actually correct.

Kila as a prefix means 1,000, and Mega is 1,000,000 - so therefore a MB is 1,000,000 bytes.

For 2^8 reasons a Kilobyte was defined as 1024 bytes as it was a reasonable approximation using a 10 bit number. Anything outside of RAM and CPU registers is defined using decimal.

[Tomcrit]

Originally Posted by Slide

The drive manufacturers are actually correct.

Kila as a prefix means 1,000, and Mega is 1,000,000 - so therefore a MB is 1,000,000 bytes.

For 2^8 reasons a Kilobyte was defined as 1024 bytes as it was a reasonable approximation using a 10 bit number. Anything outside of RAM and CPU registers is defined using decimal.

1 kilobyte of data is 1024 bytes so if i buy a hard drive of 1kb then i should expect it to be able to store 1kb

i agree that kilo = 1,000 and mega = 1,000,000 in the outside world but the manufacturers are working in the computer industry which defines them as you stated above. They are just being misleading because it sounds better for them. If the definition was in the other direction and KB was less than 1000 then they would never mention kilobyte and megabytes

[Slide]

Originally Posted by Tomcrit

1 kilobyte of data is 1024 bytes so if i buy a hard drive of 1kb then i should expect it to be able to store 1kb

i agree that kilo = 1,000 and mega = 1,000,000 in the outside world but the manufacturers are working in the computer industry which defines them as you stated above. They are just being misleading because it sounds better for them. If the definition was in the other direction and KB was less than 1000 then they would never mention kilobyte and megabytes

...

There are two slightly different definitions of the size of a gigabyte in use:

* 1,000,000,000 bytes or 109 bytes is the decimal definition used in telecommunications (such as network speeds) and most computer storage manufacturers (such as hard disks and flash drives). This usage is compatible with SI. Quotes from Seagate: "The storage industry standard is to display capacity in decimal",[1] and, "One gigabyte, or GB, equals one billion bytes when referring to hard drive capacity".[2] Similar quotes are found on the websites of other storage manufacturers.
* 1,073,741,824 bytes, equal to 10243, or 230 bytes. This is the definition commonly used for computer memory and file sizes. Since 1999, the IEC recommends that this unit should instead be called a gibibyte (abbreviated GiB). Microsoft use this definition to display hard drive size, as do most other operating systems [3]. Every operating system uses this definition when referring to the size of files.

[Tomcrit]

"The storage industry standard is to display capacity in decimal",[1] and, "One gigabyte, or GB, equals one billion bytes when referring to hard drive capacity".[2] Similar quotes are found on the websites of other storage manufacturers.


But of course the storage industry adopted it as it very much suits them.

* 1,073,741,824 bytes, equal to 10243, or 230 bytes. This is the definition commonly used for computer memory and file sizes. Since 1999, the IEC recommends that this unit should instead be called a gibibyte (abbreviated GiB).

Beg pardon i have never ever heard of a gibibyte has anyone else outside of the IEC?

hehe just did a google on it and for an official measure the term pretty much only apears in dictionaries.

Is there another possible reason other than to mislead, that they come up with a size and definition to store data, that uses a completely different size and definition. After all the data is still laid down and moved around in the binary format and the storage chunks/allocations etc still use the same I.E an allocation unit on most XP machines is 4096. Pretty much the whole computer world uses and understands the KB=1024 standard even the storage industry within the heart of their drives etc but they choose to advertise the sizes of their storage in a different measure.

I am interested as to how many on here have heard of the gibibyte (abbreviated GiB) and more especially heard it actually being used as opposed to reading of it in some dictionary, after all it was defined and given to us to be used 7 years ago?

[rhagz]

Gibibyte? What the hell..

Are there mebibytes and kibibytes too?

[Kriptical]

Originally Posted by rhagz

Gibibyte? What the hell..

Are there mebibytes and kibibytes too?

jib E bite ....lol...teh Aussie Byte -x..


sorry couldn't resist...I just said it to my wife who responded.."shot who in the what now.."

[akuthia]

i thought the "official" problem was with byte vs. bit. Basically, the bit is the 8 point math, that computers are built on/around. However, at some point, the computer industry decided we were too stupid to understand 8 bit, 1024 kilobits= 1 megabit, so they rounded it off, made it power of 10, and called it a megabyte.

[evilsofa]

Manufacturers love to confuse you about whether they are talking about bits or bytes. You get 8 times as many bits as you do bytes, so it sounds a lot better to say, for example, that a wireless 802.11g router transfers at 54 Mb/sec than to say that it transfers at 6.75 MB/sec.

Did you see what I did there? 54 Mb/sec = 54 megabits/sec = 6.75 megabytes/sec. But you'll have lots of people thinking it's 54 megabytes per second. Advertisers and vendors will confuse even themselves by misusing Mb vs MB or Gb vs GB.

Just try and find out how fast your hard drives transfer data. The Raptor 150GB hard drive entry on newegg lists in its specs that it transfers data at 1.5 Gb/s on its SATA-150 interface - a claim which doesn't sound right to me since 1.5 Gb/s = 187 MB/sec, and SATA-150 is 150 MB/sec, so how...?

I have found the wikipedia List Of Device Bandwidths to be invaluable in keeping straight what goes how fast.