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. ×

bizzybody

Member
  • Content Count

    416
  • Joined

  • Last visited

  • Donations

    $0.00 

Community Reputation

4 Neutral

About bizzybody

Profile Information

  • OS
    Windows 10 x64

Recent Profile Visitors

3,145 profile views
  1. 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.
  2. 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 g
  3. 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 ensur
  4. 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
  5. 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.
  6. 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.
  7. 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
  8. 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 th
  9. 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
  10. 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.
  11. 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.
  12. 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 thes
  13. 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.
  14. It's a genuine Lexar LJDTT64G-000-116 like this https://www.geeksstore.com/Products/LJDTT64G-000-116 The XP machine that screws it up isn't at my place. The XP laptop I have just insists it's bad, without making an improper alteration. So probably tomorrow I'll go get it zorched again then use the XP laptop to get samples of it screwed up, followed by using the Win 7 laptop to fix it and take samples - since XP flat out refuses to recognize that there's actually nothing wrong with the drive. It'll be interesting to find out what's going on with the computer screwing it up. Mostly of
  15. I plugged the USB drive again into the XP computer that corrupts it. Brought it home and verified that my Win 10 system cannot read it. 10 does not allow HDhacker to run without disabling SmartScreen, then refuses to allow it any access. I got out an old laptop with XP and used it to use HDhacker to get the first 16 sectors. Then I plugged the drive into the W10 system to scan it. (Results pasted below.) After repairing it I plugged it into the XP laptop, can't read it, claims it's bad, refuses to scan it. So I plug it back into Win10 and it's NOT corrupted. Whatever is damaging it seems
×
×
  • Create New...