Jump to content

jaclaz

Member
  • Posts

    21,300
  • Joined

  • Last visited

  • Days Won

    53
  • Donations

    0.00 USD 
  • Country

    Italy

Everything posted by jaclaz

  1. Good. Though to me it is already a miracle that the dropbox location actually allowed you to get up to that point. But your first point was valid, I don't think anyone else ever had this specific issue, as I never heard of anyone attempting to use files in a dropbox storage for this kind of use. jaclaz
  2. Noone said the contrary of that. Just in case: https://www.robvanderwoude.com/redirection.php jaclaz
  3. I see , it is a really old model (but SLC) that has no support for trim in the internal processor/controller. Yes, you can't do more than what WinClient5270 suggested, but it is included among the models supported by the: https://downloadcenter.intel.com/download/29205/Intel-Solid-State-Drive-Toolbox cdob pointed you too, so maybe it is worth the time to check what it can do. jaclaz
  4. I prefer "accurate". jaclaz
  5. You mean late-observant of course, if you were un-observant, you wouldn't have noticed ... jaclaz
  6. That error - basically - means that the BCD is "in use". No way to know from a distance WHAT is using it and keeping it "locked". Try again after a fresh reboot. If it still doesn't work, it should mean that you have *something* (it could be an antivirus, another "security" program, *whatever*) locks it at boot or when you run the WinntSetupFromUSB. If this is the case (and even if it isn't, you can get unlocker: http://www.emptyloop.com/unlocker/ and hopefully_ 1) understand what program/process locks it 2) unlock it manually jaclaz
  7. Good. Due to the way the files are made by the program, new additions (players) will be added at the end of the batters and pitchers files, thus the index/address file will become again not-sequential (even if only in the last part), and you will need - before or later - to re-run the scripts to re-compact it. jaclaz
  8. @MrMADRYAN Post the specific make/model of this SSD. jaclaz
  9. Hmmm. https://web.archive.org/web/20181225133300/https://msfn.org/board/ <- No dice https://web.archive.org/web/20171225070707/http://www.msfn.org:80/board <- No dice https://web.archive.org/web/20161228040343/http://www.msfn.org:80/board/ <- No dice https://web.archive.org/web/20151221233156/http://www.msfn.org:80/board <- Here it is in all its beauty jaclaz
  10. Well you can trim on Vista just fine (manually), if it is possible on XP, it should be also on Vista: The point might be is wherther the specific SSD is "recognized" by available software. jaclaz
  11. Well, redirection is for the output of a command, not for the command itself. Try running this: @SETLOCAL SET MyNum1=1 SET MyNum2=2 >NUL SET MyNum SET MyNum>NUL @ECHO. @ECHO Here start the @ @SET MyNum1=1 @SET MyNum2=2 @SET MyNum @SET MyNum>NUL jaclaz
  12. Not really. You shouldn't redirect to NUL when you can "hide" that output by simply adding a "@" before that line. jaclaz
  13. Sure , and now - through a moderate use of torture - I managed to have you document that reason. Sure it is a personal opinion, though exceptionally the fact that a number of drivers (most?) have the same file name for both architecture is not a (valid) reason, particularly if coming from someone that had the sensibility (and good idea) of renaming the drivers to avoid the possible update issue. Anyway my congratulations to you both for the idea/finding and for the mods that allow the use on Win2K. jaclaz
  14. Given the "delims=<>:/|?*", what happens if the last character is a delimiter? I.e.: DIP=dfhkasldfjjalsdkj| or DIP=dfhkasldfjjalsdkj? About the "fun" code, some of the things that may happen can - as you did - be explained, some other things of what happens in batch has no real *rational reason* or explanation, some are quirks, and you need to learn to live with them. Rob van der Woude has a few pages documenting "strange" or "unexpected" things that may happen in batch (and how you can in some cases take advantage of those): https://www.robvanderwoude.com/altmsdosbatch.php https://www.robvanderwoude.com/useless.php https://www.robvanderwoude.com/clevertricks.php jaclaz
  15. Well, in the meantime I checked, and seemingly you didn't change the .sys contents, but changed the .sys name (or at least I was able to find the same binaries in a supposedly original Asmedia driver set), then the 64 bit .dll is unchnaged but renamed, while the 32 bit .dll you patched/modified. If I may, not the smartest of the ideas to call the 32 bit and 64 bit drivers the same . I am attaching the original drivers (together with a copy of your drivers in a more convenient .zip format and with a filename slightly more readable than "f45t5753p100543n2_dQJtNfwo.rar" ) because - set apart the name change - it seems to me interesting for learning about the .inf and .oem changes you made . jaclaz ASM106x_ori_XP_sata_drivers.zip danielk_ASM106x_mod_XP_sata_drivers.zip
  16. If suggestions are open, what about "The Nameless Browser" (TNB for short) which is accurate and vaguely reminds of H.P. Lovecraft : https://en.wikipedia.org/wiki/The_Nameless_City jaclaz
  17. Is it modified or unmodified? Only for the record, I had to get unrar because it is compressed in a format that my 7-zip (of course dated) doesn't understand. A .7z or even better a .zip would be nicer (next time). particularly if the thingy is intended for 2K/XP users. jaclaz
  18. Personally I would go for the PS2 keyboard. The USB 2.0 pci card (while a nice idea ) seems to me something that would be worth the time of an experiment, but there is a concrete risk that the install will fail, or - if you prefer - PS2 keyboard surely works, your USB 2.0 PCI card may. jaclaz
  19. Anyway someone that took the pains to instal Win9x to a logical volume already should know that some issues may come with it. Just in case, good ol' XOSL FAQ's contain some good information about this (and various other "old OS" knowledge that is little by little being forgotten): http://www2.arnes.si/~fkomar/xosl.org/faqhow/faq.html jaclaz
  20. Ok, I see where the issue arises from. I needed the Tomorrow and Naturally is on first as placeholders (to get the numbering right in the ADDRESS file) but they shouldn't be written to the actual Pitchers and Batters files, that are seemingly written sequentially without "gaps". So it is just a matter of putting an IF condition in the N column of the spreadsheet and regenerate the files, though now fsz it is also needed to add the 00 bytes at the end of the Batters and Pitchers file to match the original "total size". Try the new attachment. jaclaz Trip_Baseball_2.7z
  21. Try adding the FullName : https://www.windowscentral.com/how-add-your-full-name-local-account-windows-10 EDIT: found where I read about the issue: https://answers.microsoft.com/en-us/windows/forum/all/windows-10-1903-login-screen/ce270499-fa3f-4c6c-9e50-bdf852f05501 jaclaz
  22. Cannot say what you want to do. I can suggest you to simply acknowledge that "modern" Windows built-in search tools are a lost cause and use a replacement. Namely (if you only have NTFS volumes) SwiftSearch or Everything: https://sourceforge.net/projects/swiftsearch/?source=dlp https://www.voidtools.com/ jaclaz
  23. Why? in-situ (when it works) virtualizes the MBR, creating a new one with just the entry/partition/volume you mapped. ****************************************************************************** *** About the new map option --in-situ *** ****************************************************************************** --in-situ is used with hard drive images or hardrive partitions. With an in-situ map, we can typically use a logical partition as a primary partition. In-situ map is a whole drive map. It only virtualize the partition table and the number of hidden sectors in the BPB of the DOS Boot Record. While disk emulation may encounter various problems with win9x, the in-situ map works fine with win9x. Note that --in-situ will not change the real partition table. Example: map --in-situ (hd0,4)+1 (hd0) jaclaz
  24. Check the "full name" against "user name". I have seen reports where the issue was created by having a "user name" different from "full name". Open a cmd window, in it run: wmic useraccount get /format:list or, if you want to better review the list: wmic useraccount get /format:list>C:\myaccounts.txt jaclaz
×
×
  • Create New...