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

    410
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

4 Neutral

About bizzybody

Profile Information

  • OS
    Windows 10 x64
  • Country

Recent Profile Visitors

974 profile views
  1. 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.
  2. 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.
  3. 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.
  4. 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
  5. 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.
  6. 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.
  7. 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
  8. 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.
  9. 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.
  10. 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.
  11. Ctrl+Shift+8 shows the paragraph marks, a centered dot in every space and right pointing arrows for the tabs. Nothing else. Today I edited the copy I had finally been able to get to print properly Yesterday. The O's were back, along with some U's. I finally resorted to just having the text at the bottom bold instead of bold and italic. Other text on the page is bold and italic without the problem, it's all the same font and all the same size.
  12. I have some documents in RTF, created in Word 2003. Recently, in parts of the document that have not been changed since the original was created, Word 2003 has decided all the spaces should be printed as capital O, but with the same width as a space so the O's overlap the characters to either side. I tried printing the document from WordPad in Windows 10. It printed the O's *and* added in some lowercase l's and in a couple of lines a larger number of overlapping 6's. In WordPad I deleted all those spaces and re-typed them. Printed again and the l's and 6's were gone but the block with the O's still had them. Back to Word 2003. I deleted the bad section and retyped it completely, then applied the bold and italic. When printed the O's were still there instead of spaces. HOW?! I copied and pasted the text to Notepad then back. Re-applied bold and italic and print, still the O's are there. Last thing I did was copy to notepad then did Paste Special *without unicode*. Printed and... O's are gone BUT now the document prints two pages, though only one is visible, and the second page has the O's. I printed it, happy to see it *correct*, then two seconds later "WTH is the printer doing?" and out comes the second, wrong copy. It's not the printer, a LaserJet 4100DTN. I've used it for years, with XP, 7 and now 10. Once in a while since upgrading to 10 it would print those O's but immediately printing a second time they'd be gone. But today Word has put them in there *every time*. How can I clean up this document, and the hundreds of earlier ones that are edited versions of the same document going back to 2011? Is there a program that can strip out everything that's not required to have the text print exactly as it shows?
  13. I have a Dell XPS-M140 laptop which originally shipped with XP Media Center Pro SP2. Some prior owner deleted the MediaDirect 2.0 partition and seriously boogered the Windows install - which had the bug of reporting itself as 2002 among others. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center The ident value is 3.0 for 2005 but properties says 2002. So I'm attempting to do a clean install of MCE 2005 off a 2005 SP2 CD - properties shows 2002. WTH? Trying to install the WindowsXPMediaCenter2005-KB900325-usa.exe fails. Fail here, there, everywhere. Faugh! I'd like to make a slipstreamed MCE 2005 SP3 disc, even if it has to bloat up to be a DVD, so that it'll be a one and done all up to date, reporting its proper version. I'd also love to be able to restore MediaDirect 2 but I can only find 3 or later. Making the MediaDirect button do something like launching Media Center or PotPlayer would be a useful substitute. Or how about an unofficial updater that takes the MCE updates and SP3 plus whatever other updates (found and downloaded like how Autopatcher does so it's not redistributing MS software) are needed then forcibly installs it all, replacing the files and registry information with the latest, working ones. Don't try to be 'nice' to the installed XP, just hammer it in like a 10lb sledge on a railroad spike and make it work.
  14. An issue with code blocks.

    When I put text between the code tags then go to edit after posting. I cannot, highlight, edit or change it in any way. It's inside a box with a little widget at the upper left corner and I can drag that, which moves that text as though it's an image.
  15. An issue with code blocks.

    It is an image when I go to edit the post. Having to disable scripting to make it work properly, to allow keeping text posted below a code block, is a bug not a feature, especially when there are web sites that depend on scripting and use it properly.
×