• Content count

  • Joined

  • Last visited

  • Days Won


jaclaz last won the day on February 16

jaclaz had the most liked content!

Community Reputation

796 Excellent


About jaclaz

  • Rank
    The Finder
  • Birthday

Contact Methods

  • Website URL

Profile Information

  • OS
    none specified
  • Country

Recent Profile Visitors

5,970 profile views
  1. The benefit of what? The OP has a given PC and a given type/model of SSD's (of limited size). He has issues with the specific install (though he succeeded with similar hardware). You posted a oneliner suggesting him to buy another (bigger sized) SSD, something that seemingly doesn't address the base questions: 1) WHY the setup doesn't work? 2) HOW can I try to find what is the issue? (and hopefully solve it) Of course similar advice can be found all over the internet, typically, still one-liners: 1) buy something else 2) that is not possible 3) upgrade your (hardware, OS, software, whatever) to a newer version etc. And this right after the OP praised the MSFN forum for providing "more good advice" than the rest ... jaclaz
  2. Are you trying to make an example of the kind of support/advice that can be easily found outside MSFN? @waltah From what you describe it seems like a driver issue , or maybe a timing problem. Since you are using a FAT32 volume anyway, I would try (on a 16 Gb SSD) to attempt installing the XP from DOS (actual DOS) via WINNT.EXE, so that we remove one of the variables (the CD loading), see (only seemingly unrelated): Method description (via Wayback Machine): http://web.archive.org/web/20080302101935/http://www.911cd.net/forums//index.php?showtopic=16713 Also are you sure that the (I believe needed) SATA drivers are integrated into the source? (or are you installing in IDE compatibility mode? For the sake of testing I would try a surely UNtouched source, even if it doesn't actually install it may porovide some hint on where the process has issue). jaclaz
  3. You can find *anywhere* a full description of a MBR. Briefly: The MBR contains a partition table. The partition table contains four entries, each 16 bytes. Each entry describes a partition and contains 4 set of fields (not in this order) check any partition table description: 1) boot/no boot (i.e. hex 80 or hex 0) 1 byte 2) partition ID (1 byte) 3) CHS data, two fields, one describing the start address and one describing the end address, CHS addressing is nowadays obsolete, but it takes anyway 8 bytes. 4) LBA data, two fields, one describing the start address and one describing the number of sectors, each field is 4 byte, and as such it can at the very most represent 2^32-1=0xFFFFFFFF or 4294967295 sectors. Thus the limit is: 4294967295*512=2,199,023,255,040 bytes A good question would be what happens if one creates on a (512 bytes/sector) hard disk two partitions, one starting on LBA 2048 and extending for (say) 4294967295-2049=4294965246 sectors and a second one starting on LBA 4294967294 and extending for 4294967295 sectors? Would this move (with the limitation of the two partitions) the limit by another 2.2 Tib? jaclaz
  4. Maybe easily, but not "common", I believe you are the only one I know that uses one of such arrays. Maybe other people have not the knowledge or cannot afford a similar setup, which even today is not exactly "cheap". jaclaz
  5. JFYI, a reborn ZX80 (using only discrete components, unlike the ZX81): http://blog.tynemouthsoftware.co.uk/2016/12/minstrel-zx80-clone.html jaclaz
  6. Yep, but overall it is more than anything else some misinformation and/or outdated info due to the accumulated information on technology that changes (the hard disk hardware) under a "static" piece of software (the Operating System). At a given date the 2^32-1 sectors limit did imply that the max capacity to be around 2.2 Tb because *all* disks were 512 bytes per sector. Soon after the hard disk manufacturers found a possible way out by using bigger sector sizes, but in the meantime, due to the "transitioning" via the so-called "AF" drives (that I believe different manufacturers, besides calling them with different names also implemented slightly different) and to the remaining problem (no support for booting from larger than 512 bytes sector disks in most OS's) the piece of info remained valid. After all, imagine the fuss that would have happened if someone bought a - say - 3 Tb drive only to find out that it was either (512 bytes or AF) not fully accessible or (4Kb) not bootable, I can understand why it was simpler for the manufacturer not to make the distinction, particularly when the good MS guys were trying all they could to ditch MBR in favour of GPT (and BIOS in favour of EFI/UEFI). The ironic part (as I see it) is that in the meantime SSD's became the *standard* or *almost standard* main boot (internal) devices and they are still - after several years - nowhere nearing the 2.2 Tb size limit, and they are all (or almost all) emulating the 512 bytes sector size anyway. jaclaz
  7. The limit is not in "cluster" size (that is a characteristic of the filesystem), it is "sector" size (that is a characteristic of the hardware). Besides that, there are issues in a number of OS in booting from a non 512 bytes sector size hard disk drive (which does not affect obviously "data only" disk drives). It is not however really a "hoax", the two things belong to different times, the number (of sectors, not clusters) limited by the 32 bit address space in the MBR partition table came out earlier, at a time when disks were still mostly or very largely 512 bytes sectored only and had not actually reached if not maybe in high end disks the 3 terabyte size, and while the disk makers started making the 4k sectored disks (that effectively "move" further the issue to around 16Tb) Microsoft decided to not update existing OS to handle the matter and jumped on the (Intel driven) UEFI/GPT bandwagon (and to mostly 64 bit). In other words, until the disks were 512 bytes sectored the limit was there and it was not solvable, and when later it became solvable it was decided by MS to not fully solve it on MBR scheme and adopt GPT (forcibly coupling it with UEFI without any real technical reason) and the disk manufacturers didn't want (or couldn't) provide support for that. And coupling disks with USB enclosures may provide "funny results", JFYI: jaclaz
  8. http://web.archive.org/web/*/http://awergh.110mb.com/* jaclaz
  9. IMHO of particular interest is the reason why all Windows drivers are dated “June 21, 2006” : https://blogs.msdn.microsoft.com/oldnewthing/20170208-00/?p=95395 jaclaz
  10. And not even in your post ... ... out of curiosity, what does it do? jaclaz
  11. This story seemingly continues here .... (just to keep things as together as possible) : jaclaz
  12. You seem like having "ghost" devices. A USB hub (unless it is an external one) is not something that you connect and disconnect, likely that device is the result of a previous (failed) experiment, and has nothing to do with a USB HD being detected/working or not. You need to clean your Registry of the non-existing (currently) devices and make sure that you don't have anymore them. As a side note, you have a question mark device (Other Devices) which means that some device have not been recognized at all. When checking devices like that, it is always a god idea to set device manager as "by connection" so that you can understand the whole "chain" of devices (and drivers) connected with the one creating an issue, and - to exchange info on devices on the board (as opposed to screenshots) it is advisable that you use devcon (you can find a copy of the redistributable version here): Though not the most user friendly tool around, running: devcon find *USB*>foundUSB.txt and: devcon findall *USB*>ALLUSB.txt will provide a quick list of all devices connected to USB, the existing and the "ghost" ones, as well, something like devcon hwids USB\ROOT_*>USBhubs.txt will provide a list of all USB root hubs. It is easier this way to provide a "complete" overview of the machine status (and data can be copied). jaclaz P.S.: Previous thread, just in case:
  13. Check this first thing: http://www.opalapps.com/sparse_checker/sparse_checker.html Here you can find a "collection" of more related tools: http://reboot.pro/topic/20487-any-tut-on-expanding-c-partition-on-many-ramdisk/ http://reboot.pro/topic/20487-any-tut-on-expanding-c-partition-on-many-ramdisk/?p=192898 There is also a built-in command in fsutil: https://technet.microsoft.com/en-us/library/cc788025(v=ws.11).aspx but it cannot - I believe - create sparse files directly. jaclaz
  14. Oww, come on, you need only the RunasTI.exe, I am attaching it nonetheless. And - normally - you do not run .cmd's by right clicking on them, but rather you open a command prompt (as Administrator) and in it you execute the batch, this way you have more control (but yes, you can type exit, possibly more than once will be needed, when you have finished with the batch). jaclaz RunAsTI.exe
  15. Well, JFYI, it's not at all like "news", that photo has been floating around since - at the very least - 2013, it is supposedly coming from Moscow, Russia: http://owned.com/p/welcome-to-advertising-in-moscow-er-maybe-not-9427 jaclaz