jaclaz

Seemingly those with 2 Mbit chips do have a bootblock (unless you accidentally overwrote it) and they can be used also as "programmers" using hot-swap (but you need another similar one). You will need a working floppy. https://web.archive.org/web/20050409123244/http://www.bev.me.uk/ruslan/Updated_BIOS_recovery_tips.htm Is it an AWARD or a AMI BIOS? https://www.overclockers.com/forums/archive/index.php/t-315360.html https://web.archive.org/web/20041207133136/http://www.amptron.com/documents/Recover.pdf jaclaz

Yep, but now you really cannot boot (to BIOS) anymore? Also some motherbaords/BIOSes have the one (or the other) BIOS recovery modes (it depends, but before actually going to the chip programmer, simpler paths should be preferred), if you detail EXACT motherboard/BIOS we can check if yours has one of such provisions/procedures. jaclaz

Sure but de-soldering (and re-soldering, or better resoldering adequately) a BIOS chip is not something that should be advised, it is of course doable but not exactly easy-peasy. Here is a video using a "test clip" (no need to solder/desolder): https://www.youtube.com/watch?v=2Y06x1f22B0 jaclaz

You may want to get GL viewer: https://www.softpedia.com/get/Programming/Other-Programming-Files/OpenGL-Extension-Viewer.shtml http://realtech-vr.com/admin/glview but most likely you will get 1.1 or maybe 2.1 (provided you have guest additions properly set and installed). It is a known issue in Virtualbox, see: https://stackoverflow.com/questions/27566569/is-there-a-vm-that-i-can-do-opengl-3-with-virtualbox-and-vmware-dont https://community.khronos.org/t/sketchup-needs-opengl/72978 It is not clear (to me at least) if something changed in very recent Virtualbox releases, but - besides the support to version 3.0 which might be still missing, I have seen here and there lots of related issues conneted to the actual Linux (and the hardware drivers used in it), user running the Virtualbox and what not. You may want to try in your OS/hardware a VmWare VM, that should be able to run Sketchup (or more generally provide openGL 3.0): https://forums.sketchup.com/t/sketchup-in-virtual-box-windows-10-guest/33500 jaclaz

Be aware of the risk of confusing evolution in actual hardware with that a the OS. On a SAME machine where 2000 runs with "good" drivers and without the need of post-end-of-life third party patches, it usually runs circles around XP (and is as stable if not more stable). I got a the time a HP Vectra who had BOTH NT 4.00 and Windows 2000, and it took me far more than one week (a few moths) to definitely switch to 2000. jaclaz

R.I.P. jaclaz

Naaah ; jaclaz

A LCD monitor has a "native" resolution (number of pixels horizontal x number of pixels vertical). Any resolution set in the video card different from the native LCD resolution either won't work or will be an interpolated resolution (fuzzy/blurred and usually also slower) or won't show the whole desktop area (as jumper hinted it would behave like a "virtual desktop"). @TrevMUN That could be a very good idea to evaluate if the display has issues and needs to be replaced anyway, otherwise it seems like a very creative way to waste 120 £ + the time and there are some risks when changing a laptop screen (clearly doable as a DIY but not exactly "easy-peasy" if you are not familiar with the procedure). jaclaz

If you have certain, specific NEC device(s) with Intel Centrino 6205/6235 and Broadcom 802.11ac Wi-Fi cards ... ... you probably won't read this: https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-1903#706msgdesc I have no better words than "total madness" to describe the above. jaclaz

Actually, the point is that the point isn't yours (exclusively), as it is (partially, i.e related to apply only) the same JFX and wimb had already made (and that you confirmed through your experiment). jaclaz

What was said by JFX and wimb was that wimlib was faster (or better or both) for capture and that wimgapi was faster (or better or both) for apply. A single test comparing wimlib against wimgapi for apply and showing that wimlib is slower (some 10%) doesn't seemingly change anything in what was stated earlier. jaclaz

As a matter if fact whether it makes a difference (at all) is subjective, and it depends on the context. Shaving of 1 minute out of 10 is roughly a 10% increase of speed (objectively), but if you: 1) launch the apply and go get a short walk or a cup of coffee and come back after 15 minutes it becomes totally irrelevant. or: 2) keep staring at the screen for 11 minutes, staring at it one minute less is a huge improvement. jaclaz

