Alanoll

The current rule has been in place for well over 4 months now. And it's not like we're patrolling for Signatures, most of the ones we remove are ones that are overly accessive or are reported. The simple fact that you didn't read it is your fault.

um... why? The reason an MST file is required for Office is because it doesn't have any switches to select components and proload any other configs. This MSI has all commandline switches required and SHOULD work fine with Group Policy. You have two choices... A. Use a variable path in the INI statement (%CDROM%) for example B. Copy the file yourself to %systemroot%\Winamp5.ini The reason the MSI needs the full path is because there's no reliable way using the script i have to get the directory of the MSI, regardless of the fact if users want it else where. The Full Path requirement simplified the script a great deal.

To be honest, there really is NO reason to let a user edit it themselves. It's clearly stated in the forum rules the regulations on signatures.

I believe you're missing the point of what gamehead200 had said. For any chatroom to truly help in that manner, you'll need people to idle in it, and BE THERE when someone needs help. Chat can still continue as normal, but people would need to be there to talk almost all the time. MSFN to my knowledge has tried this two times in the past. 1. The first attempt was a full fledged IRC channel. Failed because of lack of users. 2. The second attempt was proposed by MSNWar and used a conference program. I think i saw at MOST 6 people ever in the channel, and myself and MSNWar being the only near constant people staying in the channel. That being said, when some came in to ask a question, most times they wouldn't get an answer because we were AFK. This soon died after it was concieved. I predict on past experience this experiment will burn and die the same death as the others. People will come in at first, loose interest and leave. Or they'll come for help, get it, and never come back...again the channel dies.

Having 150kb limit for each post how could I uploaded here? My only option was to upload to rapidshare.de whoops, guess I should have adde the smiley so you know I wasn't trying to say you did something wrong. Next time though, if you need something attached, you could just send it to me and I'll upload and attach it to yourpost.

That was not me my friend...I only attached for file to the creator's post

I see a flaw in the BitTorrent plan, which is why i dislike torrents. There's no guarantee that people will be able to connect to any of the seeders. I know, my university has ALL P2P protocols blocked at their routers (yes, it's possible I've setup many for companies doing this, and no, it's not just the ports, it's the entire protocol) so torrents would be useless to me. That being said, I shouldn't be the one to hold it back, but my school can't be the only one that does this. Then you run again into the problem of...most of the members on this forum reformat occasionally, that runs the risk of the seeder not reseeding the file when done, and the file dying as a whole. In principle it's a good idea, in practice however, it won't last. You'll need a dedicated seeder, which serves the files and never loses the files and rarely ever goes offline...wait...that sounds like a webserver... I really don't mean to keep shooting down your ideas prath...

That's the second file of yours I've attached so people don't have to go to that dreadful site... I'll try this later on... But as for the sticky...I do believe a random suggestion in a post does nothing. Let alone one for your OWN topic. It's just not really polite in all honesty. I'll unsticky the old thread, but there really isn't any need for this to be a sticky, or the other page. They're still on the first page of the forum, and a simple search should bring these up.

