bilemke

The problem is not changing what windows sees as the current drive letter.. It is all the other changes in the registry that need to be changed to match. I had to fight this problem many times with my unattended cds. I have 2 Raid Arrays with 2 partitions each on them. Plus, a floppy drive that has a USB card reader build in.. I have to unplug the 2nd raid array and USB card reader (internal) every time I reinstall windows to gurantee it doesnt try to associate C: with a partition on the 2nd raid array or one of the drives that windows sees in the USB card reader.. Another example is if you have a secondary IDE controller (raid or otherwise) and have a zip-100 internal drive (i dont have one buy have seen this case). Windows setup will see the zip drive before the secondary IDE controlelr and your HDs on it. So, it assigns the lettter C: to the zip drive and starts with D for the HDs. Since it remembers from setup, the resulting windows install will be installed to your HD on D:\windows. Format and reinstall is the best way to date, that I have found, to resolve the issue. Partition Magic used to work great in 9x for this as it really did do a good job of handling all the registry entries. I have not used it in a while (no 9x and no other use for the program as I have found freeware better for doing partition changes) but, I would start with a current version if you were to try anything to do this properly. " reformatting and reinstalling " Yes, too many people suggest that without knowing.. You are right to look first, you will learn more (even if unrelated to the problem). Anyway, good luck in whatever you find out and choose to do.

Like Astalavista said.. Yes it can be done.. With a little more work.. To stat with you need a cd boot loader instead of jsut the "Windows Setup" cd boot loader.. Check out cdshell Plus, make a disk image (with winimage if you want) of a bootable dos floppy with your choice of dos based partitioning software like Ranish Partition Manager.. Next, using info from above site, make a cdshell script for the boot loader and build the cd as also described in the above site (yes, I know, a lot of reading, but worth it). So, after this cd is constructed you can boot the floppy image off of the cd in emulation mode and run the dos based program to setup partitions and then reboot. Next, from the same cd, start windows setup this time with all your partitions already setup and pick the one in setup you normally would.

It is running for a couple of days now, but I thought it will be easier if there is another way instead of Reformatting and reinstalling. Either at the DOS or BIOS level. I think I have to go to correct that. The danger of messing around with that is one will not be able to BOOT later, cause U are messing around with the System Volume or Bot Volume. Let me investigate into the Software, Thanks guys! <{POST_SNAPBACK}> I can tell you, BIOS and windows Dirve Management wont help this one.. There are too many tings pointing to F: as the boot partition and the location of default program in windows and windows fodler itself. Partition Magic used to be able to to do this.. Maybe still.. Best way is to reinstall.. Atleast the primary partition. You may want to try and hide the secondary partition from windows setup to prevent it from using the wrong partition as the boot partition.

If you really want to do it before windows sees the drive, your best bet is a bootable floppy image on the cd with dos and Ranish Partition Manager (or some other tool of your choice) on a multiboot cd.. Or a seperate cd. Tell you the truth, wjhy do you want to set up all the partitions besides the bootable one before setup? Windows will isntall to the partition you choose and then change the letters of the drives (if this is what you are trying to do) after you first boot in to windows.

Thanks, it is a nice little tool. <{POST_SNAPBACK}> Indeed it is.. I love that program for identifying packed exes.. Very nice right now for all the UPX flase positives with AntiVirus software.

Correct, this is a known problem with using a unnattend (.sif file) install type.. I see several threads going on to find a way to use drivers from cd without winnt.sif and $OEM$ folders.. One the need for winnt.sif is gone the floppy problem will be no concern eaither.. I am corrently trying to do everything I can to not use winnt.sif.. But integrating drivers without it are much more of a pain then with the oem setup. I would either update your cd with the new drivers you have on the floppy, or make 2 cds, one with unattend and one without.. You can get soem of the things you do with winn.sif and OEM setup type by using RUNONCE registry entries and such. I personally prefer these other methods over using winnt.sif. Anyway.. ramble ramble ramble...

I assume you have anti-virus software isntalled of some sort already right? If so.. May I ask which one? Sounds like a problem I have had a few times...

