Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About bwana

  1. tnx again for your thoughts. secure erase doesnt see the ssd power cycling did nothing i have an email into crucial/micron-we'll see what they say
  2. I started installing windows 7 to a micron c300 ssd. I chose the whole ssd as the install target, The install cycle started and then i realized i forgot to save some raw space for a linux install. so i just shut off the computer. reboot into win 7 installer now shows the ssd has zero bytes available. bring up a cmd terminal with shift +f10 and start disk part. list the disks -> the ssd is disk 0 select disk 0 'clean' it says 'cleaned' reboot-> still only zero bytes on the ssd. plug the ssd into another windows 7 box-> ssd doesnt show up in explorer. however, I do see it in device manager. bring up administrative tools->computer management->disk management , NO SSD! uninstall the ssd in device manager. reinstall the diver by selecting 'scan fr hardware changes' no improvement-ssd still invisible in disk management boot into ubuntu linux-> gparted doesnt see the ssd. So....., I did download the firmware update,C400 mSATA Rev. 01MG Bootable Media Firmware Update, from here http://www.micron.com/products/solid-state-storage/client-ssd This did recognize the disk and successfully flashed the firmware! However the disk is still seen by the windows startup disk as having zero bytes. diskpart still gives the same errors. so i rebooted with the firmware update disk. this is a linux based iso. by holding f8, it traces the boot process. the following erros are reported: InitiDiskBIOS reported 0 sectors/track, assuming 63! Error reading partition table drive sector 0 BIOS reported 0 sectors/track, assuming 63! The disk continues to boot properly and this time recognizes that the firmware does not need updating, it is already at version 01MG, the most recent. Curious that the disk is seen by the bios and some parts of windows but not resettable. i attached the ssd to a windows xp system and ran crystaldiskinfo. This utility says my ssd is 2199 gb! not bad for something that is supposed to be ~128gb. so how can i fix thix this ssd? minitools and easus wont fix it.
  3. I have a PC (named PC1 running win xp with sp2 and various tweaks) that doesnt permit other computers to copy files from it. Operators from other PCs (PC2 - win xp sp2 with antivirus installed, PC3 -win xp sp2 stock,and PC4 -win2k sp4) can delete and transfer files to PC1 but when a file from PC1 is 'dragged to the desktop of the other machine by its operator, a dialog appears ~~~~~~~~~~~~~~~~~~~~~~ Cannot copy file:Access is denied Make sure the disk is not full or write protected and that the file is not currently in use. ~~~~~~~~~~~~~~~~~~~~~~ PC1 can copy, transfer and delete files on the other machines no problem. PC2, PC3, PC4 have no problem with each other. A new share on PC1 has the same behavior as the preexisting shares-the operator of PC2(or PC3 or PC4 for that mattter) can push files to it, delete files in it, but NOT copy files from it - the same behavior is exhibited if i create a new folder on PC1 with wide open permissions (full control) for everyone, guests, administrators and set security wide open as well - full control for everyone. also, if the operator of PC2 tries to copy a file from PC1 into a folder on PC2 where the file already exists(drag a file to PC2)-interesting behavior occurs- a dialog pops up asking if i want to replace the file- i click yes- a progress bar appears indicating the copy process and at the end of that-the dreaded file access denied error dialog appears. the preexisting file on PC2 now has disappearred. this problem only appears to the operator of PC2. the operator on PC1 has full control. In short, PC1 will only let macs copy files from it! A pc with a mac infatuation? How can I fix this?! I ran the network setup wizard on the other healthy pcs and then executed the netsetup app on PC1 with the floppy i generated on pc2. Still, no improvement. Help?!
  4. why would this - http://www.msfn.org/board/index.php?showto...&st=0&p=356029& not work for you?
  5. Integration of NVIDIA's nForce RAID and AHCI drivers

    please forgive me for not reading and UNDERSTANDING what your first post said. After reading the next 52 pages (instead of cutting to the last post) i realized the havoc that the new nvidia folder structure creates for the new windows xp install. And how the integration of the various files from legacy and sataraid,etc. folders works to get around and solve the problem. Yes I am building an nf4 system and this is how I came across the current problem. I will update my sig when complete. I also noticed in the first post you explicitly mention the legacy folder but in the actual text of the thread you started by suggesting files be pulled out of the pataraid folder. i guess at some point it was discovered that the legacy folder has what's needed. (somewhere around the end of the page 20s) thank you for your fine work as it enabled a quick install. along with auto patcher, winxp install is a breeze. What happens when nvidia comes out with an upgraded nforce driver set? does the installation overwrite these older files? does the raid array use the new sata drivers?
  6. Integration of NVIDIA's nForce RAID and AHCI drivers

    Thank you Fernando 1 for this guide. However, I am a little puzzled. I have been struggling with Windows XP install onto an nf4 mobo and the F6 floppy route for the Nvidia drivers. My troubles (described in this post in detail (http://www.dfi-street.com/forum/showthread.php?t=47592) relate to how only older nvidia drivers worked. The 6.6 and 6.7 nv sata raid drivers resulted in an endless reboot cycle. A reader on that board suggested that slipstreaming was flawless for him and in fact referred me here. Why would slipstreaming solve a problem with what appears to be a driver issue? Also, this fellow is talking about the bus and the network driver conflicting (http://www.dfi-street.com/forum/showthread.php?t=46714&highlight=microsoft+engineer) Is this what you have been discussing in the previous few posts? Please forgive me if you think this is irrelevant and I will post a new message for this issue.