do go ahead and tell... (if you attach the BIN file, you'll need to RAR/ZIP is first i believe to pass the file type check on the board) I'd rather not have a premodified file, but rather a description of how to do it myself and how you came to the conclusion....

Have a great birthday! Don't come near this board all day...

Seems someone is getting alittle testy there... I had known about your "way" for awhile, and I believe someone has even posted on it, and I responded the same way, it's not a true multiboot. Let's see, I can think of atleast two different version of a x64 OS i'd like on a CD. 2003 and XP. Add to that three seperate loaders for each with different WINNT.SIF files, and I come about at 6 possibilities. Then I go and try to add 2003 32bit SP1 to the disc, again with MAYBE 3 variations (Enterprise, Web, and Server) and then tack onto that another 3 WINNT.SIF variations and we're at 15 OS's in total. Now you're saying, there's no way that will fit on a disc, but wait....that's only MAYBE 1.5-2 gigs of unique files, leaving plenty of room for more. Now do you see why I said it's not a true multiboot? I have Win2003 SP1 working just fine reconstructed on my own using the files I posted earlier (though their 32bit counterparts since I posted the 64 bit). I would assume the same methodoloy would work for the those as well. Simply replace the EN6R with your folder name, and EN64R with it's equivalent, and edit the path entry. Now you're saying...but how do I know what files need to be in the directories and where? Oh I don't know, maybe because I posted the directory listings as WELL as an example directories for both with the required files. Have you tried going that route? I don't believe you have, unless I've missed something, since everytime I tried to point you back to my post, you seemed to have disregarded my response and thus arrived at your current conclusion. And no, this is not flaming, but just illustrating my point. If you have tried the above using what I posted prior, my apologies for believing otherwise.

@amd64lover that would negate the purpose of a Multiboot atleast in it's truest definition. You would only be able to have ONE x64 OS on the CD (or 2003 SP1 for that matter) since you could have only ONE I386 folder.

I've just disabled posting on Mastertech and gdogg for their last few posts in this thread. I was not joking in my post before. Keep it clean, or don't post.

I only have a 32bit processor, so i could only test those, and Windows Enterprise 2003 SP1 installed just fine

@Nakatomi2010 why are you copying all the files?

I do believe I posted a DIRECTORY LISTING of the files found in the required boot folders... then edit TXTSETUP.SIF to look for the ROOT like in a normal AIO disc like before.

Umm... All the files I posted last night a couple posts back, are for ONE OS, for teh 64bit version. So...umm...yeah...If you look, there are two seperate folders

I sometimes find it amusing going off topic. I find it even more amusing that you chose this thread to whose last reply was back in February. Speaking of going off topic, what does your post have to do with "Gosh's Registry Files"? This thread isn't pinned either.

I've delete two prior threads because of the flaming going on in them. Next person I see from this post on, will have posting suspended for a period or depending on the severity, permanently BANNED from the forum as a whole. This thread by no means belongs to the nLite forum, and as such I'm moving it to the XP forum.

@geitonaki Here are the two dir listings you wanted. I did them on the EN6R and ENR64 folders, since they're for the 64bit OS Windows 2003 x64 Enterprise. EN6R = I386 from the original CD, atleast in where it attains it's files (not sure where DISK101 and those came from yet) and the only file altered is SETUPLDR.BIN ENR64 = AMD64 from the original CD, and the only file altered is TXTSETUP.SIF I'm attaching the DIR listings, and RAR files of both the folders in question. EN6R.txt ENR64.txt EN6R.rar ENR64.rar EN6R_BOOTSECTOR.rar

@geitonaki I'll do it later today when I get out of class, and am done with my meetings this afternoon.

I prefer not to diredtly edit any ISO, so i don't use anything other then CDIMAGE or MKISOFS to recreate the entire ISO instead of inserting a new file using WinISO/MagicISO/UltraISO or the like...

That's probably because the initial servers the eDonkey2000 download connects to are hosted by themselves. To completely bring down the ed2k network, you'd need to take every server offline, which number in the thousands of which everyone can connect to. The same was true for the Gnetulla network, started by the original Napster, which still exists today, even with a new version of the protocol under testing (implemented in Sharaza i believe). Then there are the various other DECENTRALIZED networks around that users connect directly to eachother that will only be brought down once all those users have legal action taken against them. I have no fears that P2P will die anytime soon. That being said, this doesn't mean you have a right to use P2P and download song/movies/software from them. Most people assume that since they have the program, it means they have the right to use it any means they can. They have the ability to use it in such a manner, but don't have the right to do so. It's still an illegal activity, and subject to applicable laws.

Now quite honestly, I was going to give the man ALITTLE credit for his statements, till he said this. There is no guarantee SP3 will contain all these hotfixes. It's the common basis for a service pack to contain all the hotfixes, but it's not always the case. Lets also not forget, Service Packs are typically more then just a big hotfix introducing new features or updating entire software packages (DX or WMP for example). The simple fact that these hotfixes are reference in the Knowledgebase as SP3, doesn't mean they'll be in there. That just means it's on the SP3 branch, though that tree can still be trimmed. I remember seeing a couple of hotfixes that came out after SP1 that didn't make it into SP2, but were marked as SP2 in the knowledge base. So all in all, Microsoft can change their mind all they want at any time when it comes to future product releases. Heck, look at Vista.

knew i forgot to do download something a couple weeks ago...