Queer point, since on this forum someone actually already suggested diagnostics (and diagnostics only) steps: 1) to check cooling 2) to disconnect EVERYTHING from the motherboard but the keyboard and video (which BTW would have solved your issue #1 - but probably not #2) well before hinting that it could be CPU or RAM were bad (the PSU was already changed). Besides PSU having been already excluded by the OP, it remains however a very likely cause when a computer either shuts off suddenly or fails to fully boot or starts booting than suddenly switches itself off (as it was the OP case), so that would have been recommendation #0. The next (good) ones were provided by Tripredacus: 3) check visually electrolytic capacitors for any bulging ones 4) try rotating or removing RAM sticks Your #2 case is different, and as you say "rare", you were having a beep code when attempting to boot, and it remains - since it was not reproducible - an "unsolved" case, for all we know it could have been an oxidized ground that re-gained contact when you wiggled the PS/2 connector (or even a bend in the PS/2 keyboard cable) or *anything else* that was somehow reset moving the case. In absence of a better explanation, I tend to categorize these issues as "voodoo". jaclaz

Sure , as said it was only a generic note. jaclaz

OT , but this seems - sad as it it is - like a very good reason (not-so-often cited) to release the source code/publish it, that generally speaking applies to any non-Commercial/Free program. jaclaz

Here is some reference (on BootIce versions): http://reboot.pro/topic/21956-bootice-v1332/ according to wimb/alacran 1.3.4 has an issue with UEFI. jaclaz

Roses are red (at least they were red 9 years ago). Any chance that you can start a new thread actually describing in detail what you are looking for/asking? (as opposed to reviving a not connected old-old thread with your vague references)? WHAT is "QSoft-2"? In which way is FLTK: https://en.wikipedia.org/wiki/FLTK which is a "widget GUI interface" connected with Windows 9x? Or with WINE? jaclaz

Yes and no, meaning that - for whatever reasons - that is the first localized version that survived, a NL 3.80 version actually existed: https://web.archive.org/web/20090228151900/http://www.winrar.nl/ https://web.archive.org/web/20081216004617/http://www.rarlab.com/download.htm And, as Trip stated the Wayback Machine didn't archive the file. I wonder if plainly asking winrar.nl via info@winrar.nl for a copy wouldn't be feasible. jaclaz

Myabe you are looking for FTP SYNC programs, or better for folder synchronization programs with FTP access. Examples (not necessarily doing what you want to do, and doing it the way you want to do it): https://freefilesync.org/ https://winscp.net/ http://www.beanland.net.au/AutoVer/ https://fullsync.sourceforge.io/ https://www.2brightsparks.com/syncback/compare.html jaclaz

Only a word of warning, at least historically, imagex (and by extension similarly working programs) are not entirely valid backup solutions: https://support.microsoft.com/en-us/help/935467/you-cannot-use-the-imagex-exe-tool-as-a-backup-tool-for-a-windows-comp jaclaz

Yep, now the MBR is the right file , here is the partition table: Entry Type Boot bCyl bHead bSect eCyl eHead eSec StartSector NumSectors #0 05 00 0 1 2 1023 254 63 64 167927381 #1 06 00 1023 47 49 1023 254 63 167927808 176652 #2 07 80 1023 59 61 1023 254 63 168105984 808662079 #3 00 00 0 0 0 0 0 0 0 0 As said the only possible issue is the type of the partition #1 which is now 0x06 but that could be either 0x06 (with the drive letter not assigned to it in Disk Manager) or 0x0DE (or other "hidden" type of partition). But as said if you actually need to access that DELL partition and it doesn't work you can always try to change the ID at the time you will actually need to use it (if you will ever need to use it). The partition offsets (StartSector) are a bit "queer", but nothing to actually worry about, the only thing that I would NOT dare to do (but that you have not ANY reason to ever do it, so it is only a hypothetical problem in theory) would be to change the active (Boot) status of the partition with XP Disk Management, as it is known to do "queer" things to the Extended partition (and volumes in it) when it finds "queer" values, but nothing to worry about in normal operation of the PC. All in all I would leave everything "as is". jaclaz

Good , so the "hidden" volumes inside Extended are (let's say conventionally) "normal", no, wait , let's call them completely abnormal but expected. Back to the MBR. I don't know what you are doing/did but the two files you posted are EXACTLY the SAME and BOTH are NOT the MBR (they are both the bootsector of volume C:\). Very likely you made some confusion either in reading them or saving them. I need the MBR, that is 1st sector of PhysicalDrive 0. Even in the (I know, confusing) view that HdHacker provides, in BOTH the files you posted you can easily read at the begining ".R|NTFS" and then "NTLDR" a couple of times and near the end "Press Ctrl+Alt+Del to restart", the file I need is likely (if it is the standard XP MBR) to begin with "3." and have near the end "Invalid Partition Table.Error loading operating system,Missing operating system," If you follow EXACTLY my previous instructions you cannot get the bootsector of drive C: Anyway, if you are OK with the current status, let it be. Normally (but it depends on the model, and the way the good DELL guys configured it) having the partition ID set to 0xDE is needed to use its contents the way they are intended, but it is entirely possible in your specific case that the current partition ID (either 0x06 or 0x0E) is fine and even originally it was simply removed from the drive letter assignment pool. The question (to answer wich the "old" disk MBR is also needed to make a comparison) is if what Macrium calls "Fix Windows Boot Problem" actually does, as three things are possible: 1) it simply deletes the MountedDevices key in the Registry (this way the hive will be re-populated by Windows at next boot, taking into consideration the new Disk Signature) [1] 2) it restores the original Disk Signature [2] and doesn't touch the Registry 3) does - additionally to either 1 or 2 above - some automagic changes on the MBR partition ID's [1] jaclaz [1] and then the disk is not anymore a "clone" [2] and then the disk may be a "clone"

That is a DELL utility partition. Your (only) system and boot volume is seemingly the C:\. Anyway you have (why) an extended partition (before the D: and C: volumes) containing two logical volumes with an unknown tag. Maybe after all Macrium didn't do very good work (or maybe the source hybrid drive was a mess to begin with?). The MBR is a Master Boot Record, and it is stored on the first absolute sector of the disk (or LBA 0). It is made of four relevant parts: 1) boot code (that is executed by the BIOS when you boot) 2) Disk Signature (on NT based systems which is what Macrium fixed under the generic "Fix Windows Boot Problem") 3) the Partition Table, consisting of 4 entries, 16 bytes each, each one being able to contain the addresses of up to 4 primary partitions or up to 3 primary partitions and 1 Extended partition (this latter can contain more than one logical volumes) 4) the "Magic Bytes" 0xAA55 Now, entering the details of item #3 above, each partition entry is composed of 4 fields: f1) Partition ID (this indicates to the OS which type of partition is the entry relative to, an extended is either 0x05 or 0x0F, Primary volumes have an ID that usually corresponds to the filesystem applied to the volume f2) CHS start adrress values (in Cylinder/Head/Sectors) f3)CHS end address values (in Cylinder/Head/Sectors) f4) LBA start address value (in sectors) f5) LBA extension value (in sectors) Now, normally a DELL Utility partition like the one you have is a small FAT 16 volume, and such a a FAT 16 volume has normally a partition ID of either 0x06 or 0x0E, BUT many OEM change the partition ID for their recover/utility volumes to an ID that the OS would consider "hidden" and thus refrain from assigning a drive letter to it (i.e. the volume is not mounted/visible in Explorer). DELL uses normally for these partitions the 0xDE partition ID. It is entirely possible that Macrium, while doing what it calls "cloning" or while doing what it calls "Fix Windows Boot Problem", decided that the volume after all was a plain FAT 16 one and changed the ID back to either 0x06 or 0x0E. Fixing this is simple and can be done in no time, What is perplexing is the extended partition containing: 1) a 78 MB FAT volume 2) a 80 GB NTFS volume without any drive letter assigned to them Only you can say if this is "normal" (it is entirely possible that the 80 GB . In theory you should: 1) switch off the PC 2) remove the new hard disk 3) re-attach the old hybrid hard disk 4) boot the PC from it 5) take a screenshot of disk manager corresponding to the one you just posted Since views on the disk manager are not "exact" data, you should make a direct copy of the MBR when booted from the old hard disk, then reverse the procedure, detaching the old hard disk and re-attaching the new one, etc. IT IS VITAL THAT THE TWO CLONED HARD DISKS ARE NEVER CONNECTED AT THE SAME TIME TO A PC RUNNING A NT BASED SYSTEM as this will create a Disk SIgnature conflict and the NT OS will silently change the Disk Signature of one of the two devices. To make the copy of the MBR use this simple tool, HdHacker: http://dimio.altervista.org/eng/ You want to choose "Physycal Drive (MBR)" (and 0 in the dropdown on the right, should appear automatically) and below "First sector (MBR)". leave "number of contiguous number of sectors to read" set to 1 then "Read sector from disk" then "Save sector to file" Save them as oldhd.mbr and newhd.mbr to a USB stick (so that you can connect it to the PB both when the old hard disk is in and later when the new hard disk is in the PC), then compress them together in a .zip file and attach the archive file to your next post or upload it *somewhere and provide a link to it. jaclaz

Well it is not that difficult to experiment manually. Just use a "normal" format command (without applying a label). See what comes out by default. Then (if needed) increase the Reserved Sectors value (in the bootsector). Then (if needed) increase the FAT size (again in the bootsector) . Then copy the first sector of the first FAT to the shifted beginning. (or just write F8 FF FF 0F FF FF FF FF FF FF FF 0F to the shifted first sector) Unmount and remount. Run CHKDISK /F on the volume, reply no to saving lost chains. As a side note, and curiously enough, the backup bootsector is not updated by running CHKDSK, but the second FAT table is alright. Quick experiment with an IMDISK volume 50 MB in size: BEFORE: Changed with Tiny Hexer (only "random" changes without any calculation behind): Reserved sectors 32 -> 34 Fat Size 788->800 And written F8 FF FF 0F FF FF FF FF FF FF FF 0F to sector LBA 34 Unmounted and re-mounted, AFTER: jaclaz

I love standards, there are so many of them ... jaclaz