Jito463

@Hulk Did you test this with XP Pro x64 or with Server 2k3 SP1? I ask because I tried various combinations (including those two you said were the only ones you got to work) and still got the ntldr is corrupt message. I may need to try copying the AMD64 directory to the root of the drive. Have to wait and see.

Why don't you create multiple setup folders each with their own $OEM$ directory containing unique cmdlines.txt files each then use the optimize function of cdimage to make it fit on CD (or just use a DVD).

I think he means it either needs to begin with an I or end with a 6, but so long as that condition is met you can rearrange the rest in whatever order you like. So theoretically, the following should all work (need to test though): i386 i368 i683 i638 i836 i863 38i6 3i86 8i36 83i6 So far as I can tell, based on what he described above, those should all work.

It's just as LiquidSage described above. However, he did make one mistake I should point out. That should go under the section [sCSI.LOAD].

Actually, there was an OS released in 1998. It was called Windows 98. 98SE was the Second Edition which was released in '99, but the core OS was released in '98. I can understand the points back and forth here. I've ran almost every Microsoft OS from MS-DOS 6.22 up through Windows XP x64 except for WinNT 3.5/4 (used it, just never ran it). But in general I would have to agree with the original poster of this thread. I just shake my head in disgust when someone buys a $1000 computer from us (a small OEM I work for) then decides to get it without an OS (which saves them like $50) and run 98SE or ME on it. If the industry made a move to no longer support those operating systems, it would force the rest of the market to upgrade. I'm sorry, but the fact is those OS's were never truly stable when they came out. It was recommended that 98/98SE be formatted and reloaded about every 6months - 1year for stability. And don't even get me started on ME. I worked for CompUSA at the time it came out and MS gave all us employees a free, unlicensed copy of ME at one of their roadshows. It lasted about 1 week on my computer and started crashing left and right. I think when I started using 2000 I ran 98SE in a dual-boot for about 3-months or so while waiting for compatibility with some devices. After that, I never went back. Face it, in spite of all the changes you guys are making, it should be put out to pasture. That's my opinion on the matter.

Though I have to wonder - given our current issues implementing x64 onto the multi-boot discs - how easy it will be to implement Vista in such a manner.

Whether it is or isn't (I think it's the standard Administrator login key though), it should also reference to HKEY_CURRENT_USER so I would try modifying it from there.

Well, that's not entirely true. All you've essentially done is added a multi-boot DVD to your x64 CD. You've not really added the x64 CD to your multi-boot DVD as we're trying to figure out here. I understand you're trying to help, and that's great. We need all the help we can get. But at the same time we need to keep our focus on the ultimate goal of this project.

I much prefer Alcohol and am even a part of their forum support team. They use the same VD drivers as DT and even share a developer or two between them, so there's not really much of a difference between them in that regard. As for your requirements above: My ideal Emulator is: 1- Can deal with virtually every Image Type! Alcohol can work with almost every datatype except for B5T and there's a way to make that work in the VD. 2- Compression Alcohol does not do compression. It has been suggested, but there are no plans for it at this time that I'm aware of. 3- Smooth,Reliable,No Hangs,Compatible Well, I've never had any problems with it. Some people have, but that's why we're there on the forums in case they do have problems. 99% of the time it's due to problems with Windows, though. 4- Can put info and comments on each CD like for instance e.g Serial Number No, and the reason being that Alcohol's main purpose is to image CD/DVD games so you can play them as if they were the original. Modifying the disc to add files and such to them defeats the purpose because the disc could no longer be authenticated. 5- Doesn't take Half of C: drive space! Well, depends on how many discs you image and how big your C: drive is. .

Erm, C&Q drivers have been available from AMD for months. http://www.amd.com/us-en/Processors/Techni...71^9706,00.html

You can scoff all you like, rodan. But the fact is my machine runs faster under XP x64 than it did under 32-bit XP. And that's without even going through and locking down the unnecessary services. No, it's not twice as fast. But it is faster.

This will definitely come in handy when I'm modifying my txtsetup.sif with more drivers. Thanks, djbe.

I know what you mean, n00dles. I'm the only one at work who creates our preinstall discs. Right now I've got them preinstalling from the disc, but I'm considering going back to a network preinstall method. Main reason I went with a DVD based install was at our old location we had 3 seperate networks, each with their own internet connection. Now that we're at the new location with only one network, it may be simpler to do.

