Jump to content

jinjou

Member
  • Posts

    18
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About jinjou

  • Birthday 03/29/1957

Profile Information

  • OS
    Windows 2000 Professional

jinjou's Achievements

0

Reputation

  1. Since you suggest you're only experimenting, is there any reason why you wouldn't use a virtual machine?
  2. I haven't tried it on 2K yet, but this link is to a 2K version. 7-Zip wouldn't open it, and Vista x64 reports that it won't work on WinNT 5.01 or later.
  3. You don't say where settings.bat is located, and that appears to be what this question's answer would depend on. You should either include the fully qualified path to settings.bat in CMDLINES.txt, wherever you choose to locate settings.bat, or put settings.bat in the same location as CMDLINES.txt. I've only tested this with W2K using the full path alternative in CMDLINES.txt, and then placed settings.bat some place on the %SystemDrive% using the $OEM$ folder arrangement mechanism. I should think this will work with XP as well. BTW, I'd be suprised to learn that environmental variables work, they haven't for me, so I'd recommend explicit, literal paths.
  4. You're correct, this is the right way to do it, except when you set the value of a variable in a block (typically, an IF or a FOR statement). You can find an explanation for all this in the online help text of the commands. Try these commands at a prompt: SET /? HELP HELP SET HELP SETLOCAL Also, try these to find additional important information: HELP CALL HELP FOR HELP IF However, this matter doesn't apply to your original issue, and is not related to this forum. If you have any further questions along this line, you should post to here.
  5. Tried again, and this time I bypassed the downloader I'm using (Free Download Manager 3.0) and used the browser directly, and it worked.
  6. I'm not sure that it would be a bad idea to include this, since it might be important for non-update related software. True, so you could leave those out. However, check here for additional updates (see post #3). Yes, they're for English, but they might still be useful. Actually, you can find links to those here. Uh, just to be clear, what FDV provides is a fileset that may or may not be used, in whole or in part. “FDV not recommended” means he thinks you shouldn't bother including those updates, but they're included in the update list because M$ officially released them for 2000. The updates go in the folder indicated on the updates list. FDV's files go in the FDV folder. If the FDV folder is empty, then nothing happens. If you include all or part of his files, then those that are included in the folder are used. I say "in part" because you could choose to not use everything included or not, depending on your preferences and your understanding of what those files cause to be changed about the installation of 2000. Let me suggest that, to start out, you not use his files until you get everything working. Then, plan on spending a bunch of time reading his files before you use them (this is about where I'm at right now). They're very interesting and informative reading (to me), and afterwards, you'll understand their purpose and what they do better (they have a lot of comments in them). You should then understand that you may want to modify his files before you use them. This is the means by which you can "configure" the effect they have. True, you should use the update list at FDV's site, since that one is still being "maintained". Actually, I think Maxfutur was refering to 1.7.9 when he said "Last official version" However, I don't believe it will matter much. I've been using 1.7.10 beta J v3 (hadn't noticed v4 was available yet), and it seems to work OK for me.
  7. I haven't tried your test myself, but just off the top shouldn't this: ECHO PKGINST=%PKGINST% be this?: ECHO PKGINST=!PKGINST! Also, you'll need to add this at the beginning of your test: SETLOCAL EnableDelayedExpansion So, like this overall: @ECHO ON SETLOCAL EnableDelayedExpansion IF EXIST HF\*898461*.exe ( FOR /F %%I IN ('DIR/B/OD HF\*898461*.exe') DO SET PKGINST=%%I ECHO PKGINST=!PKGINST! ) PAUSE
  8. Tried to download 1.0 beta7 and no luck. I got to the download page and the download link responds, but the resulting file is only around 1K and clearly not the archive file it's supposed to be. Can anyone shed any light on this?
  9. I'm interested in the same thing you are (not Spanish) and have been investigating it for a while. I can't answer all your questions but I can get you started. You mean this page, right? Becasue the answer to this question is really close: See Step 3 on this page. This page is probably the best information in general about what you want to do, especially with regard to the Windows 2000 Service Pack 4 Hotfixes list. Tomcat76's Dynamic hotfix lists are still available here. That's my understanding. Yes, if you install the SMTP service, then you'd want that fix. But I don't think it has anything to do with Hotmail. This would be if you wanted to provide your own mail service for a local network, or wanted the mail server to interact with other mail servers on the Internet. Probably doesn't matter too much as long as you have one. A good place to get one would be Mim0's site here. Mim0 maintains the XP update list here, and in the "Table 6: Files used by HFSLIP" section you can find links to a couple versions. Actually, your English is pretty good.
  10. Thank you for the explanation. For others like myself who might not understand it immediately, under item #2., wordpad.in_ is in Source\I386.
  11. Didn't realize that. Didn't think to compare different versions to see if it was in previous ones. I was using the most recent one I could find. Wow. Behind closed doors eh? I thought others would like to be aware of it in case they were having (non-obvious) troubles. I thought about that, but thought that since it was about HfSlip in general, this was as good a place as any. Neither have I, and I didn't attempt to anaylze what was going on there since I've only just recently started to examine the code in the first place. Sounds good to me. Yeah, in general, I think starting a new topic regarding maintenance would be a good idea. But if PMing Mim0 about his version is considered more apropo, that will work for me. It's just that then all that takes place without input from others, which I've always heard was a good idea. It matches the version I mentioned. What do you mean? Ah, yes you have, but maybe misunderstood is a better characterization. Which wasn't the one I mentioned. Ah, yes, there is, beta_J_v3. A revision of beta_J_v3? ******* Basta! Time to move away from this obviously tainted place of discussion. Mim0, I'll PM you if you like about other more minor discrepencies I've found. I think it should be you that starts a new topic about your version, since it's yours after all.
  12. jinjou

    Windows Updates

    bristols, Thanks much for that! I certainly haven't seen much to give me that feeling. Boy, I admit that did not quite compute. Is the later release on the list? If so, which one? I guess that would help me anyway. Actually, I just thought it would be good to tip people off that FDV thought Windows2000-KB842773-x86-ENU.EXE was also to be avoided, but anyone can find that on his page like I did, if they're looking. You rock dude. ***** OK, I admit it. I'm a noob. I just spent five minutes trying to figure out how to make a "so and so, said:" quote. Anyone want to toss the old man a bone and give me a clue? Much appreciated. And this post editors got some MAJOR kerning issues...
  13. So, to start out with, sorry if this is the wrong place for this, but really, the right topic is locked (), and this looks about as close to the right place as I can determine, other than starting something new, which seems like it ought to be unnecessary. I'm using Mimo's hfslip-1.7.10_beta_J_v3. On line 2749 is the following (very partial) statement: ECHO>>WORK\WORK\HHIVADD.TXT Is the "WORK\WORK\" path an error? I did a global search for it and didn't find it anywhere else. That's not conclusive by any means, but it caught my attention almost immediately when I first saw it. Just seemed wrong to a have WORK folder inside a WORK folder, I guess.
  14. jinjou

    Windows Updates

    @bristols There's a couple of items that a review of the updates page for 2K on FDV's site has revealed. Nothing urgent, nor maybe even important, as 2K has probably already slowly sunk into the West for a lot of folks. Just not me. The Windows Media Player 9 installer link, MPSetup.exe, is pretty much dead. Didn't take me anywhere worth going. So I tried a web search (Yahoo), which is getting to be a frequent occurrence for me where M$ software is concerned. That brought up a couple of free files sites, the second of which (http://www.freewarefiles.com/downloads_counter.php?programid=4643) was merely a link back to M$'s site, but guess what? It worked! So it's still available, and it's a direct download to boot. http://download.microsoft.com/download/1/b/c/1bc0b1a3-c839-4b36-8f3c-19847ba09299/MPSetup.exe Now the only remaining issue is how long will it last... The DirectX 9.0C (standard) link is also pretty much dead, but my luck in finding a M$ link didn't hold. There are some FTP sites where I was able to obtain a copy but most were in non-English speaking domains, they weren't all the same size, which might mean different languages, and who knows how long they'll last. Not saying there's anything to do here, just being thorough. Another item is that Windows2000-KB908531-v2-x86-ENU.EXE includes the note "FDV not recommended". According to his page, Windows2000-KB842773-x86-ENU.EXE should also include that. Last but not least, I gotta say, "Don't do it!" doesn't do much for me, and apparently others are confused as well (). Wouldn't a relevant link () would be a good idea? Thanks for listening and your time! @ykchanaed Thanks for IEAWSDC.CAB and OPUC4.CAB. That makes my collection complete.
  15. jinjou

    Windows Updates

    @bristols Tried to PM you, but no tickee, no washee... Besides the message above, I would've included:
×
×
  • Create New...