jaclaz

HWPNP? PENETWORK? http://reboot.pro/7036/ jaclaz

NO, it isn't or it it isn't "only" for that. That's normal as there isn't any. No, there isn't, the way you have ben doing it. The way you have "backed up files" till now is "wrong" in the sense that you are using a feature of the OS that is NOT aimed to create "efficient", "compact", results. If you take some time to read about SAO writing mode, this would become evident. Imagine that you work in a (crazy ) company delivering (say) TV's. Your job is to load on a truck a TV (in it''s box), drive the truck, get to the customer house, unpack the TV and deliver/install it. Noone ever disposes of the empty packagings that remain on the truck. You will soon find out how once you have delivered a small number of TV's you cannot load anymore a (filled) Tv's box on the truck as all the space is occupied by the empty boxes. Now what a SAO writing approach behaves is more or less like this: you package the initial (first sesson) files in a (virtual) cardboard box complete with polystirene fillings you load the box on the CD on next session you take the contents out of the first box, and add them together to some new contents to a new, larger box you load this second box on CD and so on soon the CD will be full of empty smaller boxes and one large box, this latter being on top of all the other ones and the only one you can open and access, and that contains all what was once stored in the "previous" boxes Just as it is in the case of the truck, the right "strategy" is to put aside the filled box, empty the truck, then load again the larger "last" (filled) box on the truck. Translated it means: copy (temporarily) the CDRW contents on another media (hard disk) re-format/re-initialize the CDRW disc copy back to it the temporarily copied contents The alternative being used a "packet-writing" software/tool that allows to add data to a CDRW with less "overhead" (but this solution is less than optimal because of possible later reading issues of the CDRW). Some other news (good or bad it's up to you to decide) is that Optical media (like BTW *any* media) is not particularly reliable in the long term, and particularly "standard" recording apps and CDRW media are not the best choice. Burning apps dedicated to create backup media store additional (redundant) information on the media so that in case of mis-readings the errors are more likely to be corrected. As an example Infinadyne makes a (Commercial) tool called Accuburn-R: http://www.infinadyne.com/accuburn-r.html which adopts - among others - this "better be safe than sorry" approach. But there is also an excellent Freeware/Open Source tool, DVDisaster: http://dvdisaster.net/en/ to the same effect. jaclaz

Well, I thought that my post #9, which I will re-quote for clarity: was as plain as possible both in the terms used and in the concepts, and I don't see it as coming from any presumed "upper level" or "ladder", it represents a set of plain statements, coming from someone that not only - as it has later become evident - found those same facts before you did, but additionally provided relevant links/info specifically targeted to the matter leading to a possible solution. It is not like I posted (and I actually could have posted this , though I did NOT ): nor I did post (and again I could have done that) post a link to the known chocolate-covered banana issue: http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/put-down-the-chocolate-covered-banana.html I mantain that what was posted was: accurate written in plain enough English providing you a correct answer to the question you asked As I see it the actual issue is/was simply that you were (BTW in perfect good faith ) so positively confident in your experience (both in the specific matter and in your general experience as machine language programmer or whatever) that you didn't contemplate in the least the possibility that your initial statement was the effect of your perceptions being deceived by the Virtual Memory control panel and more generally by the XP OS behaviour. In another place, in another time, this was actually pre-coded in "Common Sense Advice", JFYI, point #f4.: http://reboot.pro/82/ You may also want to notice how I never stated a particular experience in anything, nor a particular "superior" state (possibly the board "status" of Developer and the 10,000+ posts speak by themselves to this regard) whilst you stated: so, if someone has attempted to, directly or indirectly, provide "credentials" to support his statements, and more loosely "self position" himself at a given level, that has not been me. To be fair, you did post: which is exactly what has been demonstrated by the evolution of this thread, notwithstanding your good experience on other (albeit similarly technically oriented) fields/topics, you knew nothing about pagefiles and Virtual Memory and were tricked by the behaviour of the OS. But now everything is (hopefully) clear and "cool", if any feathers were ruffled, they have been smoothed down again, and outside (at least here) though cold, the sun in shining.... jaclaz

On the OT news, the actual UK sentence (Apple vs. Samsung) reachable through one of the links by Charlottethehariot: http://www.bailii.org/ew/cases/EWHC/Patents/2012/1882.html is a masterpiece of clear, documented logical thinking really interesting to read. The essential points (bolded italics in the original as well): that were analyzed in detail and led to the: confirm the IMHO good synthesis provided by the Samsung guys about the US decision: jaclaz

jaclaz

A quote from: http://www.microsoft.com/about/technicalrecognition/julie-larson-green.aspx To which jaclaz has to say: (and jaclaz didn't get any "Common Sense Recognition Award" for this comment ) jaclaz

AQM, if you want tips about starting to learn programming, you could start a NEW thread here: http://www.msfn.org/board/forum/66-programming-c-delphi-vbvbs-cmdbatch-etc/ About the issue you had with WinNTSetup v2.3 cannot say by what it was caused, most probably by a "wrong" way with which you have partitioned/formatted the hard disk. The MBR you posted had the starting address of the volume at offset 0x3F (63). The PBR/VBR/bootsector you posted had the starting address of the volume at offset 0x00 (0). Of course such a disk won't boot, as these values should be the same. This has actually nothing to do with programming, but rather with knowing how hard disks, partitions and volumes "work". Go here: http://thestarman.pcministry.com/asm/mbr/index.html and read EVERYTHING on it. If you have doubts, question, feel free to ask them, in a NEW thread, the most suitable forum for these kind of questions is: http://www.msfn.org/board/forum/169-hard-drive-and-removable-media-issues/ jaclaz

Good , so now everything is hopefully clear ,.not very different from what initially stated: actually exactly as it was . JFYI, the working is more or less like this: the Virtual Memory Control Panel is nothing but a nice GUI interface to a few keys in the Registry. when you change settings in that, the corresponding keys in the Registry are actually changed. at reboot *something else* reads those keys and does what is written on them, BUT IF what is written on them makes no sense (like making a pagefile on an "external" device), the *something* tries to do it's best, like interpreting that the user wants a pagefile of a given size and actually makes one, only it makes it on the first device it sees as fit. on the other hand the *something* does not notify anyone about the interptretation it put into practice, leaving the related Registry keys "as they are", thus if you re-access the Virtual Memory control panel you see the same settings you input earlier Seemingly the 64 bit version is a bit smarter and doesn't list the external drives in the Virtual Memory control panel, thus preventing this form of miscommunication between the System and the user. The good news are that the "Kingston DataTraveler DTI / 4GB" that you used for the last several years has not suffered ANY wear due to the paging file rewrites and will probably last forever in that role . Slightly OT, but JFYI: jaclaz

Good, if you say so I am happy for you. Just as a check (that by any remote chance what the Virtual Memory control panel does not actually represents fully what is happening): Can you open that "USB card" in explorer and see if there is in its root (possibly hidden/system) a file named "pagefile.sys"? Which size is it? Can you resize the size of the pagefile (a few megabytes will do) in the Virtual Memory panel (and reboot) then check again the size of "pagefile.sys" on the "USB card"? (please check as well the Hitachi 61.4 or 'Old IDE' for the same file in root and do the same test resizing it) As I see it, if a pagefile.sys exists on the volume and it can be re-sized through the Virtual Memory control panel, a pagefile exists, otherwise it could mean that what you see in the Virtual Memory control panel might be deceiving) If you happen to have one of those IDE to USB cnverters/enclosures, can you try placing the pagefile on the same Hitachi HD, this time connected through USB? jaclaz

