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. Well, it is possible, you get a router from ISP, with *standard* Admin/Admin (or similar password). In theory you should connect it ONLY to a PC (NOT to the DSL line) and configure it, including changing the access password). In practice most people (sometimes even the instructions from the ISP say so) will connect it to both network and DSL, leaving the standard password and start fiddling with it (and besides very often ISP issued routers will have remote connection enabled by default). If the device is "scanned" by some bot, it may well become infected in no time (do you remember the infamous "unpatched XP" before SP2 issues?). I wouldn't be surprised if an ISP put up some "external defense". But not everythng that comes from outside is bad, there has been also a "benevolent" router patching virus around, fiwatch/ifwatch JFYI: https://lootmyself.wordpress.com/2014/11/09/ifwatch-malware-part-1/ http://www.securityweek.com/developers-mysterious-wifatch-malware-come-forward https://gitlab.com/rav7teif/linux.wifatch jaclaz
  2. Good, so you can experiment with the suggestions in the given link (that one is related to WinPE 3.x, aka Windows 7 based, later PE's may behave differently). jaclaz
  3. This is what usually is called "looking for trouble". You mean when you run diskpart in the PE? jaclaz
  4. Coincidentally, right now there are two rather serious scandals over here in Italy, one which is making the headlines about a couple of people snooping on members of the parliament/VIPs emails and other electronic contacts, and one with a much lower impact, but actually IMHO much more serious, about the Justice department "discovering" that (lawful) interceptions that were technically implemented (recorded and stored) by (authorized) private contractors were accessible remotely - besides by the Court/Prosecution Offices - by the contractors themselves (and that some of these contractors may have actually peeked in them ). Of course we have an Italian saying for that, "segreto di Pulcinella": http://www.wordreference.com/iten/segreto di Pulcinella anyone with more than 2 neurons AND a very-very basic IT background would have suspected that, just like your security monitoring company example. jaclaz
  5. Don't forget Hanlon's Razor: https://en.wikipedia.org/wiki/Hanlon's_razor jaclaz
  6. @Dibya Which part of "this memory dump doesn't show up in BlueScreenViewer" is difficult? jaclaz
  7. Now some (interesting ) news on the Windows 10 Privacy front: https://blogs.windows.com/windowsexperience/2017/01/10/continuing-commitment-privacy-windows-10/ I won't make any comment if not to highlight the Author's name: Terry Myerson (and I have said enough). jaclaz
  8. In alternate realities everything is possible ... You wouldn't really expect Gordon Kelly or any web journalist (or any journalist for that matter) to double check or verify anything they post or write, would you? The source is here, however: https://mspoweruser.com/project-neon-windows-10-first-look/ which very likely gets the source from: http://www.windowscentral.com/new-design-language-windows-10-project-neon that actually gets info from here: http://www.numerama.com/tech/212129-en-2017-microsoft-va-retravailler-toute-la-charte-graphique-de-windows.html and back to the circular: http://www.numerama.com/tech/222885-project-neon-des-premieres-images-pour-la-nouvelle-interface-de-windows-10.html to: https://mspoweruser.com/project-neon-windows-10-first-look/ This stuff is not entirely unlike (please read as exactly like) gossip papers, some info is true, most is not, and around them everything (and the contrary of it) can be (and actually is) written ... jaclaz
  9. Just saying ... https://www.exploit-db.com/exploits/38707/ An "overview" by manufacturer: http://www.cvedetails.com/vendor/899/D-link.html jaclaz
  10. But not hurried enough to refrain from posting this (also for mind readers): jaclaz
  11. ... as long as they find gullible customers actually buying them bells and whistles ... jaclaz
  12. No prob jaclaz
  13. On the other hand, dogs tend to be somehow more collaborative ... jaclaz P.S.: Someone is more creative ...
  14. Actually it would be easier to get Server 2003 and be done with it ... @burd JFYI, the "I read somewhere" comes third, right after "dog ate my homework" and "the devil made me do it, officer" in my personal list of common excuses. jaclaz
  15. I am afraid it will be impossible, for some reasons my editor seems to believe that it is not correct to attach "by jaclaz" to a work by Charles Dickens, and he won't publish it. He seems to think that misrepresenting the Authorship of something is somehow ethically wrong. (and - crazy it may seem - this applies also to work which is not anymore under copyright, patent or any other IP protection). jaclaz
  16. Well, not really. It was exactly overlapping the development of Windows 2000 and XP, the full specification was released in August 2000, but was pre-announced (to the public) in October 1999. Windows 2000 was released end of 1999/beginning of 2000. Windows XP was released October 2001. (and is/was IMHO nothing but a renamed Windows 2000 with a few bells and whistles attached to it). The Windows XP Professional x64 Edition came much later (and is/was definitely nothing but a renamed Server 2003 with a few bells and whistles attached to it). BUT in the meantime (end of 2001/beginning of 2002) there was a Windows XP 64 bit Edition (which was for Itanium, i.e. IA64), most probably that one is the Windows 2000 "Janus" 64 but with some bells and whistles attached). https://technet.microsoft.com/en-us/library/bb457053.aspx What we don't know is if the good MS guys completely ignored the 1999/2000 AMD news or if they made a parallel "Janus" for x64, that later became the Server 2003 x64 and the Windows XP Professional x64 Edition. jaclaz
  17. What makes you think that? GPT is only a (perverted) way to index volumes, a volume (intended as a contiguous extent on disk with a filesystem applied to it) is not dependent on the way it is indexed, whether it is read only or r/w depends on the filesystem driver (and to the specific setting for the volume). Another thing is booting a pre-Windows 8 Windows OS from a GPT disk (that simply won't happen any soon without modifications to the involved bootloaders). jaclaz
  18. And you were also given not one but two possible sources to buy that thing from the US, both (Walmart.com and tigerdirect.com) "well known" and "reliable". jaclaz
  19. jaclaz

    edit

    I perfectly understand the point you were trying to make . Only, it doesn't apply. Let's take good ol' nlite. You wrote it. You maintained it, fixing the bugs and introducing the little fine tunings users suggested. The thingy is/was solid enough nd good enough. This ONLY happened because you are NOT a lazy/lousy programmer. You did not make any money from it, all the non-commercial people were happy to use it even if it was closed source, most of the commercial people used it nonetheless even if it was explicitly prohibited,the few honest people were deprived to use it in a commercial environment. What would have happened if you decided to open source it? Nothing much, the same people would have used it. with the addition of a few people more. Maybe one or two wannabe programmers would have forked it, probably creating a "monster" with a zillion more options, some of which would have worked only on wednesday nights IF there was a full moon. Nothing much overall, but in any case the quality of your program wouldn't have been different. jaclaz
  20. What was the difficult part in "apart "ENTRIES_DIBYA.ini"? Which contents are: ;================================================================================== ;# Special thanks to 5eraph and Ramsey (admin of zone54) ;# thanks a whole lot to user_hidden for update pack :# thank a whole lot to harkaz for SP4 and patched file ;# ------------------------------------------------------------------------------------------------------------------------------------------------------------------- ;# This file contains a list of all entries that need to be added to various Windows ;# Thanks a lot to all guys/gals of zone62,msfn,driverpackforum, ryanvm forum,wincert,overclocker. ;# Greatest respect and thanks to nuhi for nlite and Ryan ,Signet for RVMi ;=================================================================================== ;This section contains version info for nLite& [general] builddate=2/11/2016 description=This patch will remove 3.25Gb Ram limit of xp sp3 32bitand extend the limit to 128GB language=English title=Dibya"s RAM PAE LIMIT PATCH ADDON version=1.0 website=www.Ryanvm.net You didn't even write two lines to explain how to use that, you don't - even sideways - mention the source of the files, yet it is "Dibya's" and "by_Dybia". Sorry, gotta go, I have a meeting with an editor that is going to publish "A Christmas Carol" by jaclaz. jaclaz
  21. "Existed" doesn't mean "released". For all we know it may have existed (or it may not) as x64 or as ia-64. All we know for sure is that at a certain time the good MS guys were working on it, and the little news we have are about Itanium version, but we don't know if a Intel x64 was under development. https://www.csee.umbc.edu/portal/help/architecture/idfwin64lab.pdf In any case today it would be largely pointless. jaclaz
  22. I know, but it's not like we know for certain if that thing ever existed at all. jaclaz
  23. Ah, well, if you say so ... http://windowsitpro.com/windows-server/64-bit-windows-2000-track-mid-2000 ... though supposedly it was ia-64 ... jaclaz
  24. XP64 (for the good and for the bad) is very similar (please read as "is essentially") Server 2003 x64, like most server editions it does need good, suitable hardware (particularly suitable drivers) AND a number of desktop programs may have issues. About the BSOd reboot, simply disable the automatic reboot: http://www.pctools.com/guides/registry/detail/229/ jaclaz
  25. Well, if cdob says that Intel xhci is not supported in Vista, that's it. I knew for sure about XP, but evidently that extends to Vista. As a generic rule of the thumb 1/2 to 2/3 of the readme.txt or however info coming from drivers packages and drivers sites is either wrong or obsolete (or both), so NEVER (and I do mean NEVER) trust them at face value. Just in case, what I wanted to know was VID and PID, just 8086/A12F, you don't really need screenshots to provide this info (but of course you need to experiment and learn how to retrieve it ). jaclaz
×
×
  • Create New...