Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


bizzybody

Member
  • Content Count

    415
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

4 Neutral

About bizzybody

Profile Information

  • OS
    Windows 10 x64
  • Country

Recent Profile Visitors

1,863 profile views
  1. bizzybody

    Making a disk image in Windows 10

    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.
  2. bizzybody

    Making a disk image in Windows 10

    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.
  3. bizzybody

    Making a disk image in Windows 10

    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.
  4. bizzybody

    Making a disk image in Windows 10

    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.
  5. bizzybody

    Making a disk image in Windows 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
  6. 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.
  7. 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.
  8. 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.
  9. 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
  10. 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.
  11. 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 academic interest because that computer has been upgraded with a dual core AM2 CPU and 4 gigs RAM and will soon be getting 64bit Win7 so it can take full advantage of that. Aside from that, there is the interest in finding out what has become objectionable to XP about the drive when it worked before with less data on it. The last big file I copied to it plays just fine all the way through - just not on XP. I'm hesitant to delete it and see if XP suddenly likes the drive again - before discovering what XP's problem is with it. Would be even more puzzling if deleting the file then copying it back made the problem mysteriously go away.
  12. 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 to be specific to the other XP system. Final step, I got out another old laptop with Windows 7 and verified it can read the USB drive then copied the first 16 sectors with HDhacker. Both copies are in the attached ZIP, bad and good. What I haven't done is alter the contents of the USB drive since it seems to be somehow connected to the amount of data on it, due to XP having previously had zero issues with the drive until it approached 16 gigs. 16,436,596,736 bytes. Chkdsk log from Windows 10. Checking file system on I: Volume label is BigLexar. Stage 1: Examining basic file system structure ... 1792 file records processed. File verification completed. 0 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 2466 index entries processed. Index verification completed. Stage 3: Examining security descriptors ... Security descriptor verification completed. 338 data files processed. CHKDSK is verifying Usn Journal... 595824 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 62516223 KB total disk space. 15883080 KB in 1042 files. 480 KB in 339 indexes. 70671 KB in use by the system. 65536 KB occupied by the log file. 46561992 KB available on disk. 4096 bytes in each allocation unit. 15629055 total allocation units on disk. 11640498 allocation units available on disk. 000700007105000035090000000000000E000000000000000000000000000000 Binary data: In Words 0000: 00000700 00000571 00000935 00000000 0010: 0000000E 00000000 00000000 00000000 In Bytes 0000: 00 07 00 00 71 05 00 00 ....q... 0008: 35 09 00 00 00 00 00 00 5....... 0010: 0E 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ Lexar-XP-corrupts.zip
  13. I have a Lexar 64gig USB drive that until a couple of days ago it had no problem at all with. It's formatted NTFS. Two days ago I copied an 806 meg file to the drive, pushing the used space up to a bit over 15.3 gig. When I plug it into the XP system it instantly corrupts the drive. Properties shows 0 bytes used, 0 bytes free. Disk Management shows it as empty, active, RAW and healthy. I never made it Active, have never used it as a boot device. When I plug it into a Windows 10 system, it says there's a problem and it needs to be scanned. I scan it and have it fix, but it says there's nothing wrong. However, if I skip the scan Win 10 won't show the contents until I do the scan. XP flat out will not let me try to scan it for errors. Is there some patch for XP that'll fix this? It's not online, only used to play some old games and runs Potplayer connected to a big television for videos.
  14. bizzybody

    Port WINE to Windows?

    I've run 10 x64 on a 2.5 Ghz Core 2 Duo with 4 gig. Runs better than 7. 10 is the first version of Windows to have lower minimum system requirements than the previous version, and from all the computers I've put it on, it looks like they really mean it. Still, I wouldn't want to try 10 on something like a Toshiba Satellite L35 with a max of 2 gig and a 1.6 Ghz Celeron M 420. "Vista Capable" my backside, especially with the 1 gig it currently has, especially when its ATi GPU doesn't have dedicated RAM. XP with less than a gig was bad enough. Some lighter weight Linux Distro and OpenOffice are likely in its near future.
  15. bizzybody

    Port WINE to Windows?

    If you're running a Kaby Lake or AMD's just released Ryzen, Microsoft has announced "No updates for you!" if you're running Windows 7 through 8.1. Whatever happened to supported through 2020 for 7? There are a lot of fairly decent computers out there, especially laptops, that shipped with Vista. Many of them only have 2 gigs RAM and (especially the laptops) many of those have Celerons, a lot of Core Solo Celerons. They can run Windows 10 surprisingly well, especially 32bit. But 7? Noooo. They choke on 7. A software package to make software that "requires" 7 or later run on Vista would get a bit more life out of older yet still serviceable computers.
×