Jump to content


  • Content Count

  • Joined

  • Last visited

  • Donations


Community Reputation

0 Neutral

About meowing

  • Rank
    XP64 is a joy forever
  • Birthday 04/03/1966

Contact Methods

  • Website URL

Profile Information

  • OS
    XP Pro x64
  1. Come on, be honest:How often have you actually been *required* to use the shadow copy ability (which is yet another resource heavy indexing system slowing down and constantly monitoring each and every move that has been made in the OS), ever? How often did you encounter a 'problem' that could only be recovered using that shadow copy? I simply have not needed it once in the 17+ years I'm running machines on Win95 or newer operating systems. I already made backups. Which I also extremely rarely needed to use for some type of recovery. At least not often enough to warrant a HUGE space and power h
  2. I'm forced to use and admin Win7 for work-related matters, and I assure you: I still get stuff done MUCH faster in XP x64. If anything, Win7 is made for non-computer-savvy users, not for us experts. I strongly dislike the slowing and utterly dumbed down GUI of Win7, which comes out more complex for people like me. It's similar to the GNOME versus others in unix/linux world. It's a difference of philosophy regarding what is important for the user. I don't like systems that don't allow me to look and work under the hood. XP x64 by far STILL outruns my performance tests as well. I don't need fanc
  3. As I wrote earlier: Cleartype is post-processing of fonts that aren't good to begin with (or they wouldn't require cleartype). It's not something you should rely on, as it is not a reliable standard. Font smoothing is ugly blurring in my eyes. Cleartype never does it the way it should be done, or I prefer hard lines over soft edges. Also, NOT being able to see where it goes wrong in fonts would be my preference over software regulated changes in displaying them.
  4. Any news with the latest nvidia XP x64 release? ( NVIDIA Forceware 263.09 WHQL XP 64 ) Does it work with nLite again?
  5. By the way, a humongous 105 Megabytes(!) for their latest drivers-installer! Is all that crap really necessary? Geez, hope nvidia wakes up and stops forcing those huge packages upon us. I don't know anyone that actually uses all that crap they include.
  6. What are the advantages of HFSLIP x64 over nLite ?
  7. Yeah, all this has NOTHING whatsoever to do with XP x64 Edition. There's another lightweight PDF-reader I can recommend; http://www.stdutility.com/stduviewer.html Works great in XP64.
  8. Try http://www.techmixer.com/download-directx-10-for-windows-xp/
  9. Hmm.. my experience with XP x64 is the opposite of that. It's the fastest OS I have on my multi-booting main system. I had no problems finding drivers for any of the hardware that is in it (including full support for my SSD boot-drive and echoaudio sound-card). As far as I know THE ONLY companies refusing to properly distribute drivers for XP64 are Lenovo and Engenius/Senao. The rest either offers drivers for XP x64 on their websites, or states that their Vista x64 drivers also work for XP x64 (and by golly actually do indeed), or the 32bit drivers work.I will be working in XP x64 Edition for
  10. LOL, hexediting it in memory is a neat and cool option, but somehow I'd rather do the hex-editing beforehand.Thanks for all the hints. Should all work now.
  11. Just to be sure, you mean: title Loading XP install - plain /XP64/I386/SETUPLDR.BIN chainloader /XP64/I386/SETUPLDR.BINin your layout, correct? And .\XP64\WIN51 .\XP64\WIN51AP .\XP64\WIN51AP.SP2 .\XP64\NTDETECT.COM .\XP64\TXTSETUP.SIF should all still stay there?
  12. That's great! As I understand it, I need mkisofs to create the iso like this: mkisofs -R -b grldr -no-emul-boot -boot-load-size 4 -o grldr.iso iso_root and I read a lot about different versions of mkisofs, is there any version specifically fitting for XP x64 that you are aware of? OK, this is loading the unaltered setupldr.bin location; How would grub4dos work together with your layout as described above in Post #2? I assume nothing changes, except for the setupldr.bin being under /I386/ which needs to be hexedited still, correct?
  13. Leading stads for leadership, the leader, the best, the most used. grub4dos must do the job. Thank you. Yes, grub4dos is also used by the MultibootISOMaker: http://www.911cd.net/forums//index.php?showtopic=23375 but I have no idea (as of yet) how to set that up for a menu to run XP x64 setupldr.bin files.. if you find a decent example, please post it here.
  14. Given cdshell: the Boot Catalog contain a pointer to another sector. This sector contain data from loader.bin. So, I think this means you need to burn cdshell's loader.bin to that sector (as that sector of 2048 bytes), and that loader.bin sector on the iso tells the machine to check the folder /BOOT for the next step? Really strange, but this information on cdshell is not easy to find, so thanks for the Torito pointer. I can only find this http://cdshell.org/doc/loader.html but without examples. By the way, the links to cdshell in most guides are wrong, it's at http://cdshell.org/ now.
  15. Yes, I knew all that, but what binaries are they, how does the booting PC know it should read those, where is this set?
  • Create New...