Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×


  • Posts

  • Joined

  • Last visited

  • Donations

  • Country

    United States

About bizzybody

Profile Information

  • OS
    Windows 10 x64

Recent Profile Visitors

3,267 profile views

bizzybody's Achievements



  1. Mostly when I build a new PC or do a major upgrade, or when there's an all new Windows version. I have in the past migrated a Windows install to completely different computers but that pretty much ended with XP. In the 1990's I migrated a Windows 95a install to five completely different PCs. I'd have all the drivers for the new (or new to me) hardware, then in Device Manager I'd uninstall everything it would allow, then shut down. Move the hard drive to the new computer and boot up. Then install the new drivers and it was good to go. It was also far far easier to migrate 9x to a new hard drive. Basically it involved moving the swap file to the root then copying and pasting all the drive contents except for the swap file and a couple of others in the drive root. Swap the new drive in place of the old, boot up and all would work. But that 95a transplant series came to a halt when by crazy coincidence it got one character corrupted in the Registry that caused the weirdest behavior I have ever seen in any version of Windows. In Explorer I could single left click on three folders or files, one after another and it would crash Explorer. This was made especially annoying because the corruption somehow happened the instant I changed the default Critical Stop error sound to a breaking glass effect. No Registry tools I tried could fix the error. Regedit would not allow the corrupted entry to be deleted. Doing the command prompt Registry export and re-import to purge unused information would fail. I even reinstalled Windows over itself, which in 95 would bulldoze over many problems by replacing them with the default files, leaving most installed software working. But not that one, the corrupted entry happened to be one that an install over itself didn't over write. (Doing this with Win98 was mostly futile because it preserved much more than 95 when installing over itself.) So I found a 3rd party file manager that allowed for copying off all the files I didn't want to lose so I could do a clean install.
  2. Windows 10 builds after 1607 no longer support older methods of driver signing, just the latest that was introduced with Windows 8. What happens is that when the driver installer is run, Windows allows it to go through the motions but silently blocks copying the files and making changes to the Registry. If you extract the driver and attempt to install through Device Manager, you'll get an unable to find file "error". So on an old computer, especially a laptop, what you do is do a clean install of 1607 and get all the drivers installed. Then make an image backup. Your next stop is updating to 1903 or 1909. Why? Because 2004 and 20H2 won't update 1803 or earlier. The installer will flat out lie and say all is well, go through the whole setup, then fail with a bogus "error" about PC Settings or something, then roll back. A bit of searching online revealed the issue was requiring 1903 or later, which the 2004 and newer setups should have been programmed to detect and tell the user at the beginning. After you get 1903 or 1909 (I recommend 1909) installed, make another image backup. Now try installing 20H2, with internet access so it can download needed updates during install. If by now it's still not working on some computers it probably will never work on them. If 20H2 doesn't work, try 2004, then 20H2 again. I had to wait quite a while before it would update 2004 on my Dell laptop. Got 20H2 on it? Make another image backup. These image backups will save you hours the next time you need to do a clean install. Keep the 1607 image in case you need to install some more hardware that newer builds won't allow the drivers to install. The main issue seems to be with older video drivers, especially for discreet GPUs in laptops.
  3. What do I need to do to make a live bootable Windows 7 Pro x64 USB stick so I can run gatherosstate.exe ? Why? To save all the time installing Windows 7 Pro x64 just to run that executable once, copy the generated file off the computer then wipe it and install Win 10.
  4. Oh but you can have FAT32 on drives smaller than 512 meg, if you know the secret switch commands. I was working at a computer shop when Windows 95 OSR2 was released. When we'd get enough parts leftover from upgrades I'd put together the best box I could, using whatever was handy for a hard drive large enough to hold a Windows install. I'd use the trick to force FDISK to set it up for FAT32 then do the install. FDISK /FPRMT Then when someone came in looking for a decent yet cheap computer, I could show them one ready to go, at X price. Would just have to order a bigger hard drive to get it ready. When the bigger drive would come in I just had to copy Windows over. Made it easier to move a lot of older but still useful hardware. With any version of Windows 95 it was super simple to hook up another drive and copy everything without needing any 3rd party drive copying software. I remember the main thing was changing the swap file location to the root of C: so everything except that could be selected. Format and Sys the new drive. Copy everything in the root director over first, except the swap file and command.com. Then select everything else and copy it over. Pretty sure that's how it went. I used to have a step by step guide I'd send to people asking what the best drive copying sofware was. Answer: Windows Explorer!
  5. Years ago, back in the ancient days of Windows 95a, I had an install I'd moved through at least four completely different PCs, with numerous incremental hardware upgrades in between. Never a problem. I'd delete everything it would allow to be deleted from Device Manager, then shut down and move the drive to the new system. (I'd also figured out how easy it is to move Windows 95 and all installed programs to a different drive without any fancy 3rd party programs.) After getting Windows settled in its new home with all the device drivers installed, I'd do a Registry export and re-import to ensure all the cruft was gone. (If only that could be done with XP and later!) I had a PC with an AMD 5x86, wire modded to run at 4x 40Mhz. Solid as a rock, and running perfectly fine on 5 volts after replacing a 33Mhz 486SX. It also had a 1x Mitsumi CD-ROM, the type where the whole mechanism slid out and had a lift up clamshell lid. (Surprisingly it could read CD-R despite being made years before CD-R existed.) It had been quite a while on that box without any problems. I decided I wanted to change the Critical Stop sound to a breaking glass effect. Right after I changed that is when the crashing started. I could not do *anything* in Explorer. After clicking three things in a row in Explorer *CRASH*. Click to open a folder, click a subfolder, click a file *CRASH*. Click on three drives in a row *CRASH*. It was like a Waltz "One, Two, Three *CRASH* One, Two, Three *CRASH*". It only affected using Explorer when attempting to do anything to manage files. I could surf the web, do e-mail, everything else was fine, except for changing Windows Sounds, since that also involved accessing Explorer to find a different sound file, thus that would make it crash too. I became immensely annoyed with that sound effect after hearing it a large number of times. I forget what all I tried to fix it. I do remember trying to export the valid data from the Registry but that failed. That helped me track down the problem. One corrupted character in one key in the Registry. Why it manifested in that perfectly repeatable, totally not random way to make it crash, I've no idea. It wouldn't allow me to delete that Registry key because it was corrupted and unreadable. I dug around the web to find some way of saving things and found the final version of Norton Commander for Windows. Apparently it was abandoned, unreleased, and not quite finished. But I was able to use it to copy everything I wanted to save to another partition so I could "Nuke and Pave" C: and do a fresh install of Windows. That's long been a problem with Windows and corrupted files, folders etc. It fiercely protects them like a mother bear protects her cubs - when what it should do is delete the bad things, or at least allow the user to delete them. Scandisk should terminate corrupted data with extreme prejudice. Before Unlocker (which hasn't been updated in ages yet still works in Win 10 1809) the only recourse I could find for a corrupted file or folder that would make Windows insist on doing a full scandisk *every boot* then complaining about the corruption (and failing to fix it) was to copy important files, then reformat the drive and do a clean install. Even with Unlocker, if that couldn't forcibly delete the bad file or folder, Nuke and Pave.
  6. I just tried installing FreeDOS 1.2 Lite from a 512 meg USB drive onto a WYSE S30. Result? Failure. It boots and launches the setup. First is says there's no fixed disk, then is says drive D: is not partitioned. So I have it partition and reboot. Repeats this exactly the same. The BIOS *does* prevent some critical access to the IDE when booted from USB or when attempting to boot an OS from the IDE, except when using an OS and BIOS updater from USB or an OS from the IDE that came from WYSE. The workaround at the bottom of this page will have to be implemented in FreeDOS in order to install it from USB. http://www.parkytowers.me.uk/thin/wyse/s10/Linux.shtml Edit: I found an "MS-DOS 7.1" boot floppy image and *this one* had no problems booting the S30 with a USB floppy drive, wiping the DOM and creating a fresh partition with FDISK, then rebooting and using format c: /s NOW it's booted to a DOS prompt from the DOM. So I'll try FreeDOS again...... Nope. Same as before. Screen full of No Fixed disks present, followed by a prompt to repartition D:, but it cannot touch it.
  7. And it doesn't work. It blocks MS-DOS from booting from IDE. I have an old FreeDOS image someone made for these thin clients, it boots, but everything is in French.
  8. Clonedisk x64's RAW image worked. Since there doesn't appear to be any up to date QEMU front ends for Windows, I used the old QEMU Manager 7.0 that comes with an older version of QEMU. I was able to install DOS to the RAW image then use Clonedisk to write it back to the Apacer DOM. Now I just need to configure the autoexect.bat and config.sys files, plug it into the S30 and see if it'll work.
  9. OK, used Clonedisk to make an image. Glory be, a Windows utility that actually uses a GUI. Point, click, done. The way Xerox intended... Got QEMU for Windows x64 downloaded and installed. Will work on this some more tomorrow. Two reasons for fiddling with DOS on these old WYSE Sx0 thin clients. Main one is to have a tiny box for running the old DOS control software for a PLM2000 benchtop CNC milling machine. That will need the USB to work, I have the Panasonic universal USB drivers for DOS. All it needs to run the mill is one RS232C port, which the WYSE Sx0 series has. USB will only be for loading G-Code files. USB keyboard support is in BIOS, other than the serial port these are Legacy Free. Secondary is setting one up as a tiny retrogame machine. The ethernet should work since it's a common Realtek chip for which there are DOS drivers. The sound is the iffy bit. Only VIA released AC97 DOS drivers. If their drivers and the chip WYSE used both were made strictly to the AC97 standard, the drivers may work with it. If that works, hello wee little DOOM machine. With up to 512meg DDR1 RAM and DOM's available from 64 meg to 8 gig, and the System On Chip faster than most 90's PCs, it should do well - if the sound will work. I don't think the SOC does MMX but what DOS software uses that? They're powerful enough to run normal Win 9x through XP but the swap file would soon destroy the DOM's chips. Would have to fit in some more durable type of storage. Going to be some fun digging 25~30+ years ago DOS knowledge out of my head to setup the startup stuff. I used to have the perfect setup memorized. I hope after all this the thin client has a sane memory map that will allow room for loading as much as possible high, and for XMS or EMS emulation to provide space for large G-Code files. I tried an old laptop but laptop memory maps post 1994 are a fragmented mess with nowhere large enough for an EMS window. Simply cannot setup any DOS on them for doing stuff like running games that use a DOS extender.
  10. I need to make a full image of a 64 megabyte IDE Disk On Module and have it work with DOSbox or some other DOS or PC emulator that can run DOS. I also need to be able to write the image back to the DOM so it can boot the thin client it's normally installed in. All I need to do to the DOM or an image of it is run FORMAT /S with the DOS that will be run from it. Then I can copy everything else to the DOM from within Windows, plug it back into the thin client and finish setting up everything from there. I tried an uncompressed, full sector image with Macrium Reflect. DOSbox won't use that, can't get CHS info from the image. If WYSE hadn't been so 'clever' with their BIOS I could simply make a bootable USB from Windows and boot the thin client from it and install DOS. But noooo, they had to put in a roadblock. It can be worked around, this guy did it with a linux kernel patch. Should be possible to write a little DOS program to do the same hack, but I'm not a programmer. http://www.parkytowers.me.uk/thin/wyse/s10/Linux.shtml
  11. I've made sure there's nothing on it I need to save and have used EaseUS to delete the partition and create a new, supposedly optimized for SSD, NTFS partition with no unallocated space before or after. Write performance is absolutely horrible, was before. It gets a short initial burst of 13 MB/sec then drops to ZERO for a while, then jumps up and down between zero to 3~4 MB/sec. I've also tried using AOMEI, no difference. Using EaseUS on an 8gig Lexar (the model with the e-paper bargraph) I was able to get 10+ MB/sec write speeds. Using Windows own formatting it cut the write speeds to 6 MB/sec or less. With the 64gig it doesn't seem to make any difference in write speed. Could be that Lexar just makes some real crap USB drives.
  12. The people in charge of the Web Archive made the (IMHO rather stupid) decision that the mere presence of a robots.txt file should prevent their archiving spider from downloading anything else in the directory containing the robots.txt file, or anything in all paths below it. Nevermind that in many cases a robots.txt contains explicit permission for archiving - which many of the archived robots.txt files in the Web Archive do. What they should have done was code their spider to *read* the robots.txt files to see if they contained permission for archiving.
  13. I can copy everything off that I don't have elsewhere (if there's anything like that) and reformat it or whatever is needed to have it as NTFS and working with XP and later. Has to be NTFS so I can put big files on it like videos and large disk images.
  14. Now with more data on it, my XP laptop is corrupting whatever its getting corrupted. I took it to my friend's computer to get it hit again. Brought it home, plugged it into my Win 7 laptop, needs scanned (I didn't) but it can still read it. So can 10. Plugged it into my XP, used dsfo. Plugged it into 10, scan and fix. Plug back into my XP then back into 10. Corrupted. Good, for certain values of good. Scanned and fixed again. (If there's 'no errors' then why should it need scanned and repaired?) Then used an elevated command prompt to pull the good file with dsfo. Hopefully these will tell you something, and what needs done to make the stick work again with XP. dsfok.zip
  15. It's not a fake size. Copied a 2.1 gig video to it, up to 17.3 gig used. That one plays all the way through.

  • Create New...