Make sure you properly edited the setupldr.bin or it won't be able to find ntldr.

I'd already considered that and as a quick and dirty method it would work. But it doesn't answer the real question of this post which is how to integrate it truly on a multi-boot disc.

62nds.com has been around for a long time. I've got some old DOS utilities they made that I still have occasion to use. I agree about XP SP2 being important (in fact, as soon as the final release became available I started using it in our preinstalls at work), but some corporations still haven't finished testing SP2 in their network and don't want to be forced to upgrade which makes this a nice alternative. There are some things they could do better with the Windiz Update site, but in general this is a pretty good idea.

What program are you using for the menu?

That's 16TB of virtual memory. Physical RAM is limited to 128GB. That's still far more than any 32-bit OS can handle, though.

You won't get an option for repair install if you use a winnt.sif answer file. You'll need to create a version without the winnt.sif to do that.

Thank you for the PM invitation, but I have no desire to attend your demo. If it ever becomes available to test with, I may give it a whirl. Let's just accept that we won't change each others minds and leave it at that. I don't want to see it work over the internet, I want to see it work for myself. Until such time, I have no more interest in it. Until I can try it myself, it's just a waste of time for me.

Well, you could add a delay into the script (30 seconds, 60 seconds, whatever works) so it waits for the desktop to load before actually running.

@rhythmnsmoke Please read more carefully when replying. I never said your program didn't work, I said I would not believed it worked until I could test it for myself. And as I stated in the message you quoted above, I won't even trust an internet demo because it's possible to fake that. You can claim all you want that it can't be done, but it can. I wouldn't take my coworkers word for it about NOD32, but I believed once I tried it myself. And I won't take your word for it, but I may end up believing *IF* I could try it for myself. Until that happens, I just won't take anyones word for it. Even reviews in major magazines don't convince me until I can try it for myself.

Yes, a RAR SFX should execute just fine from cmdlines.txt if that's what you're asking. I'm pretty sure the system variables would be available by that point. Best way to know for sure is to try it.

The difference with Sony and the PS3 is that they're a credible source that has proven themselves. They are a clearly known and defined company and based on past behaviour we have no reason to not trust what they're saying. You have no such past behaviour for us to look at and say "Oh, he must be telling the truth. We should trust him". Does that make sense to you? We don't know you from Adam, so the only way we're going to trust is by trying it for ourselves. And regardless of how many times you claim it, a demo over the internet is not the same as the real thing and can be faked. You can claim otherwise all you want, but it can be faked. I'm not saying you are, but I'm saying it can be done and as such those of us in the know won't bother to take you up on your offer because we have no way of knowing if what we're seeing is real or not. It's got nothing to do with our ego (well, at least for me it's not and I'm assuming for the others), but it's because we know what can be done with computers and won't trust your software until we can stress test it ourselves. As an example, my coworker tried to turn me on to NOD32 instead of NAV. I was pretty happy with NAV (except 2k4's bloat) and I didn't even really trust his word on it. But then I "tried it for myself" and have been very happy with it. I didn't even take my coworkers word for it when he suggested a new program, but only believed it after testing it out for myself. What makes you think I'll believe you, a total stranger? I'm sure that same mentality is the reason you find so much resistance here. We don't want to listen to you talk about how great it is, we want to play with it and find out for ourselves. If you wanted to expound the greatness of your companies product, you should have picked someplace less tech-savvy. We don't just take people at their word who haven't proven themselves.

Here are the changes I made to manually implement viamrx64.sys into my preinstall CD: [SourceDisksFiles] viamrx64.sys = 1,,,,,,3_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_1106&DEV_3249 = "viamrx64" PCI\VEN_1106&DEV_3149 = "viamrx64" PCI\VEN_1106&DEV_3164 = "viamrx64" [SCSI.Load] viamrx64 = viamrx64.sys,4 [SCSI] viamrx64 = "VIA VT64xx/SATA RAID Controller" You could check and make sure those lines exist in your txtsetup.sif (the last line may look slightly different as I modified it). Also make sure the file itself exists in your AMD64 directory and not your i386 directory.