Which reminds me, Fantastic Four is coming out this summer. So, as Johnny would say, "Flame on!" Sorry, I just couldn't resist. <{POST_SNAPBACK}> You mean this.. Flame on.... If you have TCP/IP functioning and you are on the same subnet plus share the files in the manner I described.. There is no reason I can see why you should be unable to access all folders under a given share.. If you can access some but not the others.... Well.. Beats me then I suppose.. Why dont you format and reinstall then.. You were obviously, most likely atleast, playing with some service or another you shouldnt have been touching.. That doesnt even make any sense because you should either have rights/permissions to see it or not.. If you are seeing some but not the other well.. Go take nice cold shower... Flame off.... Good luck to you all, maybe durex can solve it for some of you.. My final suggestion would be a good wipe and start over.. Move your documents to another drive or safe folder and delete windows and reinstall it like gigabitfx said earlier.. Otherwise, if you can ping the ip address of the client and server, connectivity is not an issue and NETBEU or NETBIOS protocols are not going to be of help.. Esspecially not a crossover cable..

This is a issue that drove me nuts the first few months I had XP so long ago.. XP/2003 handle the authentication process a little different then 2000.. Futher... they tried to make it more friendly like 9x with simple file sharing but I think they just made it worse.. The fact that you cant disable it in XP Home is really a pain as it should not take XP Pro to be able to use Advanced file sharing.. Most likely problem everyone is experiencing is a conflict of both File System and Share permissions. For XP home users.. I feel sorry for you all.. I will not go through the process to reset all the permisions until a further date.. But, quicky for XP Pro users.. One, start with simple file sharing. Share a folder once (get past the "Yes I want to share my files etc etc etc..." dialog and atleast share something once)... After hitting apply you can shut it off right away.. (May sound reduntent but just do it)... Next, if at all possible use the same user name and password on both (all of your machines) or this will require further work yet. If you make matching acounts on both machines this will work flawlessly. Alright.. Go turn on advanced file sharing.. Next right click whatever you want to share and go to "Sharing and Security".. Click "Share this folder" Change the name if you want.... For now it will use default "Share permisions".. (Everyone, even people without a matching user name and password, will be able to see the share atleast when browsing the machine on the network)... Hit apply now if you want.. Or a little later.. Next, we go to the "Security" tab for some file system permissions. (Note, this security tab is only present on NTFS drives and not FAT32 drives) If it is a FAT32 formatted drive ignore this and only the Sharing permision applies (in which case you are probally not having this problem anyway). Again, if you have matching user accounts on both machines.. This will be easy. If the user name is not already listed.. Click add .. Then type in the user name (has to be one that exist on the local machine for simplicity sake).. Click ok and select it in the uppper list box... The lower box should show basic (default) permissions that will atleast allow you to access and read the files and folders in that folder. Check mark "Full control" if you want "full control" of the files remotely. Next, to make sure some sub folders do not have odd permisions.. Click "Advanced" and click the check box in the bottom left mentioning the replacement of permissions on all child objects. Hit ok.. This make take a while if there are a lot of files in the folder and sub folders.. You should be back at the security tab.. Hit apply or OK and try to access the share accross the network.. All fodlers/files and sub-folders should al act the very same as each other.. Hopefully I worded that correctly for someone to understand. Otherwise ask some questions and I will try to correct it or atleast answer..

I strongly doubt this will solve the problem... At least until anyone else could confirm it? <{POST_SNAPBACK}> This is very likely the fix if those who have been testing havent tried it.. I have lost track of the integration of drivers as the only ones I cared about were the raid drivers.. Without them it could prevent an install from finishing.. I dont need sound etc integrated. Anyway, some time back I added SCSI/RAID drivers without using unattend or adding anything extra exe to windows. I actually added on to txtsetup.sif dosnet.inf and PNPSCSI.INF (windows default scsi/raid drivers for the most part). Anyway.. Wihout winnt.sif (and consiquently the above mentioned entries) every thing worked. However, since my drivers (fastrak tx2000 at the time) were not signed, I would receive driver signing notices every time. Since the method still requires a OEM preinstall type of setup, I would add the entries to winnt.sif if you havent done so and give it a go.

I dont know why they called it Windows "XP" 64.. Should be called Windows 2003 Professional 64 Bit.. It is more like a client (non server) version of 2003 then it is like the original 32 bit XP.. It essentially is 2003 with all the stuff turned back on for client use.. Themes and such.. Which 2003 Server of course has, but are disabled by default. That is why it is XP 64 SP1.. It actually is 2003 SP1 so it is newer then XP SP2 (32-bit). Either way, I wonder if service packs for it will come with updates for 2003 server or when a update is made for XP 32-bit?

@RYU81 Its been a few days... It work out?

As noted in a earlier post.. the old setupldr.bin from pre sp1 should work fine.. I have personally done a full sp1 install with it and had no problems.

