Jump to content

jaclaz

Member
  • Posts

    21,300
  • Joined

  • Last visited

  • Days Won

    53
  • Donations

    0.00 USD 
  • Country

    Italy

Everything posted by jaclaz

  1. I am not sure to get it right. Here: http://it.us.syba.com/support_download/download/73-0203-1.html There are two files liinked to mentioning Windows98: http://it.us.syba.com/bin/silicon_image/sil3112-raid/sil3112-raid_drv_winall_v1.0.0.40.zip <- sil3112-raid_drv_winall_v1.0.0.40.zip and: http://it.us.syba.com/bin/silicon_image/sil3112-raid/sil3112-raid_medley_v1.0.0.19%20.zip <- sil3112-raid_medley_v1.0.0.19%20.zip On page: http://www.sybausa.com/resource/SD-SATA150R/ there is (including the one you mentioned) these three: http://www.sybausa.com/resource/SD-SATA150R/SD-SATA150R_Windows_98SE-ME-NT4-2000-XP-Server2003-XP64-bit-Vista-7-MacOSX-Linux-Netware.zip http://www.sybausa.com/resource/SD-SATA150R/SD-SATA150R_Windows_98SE-Me-2000-Server_2003-XP-NT_4.0,-Vista-7-_Linux.rar http://www.sybausa.com/resource/SD-SATA150R/SD-SATA150R_Windows_98SE-Me-2000-Windows_Server_2003-XP-NT_4.0-Vista-7-_Linux.zip None of these contain a suitable Win98 driver? I would also chek here: http://www.wecandobetter.com/dnload/BartPE/SourcefilesBkup/drivers/SCSIAdapter/SYBA-SATA-3x12-RAID-2P/ jaclaz
  2. Please be aware that Ghost (besides being a Commercial software) is not necessarily a sector based tool for disk imaging (it is , but only if use the right switches/settings). You want to image the WHOLE disk from it's first sector to it's last one, and NOT "only" a partition on it. It is debatable whether you can use software capable of skipping blank/unindexed sectors, but to be on the safe side there is ONLY the INTEGRAL "dd-like" or "forensic sound" approach. I strongly doubt that if you - by accident - delete a partition or wipe the whole disk it is in ANY way considered a voiding of a warranty. If you open up the notebook and change internal parts, it SURELY is. jaclaz
  3. Having backed up the license does not really mean that you will be able to re-install Windows 7 using a "generic" media, Sony, HP and similar "large OEM's" have a knack for adding *any* type of "road-blocks". It is very possible that your backup is only valid for the specific install that you can get through the recovery partition. BTW YB15FG is not found on the Sony site, are you sure about the model number? http://esupport.sony.com/US/perl/model-find.pl?mdl=YB15FG can you try and find it? jaclaz
  4. Yep , and this provision makes a lot of sense. Since it was not clear what exactly maanu was meaning, I posted a general kind of warning. The idea of by-passing the license limitation is "in the air" since a few days, so IF that was the idea, THEN it won't be acceptable/accepted on MSFN, there is an Italian (actually tuscan) proverb: [italian] [/italian] to the effect of: jaclaz
  5. It depends on the specific "mechanism" the "Recovery partition" is actually started on your specific machine. Basically there are THREE main "ways" a provision to boot the "recovery" partition: from an internal BIOS provision from a "special" MBR code provision from the BOOTMGR provision If case #1 you can do whatever you want. If case #2 you MUST backup the MBR code "as is" and restore it after having installed the XP. If case #3 you NEED to have the BOOTMGR still be the "main" bootmanager (i.e. you will have to backup it and the BCD and restore it after the XP install AND add to it a provision to boot XP). Additionally to the above the actual program that restores the system may "want" some specific settings in the partitioning scheme, or a given (hardcoded) size for the "target" partition or *whatever* else . To find out which is which, the only thing is experimenting, to do this SAFELY you will need a dd-like (or "forensic sound") image of the disk, so that IF anything bad happens you have a way out. AT THE VERY LEAST, you will need to backup a bunch of sectors, including the MBR the PBR's of the current partitions, the BOOTMGR and the \boot\BCD before even thinking of messing with that hard disk. Also, those laptops should have a provision to make a set of "recovery" CD's or DVD's, if this is the case, NOW it's the perfect time to create them (itf you haven't already done so. Even better, - IF possible - would be to create ADDITIONALLY a 7 install media, something like what is detailed here: jaclaz
  6. Most of these chipset specific utilities for reprogramming USB Flash drives only work under XP. They don't work under Vista/7/SVR2k8 as the drivers are written for XP. But this has to be tested specifically. Some utilities need to install a particular driver, but many will work through the "standard" USB driver (these one seems to be of this latter type). The issue is rather which settings are needed to be changed. In that tool the capacity is on the THIRD tab "Factory settings". I would try this version of the tool: http://flashboot.ru/Files-file-415.html If you get this one: http://flashboot.ru/Files-file-262.html it has inside some quick instructions (in Chinese) that may (or may completely fail to) be useful. Understanding how these tools work is often a nightmare and a hit 'n miss game. jaclaz
  7. I am not sure I get it. The actual problem in your setup is preserving (if needed) the "recovery partition" (AND the whatever way it is used to access it if needed). Is it a laptop? (usually desktop don't have "recovery partitions") Which EXACT make/model? Are you sure you want to delete Windows 7? Basically on some setups Windows 7 uses two partitions (the "system reserved" and a "normal" one) instead of a single one. There is no problem (if you REALLY want to get rid of Windows 7) to delete both partitions and install XP. jaclaz
  8. I am not going to have Uncle Norm on Christmas Eve this year.... jaclaz
  9. Filename NOT FolderName... Yep . Example: C:\somefolder: <- means "a suffusion of yellow" C:\somefolder\ <- means a path to a folder C:\somefolder\filename.ext <- means a path to a file C:\somefolder\filename.ext:mystream <- means a path to a stream named "mystream" attached to file filename.ext To view (and delete) streams, you may want to use STREAMS : http://technet.microsoft.com/en-us/sysinternals/bb897440 BUT also directories can have stream attached, i.e.: C:\somefolder:myotherstream <- may mean a path to a stream named "myotherstream" attached to directory "somefolder", BUT it should be: C:\somefolder\:myotherstream INSTEAD (with the backslash) Only IF that is the case (C:\Documents and Settings\Elkian\Local Settings\Temp:winupd.exe meaning a stream named "winupd.exe" attached to the directory "C:\Documents and Settings\Elkian\Local Settings\Temp") the DEL command won't have any effect (since you would need to delete the directory, with RD) jaclaz
  10. Answer is simple too : No. http://homepages.tesco.net/J.deBoynePollard/FGA/questions-with-yes-or-no-answers.html BUT you should have NOT non-backed up data ANYWAY. jaclaz
  11. Sure it does not . It was in fact, and as clearly stated, related to this: and nothing else. If you want to know whether the line Yzöwl posted is "more efficient" than the one you suggested, you may ask so. (but that would be ANOTHER question). In fact I don't see a "\" (backslash) after "C:\Documents and Settings\Elkian\Local Settings\Temp" and before the ":", and AFAIK/AFAICR the ":" is not part of a path nor of a filename. (actually colon is not an accepted character in *any* file/directory name under Windows, so it probably comes from the output of the unreferenced antivirus) jaclaz
  12. JFYI: (just to put everything in some perspective) The label on the disk says what firmware was put on the disk in the factory. The Seatools tells what firmware is currently on the disk. It is very possible that the firmwre was updated (by Maxtor or by the whomever actually assembled the disk drive in the external case) If you have SD3A to WHICH firmware would you want to upgrade? (SD3B should be the latest? ) (cannot say if it applies to your specific model) If you want to live dangerously, have a look at this, too: jaclaz
  13. It is something worth a try. Read the original post by Aviko: it seems to me clear enough. See these ones also: Please understand how this is NOT "exact science" (basically because we have NO actual idea what the issue with those drives is, i.e. we have NOT a "diagnosis") and because we have no idea how exactly the cure (IF the cure is appropriate to the disease) works. Imagine that you have an initial stage of pneumonia, and you take some aspirin instead of going to the doctor and get an appropriate diagnosis and corresponding cure. The aspirin won't make you any harm, and if you are strong enough (and lucky) it may also cure the pneumonia (or contribute to the self healing). jaclaz
  14. Try running DEL /?. You will notice how: DEL [/P] [/F] [/Q] [/A[[:]attributes]] names the red part is inside square brackets. Would this mean anything? jaclaz
  15. @All Be VERY AWARE of Rule #1.a of this board: http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules jaclaz
  16. Some info. The bla-bla-bla about clean-rooms is exactly that (bla-bla-bla). There is not any actual need for a clean room to open and close a drive (we are not talking about reconditioning/buliding a disk drive, we are talking about having the disk work for the few hours needed to get the data from it). You can get away with a poorman clean room (making one using an aquarium or a barbecue, or something like that, is easy, see an example here: http://hardmaster.info/eng/articles/30-05-2009.html Swapping platters is easily doable on SINGLE platter disks only. On multiple platters disks (and expecially with the recent Seagate ones) it is simply NOT possible to do it without specific alignment tools and A LOT of experience. Even "parking" the head outside the disk surface is a very delicate chore that needs a specific tool and/or, AGAIN, LOTS of experience. Here is one specific tool for the Seagates heads: http://forum.hddguru.com/hddsurgery-seagate-7200-read-write-head-change-tool-t17926.html Here is one of the traditional "platters exchange tools": http://www.hdrconline.com/platter-exchanger-tool.php And here is the"newish approach" (transplant the whole spindle): http://forum.hddguru.com/hddsurgery-spindle-replacement-tool-for-seagate-manual-t20514.html jaclaz
  17. It is possible or probable that the two disks simply suffer from "something" else that may (or may not) be fixable. (see previous page for some comments on other commands). From the little you say the #1 may still contain data, we have seen disks that needed to be recovered, an example is here: the fact that #2 is "slow" should mean (beisdes whether it "contains data" or not) like a yet to be resolved issue, or simply a "gone" disk drive. If you need help with examining the data (yes, there is definitely some data on them, only it may be inaccessible or unreadable) start a new thread, please. jaclaz
  18. As said before "nice" is very personal, but robocopy GUI's do exist: http://www.sh-soft.com/front_content.php?idcatart=156 http://betterrobocopygui.codeplex.com/ http://technet.microsoft.com/en-us/magazine/2006.11.utilityspotlight.aspx http://technet.microsoft.com/en-us/magazine/2009.04.utilityspotlight.aspx http://copyrite.dyndns.biz/ jaclaz
  19. If we assume it's too expensive to send the bricked HD to a data recovery company: OBVIOUSLY. But since you (and I) have NO idea of the amount of damage that issuing such a senseless (in the sense of "since we do not know exactly what it does nor a way to undo", thus senseless) command may provoke, it should NEVER be advised, EVEN if the disk is going to be given to a PRO anyway. I mean, the diffference between (say) 500$ (drive with problems BUT NOT with some internal tables wiped) and (say) $1000 (or NO way to recover) is too big to be underestimated. No. What I am saying is that we know FOR SURE that a given set of commands is capable of reviving a bricked disk IF the bricked disk is suffering from a certain given issue (actually two of them) AND IF the cause of such issue(s) derives from a given firmware problem. We also know that in some cases the same fixing procedures, since they represent a kind of "reset" for the disk, may help also with a few different issues. We know nothing (or not enough) about different procedures, it is IMNSHO irresponsible to suggest something that you don't know for sure what is and how it works unless you know FOR SURE that it is NOT "desctructive". We are supposed to be here helping people solving problems, NOT inducing them to create some (see the previous issues about swapping boards, you plainly suggested something that was plainly wrong AND dangerous for the integrity of the device). You are perfectly free to suggest everything that you think fit, as well I am free, EACH TIME you will IMHO post something dangerous or senseless or both, to SCREAM about this VERY ALOUD. If the procedures in the Tutorial by CarterinCanada + a few other NON DESTRUCTIVE command do not work, it means that the issue is outside our (very limited) sphere of competence. jaclaz
  20. If needed; DO NOT EVEN THINK of EVER using/suggesting/mentioning the M0,1,1 command! In the best case it will completely wipe the hard disk, MOST probably it will also render the disk UNUSABLE! Once you set apart the spite, Gradius collected and translated some info, while Aviko knows what he is talking about BUT by chance or by design he posted half truths or incomplete info. This is among the reasons why the tutorial by CarterinCanada is advised (by me), it may not cover all issues but it covers the specific one without any deceiving or dangerous instructions. jaclaz
  21. I don't think that you will find *any* bad sector. On modern hard disks, the disk firmware should re-locate the bad sector mapping (and increase one of the S.M.A.R.T.) registries. But no, you don't have to re-scan the disk, not even with old controllers, unless of course, but it really is a VERY rare occasion, the bad sector "appears" in the short time between your check and the re-partitioning. jaclaz
  22. And, with all due respect , you completely fail to listen to his/her requests. What you suggested (BTW containing a lot of "common sense" ) are UNrelated to the question. Now, OP may have asked the "wrong" question allright , but your answer - again very senseful - is to ANOTHER question. Carpenter's comparison: Q. How do I nail some plywood to close a broken window? A. You put the plywood on the wall, than you place on it a nail with point on the plank and head facing you, then you hit the nail head with a hammer several times until the nail is fully inseerted in the plank and wall, repeat for a few more nails.. Your answer: So you want to build a wall. For this you will need cement, sand, a mixer, and a few blocks ...... Cement block walls are safer than plywood. jaclaz P.S.: you can get the cement blocks for very lttle (and some masonry advice ) from this guy on Craigslist : http://www.collegeslackers.com/pictures/craigslist_cement_blocks
  23. I guess some lines need to be drawn *somewhere*. Having the pagefile on a "separate" partition BUT on the "same" disk, makes sense in some situations (as an example multi-boot). Having an auto-managed pagefile is IMHO "pure folly", BUT if you really want to have it auto-managed, having it on a separate partition, makes some sense. 10 Gb for the pagefile is - this time IMNSHO - "pure folly". This said, I would love to know the arguments you used (the ones that your colleague was NOT convinced by). Usually? I have observed over the years two kind of opposite behaviours, one by Admins/Network manager in big companies, the other in small, almost unmanaged businesses, both of which could be connected to "ignorance" and "arrogance/supponence", relating to security: "since I am the Admin I block everything, I don't care about what is needed by the people that actually work, this way I won't have security problems" "since it is a small firm, I don't need any security, "they" won't target me, hence I don't need an antivirus, let alone block ports or protocols Another couple ones (same sources): "it's not possible" (no matter what the question was) "no problem" (no matter what the question was) Explanation: Admins in big companies tend to be less friendly than ones in smaller one, but often both have no idea of whatever the problem is or what a suitable solution to it would be. jaclaz
  24. ....and maybe if you ask the wall nicely it could move a little bit and let you pass..... jaclaz
  25. You won't like the answers. A1. There is "NO" *best* tool that I know of. Whether a disk will develop bad sectors and whether bad sectors are going to spread and/or will be relocated automatically by the disk firmware is something that no program can forecast reliably and anyway you cannot do nothing about it. BTW, if you want to unneededly put additional stress on a disk you may want to run from time to time Victioria, here: http://majorgeeks.com/Victoria_for_Windows_d5688.html though it won't probably run on 64 bit and, if you choose the "wrong" settings, you can easily botch a hard disk for good. It is a tool that is more suited to check a disk when attempting reconditioning it than a "periodical check". A2. There is "NO" *best* tool that I know of. There are dozens of similar tools that read S.M.A.R.T. data. It's the S.M.A.R.T. mechanism that is the issue, IMHO. See here: A3. Benchmarking a disk makes very little sense (unless you are trying to publish a disk speed comparison). A benchmark is only useful as "comparison" metrics. Real life (and real data transfer) is very different from what any bechmark reports, for a quick idea of what is happening I normally use Atto, though since it is aging, probably it is not fully reliable on newish disks/OS.I guess that if you want such an app you shoud check published disk benchmarking tests and see what they use. jaclaz
×
×
  • Create New...