I will try again, SECOND WARNING: About: As you have been already told, here and on the thread on the other board you linked to, making such thing in software is either NOT possible or extremely difficult, and in any case it has not being done till now, and even when it will be made it cannot be "universal". It is not that by whining or by repeating over and over your questions/wishes you will in any way facilitate the creation of such a tool. We got the message, you want someone else (not you since you don't know programming) to write something that is (for those that actually know about programming) deemed impossible. Your wish is recorded, you don't need to insist on it, or if you wish to do so this thread (which is about JFX's WinNTSetup) is NOT the place to post about it or your other babblings. jaclaz

AQM The general idea is that you NEVER post twice one after another, if you have something to say you forgot and your previous post is the last one in the thread, please edit it adding new content. I cannot make head or tail of what you are talking about. With their limits, the software solutions are all "on the table", grub4dos, winsetupfromusb, rmprepusb, rufus, etc. Everytime I hear someone - expecially if self-proclaiming himself as a non-programmer - talking of "universal" OS installer I get shivers down my back. Such a thing does not (and CANNOT) exist. There may be solutions, like the mentioned ones that can usually be extended/adapted to another OS install (sometimes, not "always" or not always without modifying - possibly heavily - the install source). If you want an "universal" solution, you need a hardware one, at least THREE of them do exist, mentioned in this thread: http://reboot.pro/8944/ the iodd drive CDEMU (experimental) isostick (which has a dedicated sub-forum) http://reboot.pro/forum/132/ With the addition of this thingy here (which seemingly is not - or not yet AFAIK- multiboot): https://sites.google.com/a/lingoes.co.cc/cardrom_en/isoeasy jaclaz

Cannot say if already posted, if yes, sorry, otherwise interesting (poll on adoption of Windows 8 asked to Techrepublic members): http://www.techrepublic.com/blog/window-on-windows/rejected-74-of-organizations-have-no-plans-to-deploy-windows-8/6828 An interesting point is the difference in percentage by nation/country. (possibly driven by the HP help desk needs ) The actual report is for member only, though: http://www.techrepublic.com/whitepapers/windows-8-business-intentions-deployment-plans-driving-factors-roadblocks-and-strategies/32565796 As an OT note: How many "external" input devices does the MS Surface use? How many of them have seemingly a big driver issue? http://news.softpedia.com/news/Microsoft-Releases-Workaround-for-Surface-Sound-Issue-305508.shtml Seemingly we can use UNARY to reply to both questions.... jaclaz

Well, at least you are sitting in the car....and it isn't raining... SCOOP! I have a RARE image of Trip outside the restaurant (and with no car) attempting to protect the privacy of his customers : And before someone invents a new accessory for IT Admins without cars, it has been already invented http://www.prlog.org/11975147-zippaz-announces-debut-of-zippa-shade-universal-computer-umbrellafits-laptops-pads-tablets.html http://zippashades.com/index.php/zippa-categories/category/listing/27-computer-umbrella.html jaclaz

Your google-fu is seemingly low , the real issue is that the good guys put one of the nice robots.txt on their site (which is no more): http://wayback.archive.org/web/*/http://www.globsol.com/ (it should be this one ) Maybe you can get something of use by googling for: site:http://cd.textfiles.com/ nslookup but cannot say.... jaclaz

Mind you the good thing about freedom is actually that of being free to do things that may seem silly and unneeded, as a matter of fact : But life is also a comedy, you have to choose roles . If you want to play ol' time expert like in it's allright, but then you cannot seriously ignore how a pagefile should be on the faster (after RAM) storage subsystem you have available and that any "solid state" media has a "finite " amount of "write cycles" before it won't be working anymore. Or you can play n00b (which is also OK), but then you should keep a "lower profile", follow this tutorial (or a similar one of this kind): http://www.ehow.com/how_5887452_move-file-sd-card.html http://web.archive.org/web/20100430151734/http://www.extremetech.com/article2/0,2845,1679935,00.asp ignore any suggestions/info given on more "reliable" sources, like: http://forum.ultrabooknews.com/showthread.php?35638-WinXP-page-file-moved-to-SD-card http://serverfault.com/questions/46903/use-an-sd-card-for-your-page-file-windows-7 http://www.pocketables.com/forum/showthread.php?t=3416 http://forum.notebookreview.com/hardware-components-aftermarket-upgrades/371619-virtual-page-memory-sd-card.html http://forums.xsreviews.co.uk/showthread.php?tid=5792 or, better, the already given: http://reboot.pro/9461/ and be happy thinking that you can make a pagefile on a USB SD card without using a dedicated filter driver. (BTW putting a pagefile on a SD card may happen on particular hardware, but it is very, very UNlikely and simply not possible if the connection to the card reader is USB) JFYI, here is an illustrative article summing up the three filter drivers that are commonly used: http://agnipulse.com/2012/03/filter-drivers-removable-media-fixed-disk-windows/ jaclaz

Yep, that is one of the possible issues. You can try three alternate strategies: try imaging the same sectors "backwards" try imaging a larger chunk of sectors (and then extract from the larger chunk the relevant sectors) try imaging a larger chunk of sectors "backwards" (and then extract from the larger chunk the relevant sectors) It is UNlikely that the issue is due to the UNbricking, unless maybe if you cleared the G-List or whatever is cleared with i4,1,22 command, and that extent is/was on remapped sectors (still in the idea that it belongs to the part of the disk that you imaged in the 134 Gb), it is much more likely that your disk "bricked" because of some issue, and this issue is the reason. It is difficult to say if once diagnosed properly with suitable tools those sectors can be made accessible again JFYI, the 2048 offset is the "normal" offset for first Primary partition on a disk partitioned on either Vista or 7 with "default settings". Data recovery, in general, and expecially at a DIY with simple tools level, is more than anything else a sometimes you win, sometimes you lose kind of game . A professional recovery of that drive (if possible) can be anything in a range from US$ 500 up to a few thousands, it's up to you to determine the monetary value of those files you are missing. I am not familiar (specifically) with .pds files, maybe even if you miss the initial 16 sectors of it, it can be rebuilt/recovered or however important info retrieved from the rest of the file (or the program making those makes a temporary file from which you can gather the missing sectors).... jaclaz

You might not, we do: jaclaz

Or maybe those that have not such a fast connection INSTEAD of whining find workarounds.... You know, like: http://reboot.pro/13049/ jaclaz

For NO apparent reason: jaclaz

To have an idea of the other kind of issues when "playing" with non native resolutions: http://www.avsforum.com/t/720897/viewsonic-n3252w-1360x768-resolution-issues http://pixelmapping.wikispaces.com/Guide+to+1366x768 The "basic issue" is divisibility by 8, see: http://forums.entechtaiwan.com/index.php?topic=20.0 but how exactly the combo graphic card+ 98 drivers + monitor will behave exactly I cannot say, Powerstrip may be the only way to have them working "properly" . jaclaz

I would assume that missing as much as three bytes difference/anomaly in 512 is allowed and can happen to even the most accurate peep : http://reboot.pro/2246/#entry14607 jaclaz

Cannot say... The 1360x768 is NOT supported by the monitor, see the Samsung User Manual, standard signal table: it may work nonetheless, since it is "very near", but you are risking to have a brand bew monitor and need a new video card or use it at a less-than-optimal resolution. jaclaz

That monitor "native" resolution is 1366 x 768@60Hz, check your video card (and it's drivers) to see if it is available. Since it is an *almost* 16:9 display, the only other "common in the old times" resolution that might provide an acceptable quality is the WXGA 1280x720 ("pure" 16:9). jaclaz

I need to spend a few words in defense of the good MS guys If anyone reads this thread he/she may get the idea that suddenly the good MS guys became complete morons. This is not the case, to tell the truth they have always been like that and over the years have introduced, in each and every OS, some senseless feature or stupid quirk (as well as omitting needed information, over-inform on trifling aspects noone cares about, misinform on many topics, fail to fix evident and often admitted issues). The difference is that over the years we got used to the quirks, senseless choices and what not because each one - senseless as it might be - was an evolution of a previous senseless feature or of a known stupid quirk, what changed this time is that they introduced a whole bunch of completely new senseless features and many new stupid quirks and we are fed up with having to adapt to their (distorted) view of computing and find new workarounds additional to the hundreds or thousands we were forced to invent, discover or get used to over the years. So, most probably it's not like they changed, it is us: we are evolving.... jaclaz

JFYI, the spirit of Rule #2a http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules is to give a meaningful title to your topic and do not change it every time you ask a new completely unrelated queston on the same topic (which you should NOT ask here , but rather start a new topic about this new unrelated question/issue ). You see , till yesterday someone looking for a solution to a problem with internet connection with 98SE might have found this thread and tried changing cable connections, now that you have changed it's title the usefulness of this thread (regarding the internet connection issue) for anyone else but you has become none. jaclaz