Two things you can try... Try a modified version of the parameters you are feading cdimage based off of what I use without any problems. CDIMAGE.EXE -LWXPFPP_EN -T12/31/2002,12:00:00 -bxpboot.img -G -H -N -M -O -X G:\XPCD G:\winxp.ISO Notice no -j1 option.. I have read about problems with that. 2nd solution.. There is a nice gui ISO program that can do optimization the same way now. You can try that too if you like. Shareware however.. But it works. Just need to enable the optimization function under properties. http://www.ezbsystems.com/ultraiso/ Update, foregot one other suggestion.. While testing.. Save your self some time until you get this worked out. Take a ordinary folder of files around 100mb or soo.. Duplicate that folder bby jsut copying it and renaming it.. Then try to make a test iso with those two folders on it.. Should come out to 100mb obiously.. But, this way you can get the thing working without having to go through 4gb+ of data just to reach an error.

Sweet.. RC3!!!!!!!! And I made it on the thankyou list. I didnt do much.. Reported a bug sorta... Anyway, might run a test in virutal pc with clean install.. And might fromat and reinstall a spare real machine just to test the appearance enhancements off a clean install again . Awsome work gape.

hey gigimarga214 can i ask which version of the ML370 you have? G3 or G4? G3 G4 They use different chipsets.. One is ServerWorks and other is Intel.. As far as the pausing/stuttering.. Couple things to note... Since I imagine you dont do a lot of 3d gaming on the systems (none I bet).. The video card shouldnt be too much trouble.. The audigy 2 is great gamer card but you may want to consider something from their non-consumer (I think that is what I can call it) line of cards.. More for straight audio use (non gaming), might have better luck with the drivers developed for those cards if you can get a pair to try out. But, with what you have now.. Couple things to consider, move the sound card away from any slots that have card in them.. Leave a gap.. Next, check to make sure intel (if you have G4 systems) has not realeased any chipset driver updates.

Wow.. they really changed setupldr.bin.. Looks like the major thing is additions for AMD64 folder on the 64 bit versions of the install cd.

98lite? Sleek? No.. not 98lite.. But it must have been a fluke.. Worked when I tried it on another new/clean install. Also, did you see my reference to the startup.cpl by Mike Lin?

speaking of licensing.. I thought the 2k style icons were working in rc2, but Only the windows style is coming through reliably for me.. Still need to use 1.6.2 to get the icons.. Not even refeshing/repairing/deleting the icon cache helps if I dont install 1.6.2 first.

My solution for defragmenting the partition I have widnows on:: format c: /q Then reinstall windows.. I keep all other data on much larger secondary partitions or even drives. No, but seriously I do it that way so I almost never defrag. You may not want to do that if you are not comfortable with manipulating partitions on a regular basis. It is best to do it when you are not using your comp. You want real fast.. Boot to something besides the partition you are wanting to defrag.. Use a Windows PE cd with your favorite defrag program on it.

I personaly dont use it, but I tested it on Outlook Express in WIN 98 SE.. It didnt break it completely. But it did make it a tad bit slower.. Just used the IE6 installer to reinstall the files and it was back up to speed again.

Cool I am very sorry I didnt mention this earlier.. As I mentioned after seeing mitsubishi 's post, I had this occur in RC1 too.. I should have mentioned it earlier.

Perhaps.. All I know.. some thigs do not get isntalled if it restarts.. no/cancle should do the same thing.. It is is just a isntaller asking to restart.. As long as it doesnt restart I beleive the others will start.. Usually they are already starting to run behind the Restart dialog when I am about to click on NO. basically.. Just click NO.. Then all should be good. The themes I assume are getting installed.. Will have to test once without installing the old 1.6.2 version of the service pack before hand.

Oh yeah.. Foregot the restart bug.. I had it happen in RC1 the few times I tested it.. One of the isntallers/update still asks to restart befoer the entire service pack is installed. If you do click yes restart.. Parts of the service pack do not get isntalled. I have gotten to use to it asking early and always click no as I notice some more batch files starting to run in the background..

I really dislike the new VB runtimes that are called .Net framework.. Even on win xp I ocasionally have had problems with msvcrt and msvcpxx.dll... They got rid of one evil for another.. @Gape.. Good work.. I can say I certainly dont mind the forced 2000 icons and theme.. For a very long time now I was always isntalling 1.6.2 before 2.0 betas just for the new icons and theme. @Mirror hosts Thank you all for making it easier to get this great addon/update for 98 SE.