jaclaz

Well, NTFS.SYS (in itself) it is a "stable enough" driver. It is more likely that it reflects - under stress - a misbehaviour of the hardware (RAM or hard disk or it's controller, or even just the SATA cable or of the network, though the latter is less probable). Try to not use hibernation for a few days and see if the behaviour remains. jaclaz

I think it's just Charlotte having some form of allergy to it. jaclaz

Yep: http://www.wired.com/threatlevel/2013/09/freedom-hosting-fbi/ The internet expert was will be right, after all : http://www.msfn.org/board/topic/157597-win-xp-past-apr-2014-was-will-xp-be-supported-until-2019/?p=1047341 jaclaz

Chromium is the actual "engine" on which also Chrome is based. http://code.google.com/p/chromium/wiki/ChromiumBrowserVsGoogleChrome As said: Let's see possible reasons to use a (non-local, and possibly anonymous) proxy: to have some speed advantage in the transfer of data (unlikely, but possible in certain parts of the world) to reach an address that your ISP, firewall, IT guy, etc. has blocked (for whatever reasons) to reach an address which the provider has linked access according to IP geo-localization to reach an address in particular emergencies of failed DNS/internet section/whatever to reach an address in such a way that the other end cannot have your IP address (or geo-localization) to reach an address whose site administrator has listed your IP in a non-allowed or "black" list to make a second or nth registration/subscription to a service that links IP to accounts to reach an address that allows not concurrent connections from the same IP, when needing to make multiple connections to trick NSA (or other three or more letters agencies) into believing you are the devil and do not exist As I see it, #1 to #8 are all possible uses, while #9, while entirely possible, may NOT give the results expected . If you prefer I believe that NO proxy is "safe" (for the scope of #9), if "they" are after you , "they" will get you. jaclaz

I would say "interesting but not surprising" . In my dinosaurish view, something that is not there (if not really-really needed) and/or it is smaller, will result in faster operations ..... http://www.msfn.org/board/topic/145209-the-smallest-possible-size-of-bootsdi/?p=933421 jaclaz

The good news are that most probably it is a re-branded Logik-100/hipshing IR608: http://reciva-users.wikispot.org/Summary_information_on_Reciva_radios http://www.hipshingelectronics.com/Prod.asp?ID=39 IF this is the case, this page may be of use: http://logikir100.tripod.com/Logik.htm The bad news are that latest firmware is was seemingly available online from Reciva.com but needs/needed registering. . The generic gpl page is out of reach until end of september (at least): More generically, that thingy seems "Barracuda" based (whatever it means) which leads us right here: http://www.sharpfin.org/index.php?title=Main_Page As expected a JTAG access and some tinkering may be needed, but it seems like everything is well documented :thumbsup: Particularly, getting a login in order to change firmware seems doable without particular hardware, only with the GREATEST care and attention. http://www.sharpfin.org/index.php?title=Changing_Firmware http://www.sharpfin.org/index.php?title=Enabling_Login Still, unless you have as a hobby this kind of mods, it is not something I would suggest, as there is a concrete risk of "bricking" the radio. http://www.sharpfin.org/index.php?title=10_Sure-Fire_Ways_to_Trash_Your_Radio jaclaz

Good :, that is a sign that you have likely bought a "fake" USB stick (or anyway that a "wrap-around kind of issue happened because of some error of the controller/settings) and what you got is "just" the "wrap-around" issue. The second image you posted is identical to first one, which confirms how the error you got initially with DSFO could be ignored, but also that filesystem oriented recovery is impossible on that stick. Remember that Photorec cannot find the "original" filenames, and often it may mistake a file type for another (just as an example Office .xlsx and .docx files may be retrieved/recognized as .zip (mainly because they actually ARE ZIP files ). It is recommended to "post-process" the results from PhotoRec: http://www.cgsecurity.org/wiki/After_Using_PhotoRec http://builtbackwards.com/projects/photorec-sorter/ to first group recovered files, then, if you have issues, you may want to use TriD on the files that have not been identified properly: http://mark0.net/soft-trid-e.html You are welcome, I am sure . Normally the last file(s) that you saved won't be recoverable, BUT if what happened is a "pure" wrap-around issue, you may want to try re-sequencing the image. Translation/example: Imagine that you have what the OS/filesystem thinks to be a (very, very small) 10 sector device: 0123456789 and you want to write on it the words hello and world, if the device actually has 10 sectors you would have something like: 0123456789 helloworld BUT if it has, say, only seven sectors you would get something *like*: 0123456 rldlowo By appending a second copy of the image, like: 01234560123456 rldloworldlowo It is sometimes possible that also the "world" can be retrieved. In your case, the "queer" fact is that the image is larger that the original device, so it is possible that this wrapping around happened at "controller" level and you are actually have already a re-sequenced image. jaclaz

I will throw this one on the table also (just to keep things as together as possible): http://reboot.pro/topic/18573-hideandprotect-ntfs/ jaclaz

Are we going on a spin-off of the usual "RAM is there to be used and Windows knows how to use it alright" vs. "RAM is there to be kept free and just absorb some (little) power" flamewar? jaclaz

Dude, HOW exactly are we supposed to know the EXACT model/make of the *whatever* you are talking about? Just in case Standard Litany (NEEDED): http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html More generally you will need some kind of "hacked" firmware (that may or may not be available) and possibly get a JTAG access to the actual circuits. Nothing I would recommend, if you are asking about it (CATCH 22 ) jaclaz

Yes, to take advantage of the USB 3.0 speed, most manufacturers use this new design (for the "high-end" sticks). Of course there is normally not any specifications about the innards, but as always the info exists:: http://www.thessdreview.com/our-reviews/kingston-datatraveler-workspace-32gb-windows-to-go-usb-3-flash-drive-review/ http://www.eteknix.com/mushkin-unveils-usb-thunder-flash-drives-with-sandforce-controller/ OT but not much, maybe we are near to these ideas becoming "common" : http://reboot.pro/topic/5634-creating-a-universal-pe/ http://reboot.pro/topic/5880-mini-pc-4x4/ I can imagine a new form of "outsourced" PC where the "core" is just a processor and a USB 3.0 controller/hub and you just connect to it *anything* from video card to mass storage, from network (cabled or wireless) to HID's.... jaclaz

Well, seemingly not much efforts needed, at the light of the Terabyte page, only to try the Windows 8 version of the BOOTMGR. Hard to believe , but after all Windows 8 does have *some* uses. jaclaz

I cannot believe that - IF the issue is in the booting only - it can be solved by modifying the \boot\BCD (which AFAIK contains NOT any particular info related to the filesystem and it's cluster size). If you don't want to add a partition, not even temprorarily for the sake of the test) , you can do with a boot floppy image: http://www.multibooters.co.uk/floppy.html an image like described can be mapped and chainloaded by grub4dos alright, and it will need not any re-partitioning, while removing the doubt that it is a BOOTMGR issue of some kind, which is a mere (though educated ) guess based on your "it doesn't boot." report (which is not an actual description of what actually happens ). About the "sense", what I was trying to highlight is that the theoretical "increased wear" may happen only on a limited number of cells, since the number of files less than 4 Kb that are often re-written on a "normal" Windows 7 system are very few, maybe the relevance of the issue is "amplified" by any file which is a multiple of 4 Kb but not of 8 Kb? And, call me reckless if you want , according to these: http://www.anandtech.com/show/7173/samsung-ssd-840-evo-review-120gb-250gb-500gb-750gb-1tb-models-tested http://www.anandtech.com/show/6328/samsung-ssd-840-pro-256gb-review http://www.anandtech.com/show/6459/samsung-ssd-840-testing-the-endurance-of-tlc-nand one of those thingies are guaranteed for 5 years and are estimated at around 11 years of duration. By that time we will likely be using Windows 13.4 SP2¼ and 256 Gb will be the space needed for just the bootmanager and configuration file. jaclaz P.S.: After all my guess was educated enough: http://www.terabyteunlimited.com/kb/article.php?id=392 http://support.microsoft.com/kb/2272294

Well, the point I was making was slightly different. I was pointing out how the use of *any* proxy, NO MATTER where it is located is in itself a "security risk", until you have some "serious" information on WHICH actual proxy is used, WHO manages it, and HOW the connection is established (if the route to the proxy, like some 2/3 of all world internet traffic "goes through" a US "hop" the use of the proxy is "pure moot"). Consider what I would personally do if I were the NSA : since I cannot close the can of worms that was opened, I develop a "secure" browser channeling all traffic to a single proxy OR manage to get full control of the cable/optic fibre/whatever connected to that proxy, no matter where it is physically located. You might appreciate how in doing this I am having the not-so trifling effect of pre-filtering the users, it is obvious that out of all the people that will start using the "safe" browser there will be some legitimately trying to protect their personal data, but also a large part of those actually trying to "hide something": Since the issue I am seemingly having (as NSA ) is the sheer amount of data I collect and analyze/store/whatever such a kind of pre-filtering may actually make the operations easier/simpler. The equation being (in my perverted mind ) that if someone uses an (anonymous) proxy, there must be some reason for doing that, let's target these people with a "higher priority" than the "rest of the world". Could the Epic browser be a "covert operation" of any of the "three letters" US agencies? Could - even if not such - be a "preferred target" by the above mentioned agencies? The answers, my friend, are blowing in the wind.... jaclaz

BAD news. The sectors you posted are just "hex gibberish". This can usually depend on two things: actual hardware failure (a Pro may be able to do a chip-off, re-calculate ECC's and hopefully recover something) a size wrap-around (which is typical of the "fake sticks" Kelsenellenelvian hinted about)It should be easy to understand which is which by running Photorec. If it finds at least some files, it means that it is #2, if it doesn't find anything (or anything readable) it means it is #1. There could also have been an issue in the making of the image, as DSFOK reported: 99,874,111,488 bytes whilst the device "presents itself" as being 61,918,150,656 but that could be caused BOTH by a hardware error and by the wrap-around. Try: D:\dsfok>dsfo \\.\PHYSICALDRIVE1 0 512000 f:\usb\first100_2.img If you get the same: the first100secs.img is an actual representation of the first 1000 sectors of the USB stick (thank you for the 900 more sectors you posted ). However next step is trying Photorec: http://www.cgsecurity.org/wiki/PhotoRec_Step_By_Step jaclaz

Let me doubt that Gigabyte (or any motherboard manufacturer providing a UUID for a motherboard) will EVER release to final customers a tool capable of removing it (or - if you prefer- capable of "anonymizing" the board). I will stand by my "likely not possible" (in practice). Of course - as said - in theory it is perfectly possible, the exact same way it is embedded in factory it can be changed. jaclaz

I understand that, I was not-so-sure about that particular SSD having 8 Kb pages (and operating on them as "full pages"). In any case - and with all due respect - it seems to me like the idea makes little sense. Let's take two extremes for the sake of reasoning. only 1 (one) file below 4 Kb is in the filesystem several thousands files below 4 Kb are in the filessystemIf #1 the impact of *whatever* is null. If #2 while the impact of the *whatever* may be relevant or noticeable, in order to reduce it you will further reduce the available capacity of the SSD considerably. My suggestion was however to try making a new (smallish partition) (Yes, a "boot" partition) not entirely unlike the one Windows 7 makes on a non-partitioned disk, with just the BOOTMGR and the \boot\BCD and see if you can boot from that one the "main" partition with the 8 Kb sized clusters . Since it is just a test you can use a part of the space you have free (it is not like having 100 Mb less than the current 23.85 Gb will change *anything*). jaclaz

Guess WHY exactly I underlined the use of the proxy in the quote I posted? jaclaz

There are some (big) differences with "common" sticks. The first one is not a USB stick (as you are used to think about it) it is a USB 3.0 to SATA bridge + a 256 Gb SSD, miniaturized. The second one is more or less (IMHO) the effect of a not-so-new idea summed up to some good marketing, noone - with the exception if the very few that are secret agents, terrorists, etc. (and the paranoids of course), actually *need* that kind of encryption/security (and as a matter of fact it was born from Goverment intitial financing : http://www.ironkey.com/en-US/why-ironkey/index.html JFYI, my personal take on the matter, of course there is nothing wrong with encryption in itself, only in the way it is (mis)used, as I see it, the real issue are people whining about having lost their precious data : http://reboot.pro/topic/9297-safeboot-42-plugin-for-bartpe/?p=80938 jaclaz

To continue on the "tiny, but not too tiny" designs, this one seems to me not that bad: http://www.emtec-international.com/en-eu/S200_usb_flash http://www.emtec-international.com/en-eu/S200_usb_flash?quicktabs_1=1#quicktabs-1 It seemingly does not protrude too much from the socket (hence it is difficult that it can be broken by accident) but still seems to provide some "grip" to extract it. jaclaz

The UUID you mentioned derives from *something* which is *somehow* embedded on the motherboard BIOS. If you can access the BIOS and change the *whatever* that produces the UUID, then you can change it. As a matter of fact a number of motherboard will return all FF's because their BIOS has not that kind of info. So, not only "not simple", likely "not possible" and in any case "very specific" to the specific motherboard/BIOS/firmware/UEFI/whatever. jaclaz

Duffy, please be aware that a number of laptops DO NOT have an "install partition", but rather a "recovery partition". The difference is not-so-slight, if the second, after you reun th erecovery procedure the disk will be restored to the exact way it was when delivered frm factory (i.e. you will lose each and every later installed program, configuration and data residing on the "system" partition Compare with: http://www.msfn.org/board/topic/163601-will-a-recovery-clean-the-hard-drive/ jaclaz

Well, it would be queer, if there is enough RAM for 2K, that a 98 system could be so noticeably faster. It seems to me like either you have some issues with hardware or have some conflicting driver/whatever or anyway you are not having 2K runnning "correctly": With less than 256 Mb (without any antivirus) or less than 512 Mb if an antivirus is running a 2K will be very slow because it will swap to hard disk as mad , but you can easily verify this observing the behaviour of the system in Task Manager. jaclaz

@Trip Yep but that is about Physical Sector size (that has nothing actually to do with cluster size). @Grofluigi There may be issues with the boot code (and just with it). Since you do have some 23 Gb free on that device, you can experiment, making a (temporary) partition using that space. Care to share the source of your opinion of using an 8 Kb cluster being *any* "better"? jaclaz

Since it is a non-partitioned image, i.e. what is commonly referred to as "superfloppy", most of TESTDISK capabilities may be ineffective (a large part of the TESTDISK scope is to re-build the MBR partition table). But still some of the features may be of use. Depending on how exactly (and under which OS) the original FAT32 formatting was performed, there may be a backup of the bootsector. I.e. this: http://www.cgsecurity.org/wiki/Data_Recovery_Examples#The_type_of_the_file_system_is_RAW_-_Recovery_of_a_damaged_FAT_boot_sector may work for your case, or this: http://www.cgsecurity.org/wiki/Data_Recovery_Examples#Two_FAT32_partitions_to_recover Basically there are four sets of meaningful info in a "normal" FAT32 volume: the bootsector CODE (which has NO relevance whatsoever if not for booting) the bootsector DATA (including the BPB or Bios Parameter Block, a set of info about the volume and it's layout, of VITAL importance to find the FAT32 tables the FAT table(s) - normally in two copies, containing the address of each and every file saved in the filesystem the actual DATA (i.e. the files saved in the filesystem)Of course you are interested in just #4, which IF the files were not fragmented can normally be recovered by "direct parsing" of the volume (please read as "using PHOTOREC"). Please understand that files recovered by PHOTOREC will "loose" their original filename. The real problem comes if the files were fragmented, in this case a plain parser/carver cannot but get partial and often invalid data. As said there is no interest in #1, but to get to #4 in the "normal" way, you need #3, and to get to #3 you need #2. The good news are that if you find where exactly #3 is you can rebuild (using dome other info) #2, this is what TESTDISK may be able to do automatically (or that can be still done manually). The idea is first thing to find out if there is enough useful information in the bootsector or if there is a backup copy of it, then to find out if the FAT tables are still valid (or at least one of the two copies is). If you wish to have some "manual" help, make a small image with the first few sectors of the image you just made, something like: dsfo C:\mynice.img 0 51200 C:\first100secs.img (provided that the image you made is "C:\mynice.img" the above will produce a file "C:\first100secs.img" with the first 100 sectors, change paths/filenames according to your setup). Then, compress the file in to a .zip and either attach it to your next post or upload it to any of the free file hosting site and post a link to it. jaclaz