Jump to content

Bullets

Member
  • Posts

    17
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by Bullets

  1. ok i take that back - it wasn't a GPO - at first glance it seemed that way but after i left work last night i was thinking and i realized that it was McAfee VirusScan 8.0i Enterprise...part of its advanced virus "protection" features is to disallow the remote creation of autorun.inf's. Once that box was unchecked, problem no more :) Thanks again.

  2. did you do this through a network? Like from a CD-Rom on your computer to a remote share somewhere else? Cause if i stick a CD-rom in the server2003 box itself, it will create the autorun.inf just fine. Through the network however it just gives me access denied errors. Its definitely not in use anywhere cause I just extracted it from an ISO, and that exact file moves perfectly fine to a 2000 share...i can't figure this out..so strange...

    EDIT:

    Also - to totally eliminate the "file in use" thing, even if i try and create a text file and rename it "autorun.inf" it will give me access denied error, yet i can create autorun.ini's, autorun.ing's all day long - just not a .inf. All other .inf's transfer fine. Its very odd...

  3. Hey guys - got a quick question regarding server 2003. I've tried transferring "autorun.inf" files through the network onto a share on a Server 2003 machine. It promptly gives me the error that "Cannot copy AUTORUN: Access is Denied.". Thinking it was possibly just a weird ACL thing with the share, i tried to drop it right in the root with the administrative share (c$). Same error. I also tried all the other Server2003 boxes we have, same error. Also, happens with the different versions too (i've tried Datacenter, Standard, and Enterprise) and all get the same error. Yet i C$ into one of my 2000 servers and it copys the exact same file without a problem. Is this something specific to 2003? If so how can it be fixed? Any help is appreciated!!

  4. Gosh,

    One other thing...i was reading through your "analysis of longhorns winpe" and i realized something...(oh, fyi, the pics on that page don't work)...you said that the .sys file in the boot folder is what accesses and then unpacks the .wim file...so i thre it into hex editor and sure enonugh there are several references to install.wim...so im' going to play aroud with that for a while...anyone else wants ot jump in and try too they're welcome :) see ya.

  5. ok, i'm having minimal success here...i tried exactly what you said Gosh and only a few things happened...on my first attempt it launched bootfix and said "press any key to boot from cd" and then i pressed any key and it instead of booting winPE it rebooted...the next attempt, i copied the ENTIRE unpacked boot folder into the boot folder on my AIO dvd. 4053 folder, for reference to the previous article. Now, i pressed any key and it booted into the winPE. Soon as its supposed to start do look like "Windows Longhorn" with the orange bar underneath, i got a blue screen saying "A problem has been detected, etc." with error code 0x0000007B. So, it seems to boot the setupldr fine...but i'm not sure whats happening after that. Any insight is appreciated.

    PS

    Nothing in the Sources folder had to be changed to say Src4053 intead of Sources...i checked every file in hex editor...and came up with nothing...

    PPS

    One other ting, when i replaced the words BOOT in longhorns setupldr it replaced it 114 times...quite a lot more than the 4 from the xp-like install..lol...perhaps there are some things changing that shouldn't be?

    Thanks again

    :)

  6. Hey Guys, i'm new here and i've been trying to make a multiboot DVD with two of the 400x+ builds of longhorn. Therefore, they both have their own boot folder. The guide i'm using (flyakite) says to rename the cdshell folder and leave the longhorn folder as boot because its easier, however, i am assuming i would need to rename the longhorn boot folder to something else and leave CDshell alone. Does anyone know where to find a guide on what to change so that the longhorn boot folder can be successfully changed to another name? Thanks.

    PS

    Any other suggestions on how to do this are appreciated.

    Thanks :)

×
×
  • Create New...