Search options (Page 66 of 99)

hi

2007-07-02 09:57:04 : <INIT> [OptionalSettings]\QSC not specified: default (yes) was set.

2007-07-02 09:57:04 : <INIT> [OptionalSettings]\QSC default (no)    was set.

2007-07-02 09:57:17 : <GUI>  Changed Windows installation files OR export (depending on the installation platform) location to I:\easyboot\disk1\ainall\w23s.
2007-07-02 09:57:18 : <GUI>  Windows Server 2003, Enterprise -  Corporate SP2 detected.
2007-07-02 09:57:18 : <GUI>  The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2007-07-02 09:57:36 : <SEL>  Selected module: mod_slip_w2k3_x86-32_disc_m2.
-------------------------

yesterday I read something about QSC and 888111.
When QSC was used, it was slipped?
We did not get a log on that report, but I can do a run on a MSDN source for server 2003 sp2, and see what it does.

besides, I am a blonde..

(a not so ) standard desktop (asus agp with an Xtreme CPU)
card NV FX5200 installed cool

Abit mobo, with TNT in a PCI..
installed cool

Same abit mobo, with agpx8, Ti-4300 OK
a fly by box with MSI NX7300GT, OK

no laptops tested

Stiertje is one of the people that still had problems, and the driver he says works has NO specific sub/Rev info in HWID for that card.
(not Integrated in mobo. It's a card..)

While I was trying to fix the issue, I got interrupted by real life, and later on a 'half fix' got uploaded because  the fix was in two files, and one of them was not even uploaded and the other was what I had when I got interupted, not what I had when I finished..

After the BIG typo, Krell mentioned that ''typo'' Which I knew was intended for Stiertje.
(erm, Krell did not spot no such INF had the HWID.)  and I have then done some more work, more checking, and 7.07 came along.

All in all, I am ashamed of the rush jobs I published.
The reason why  those rush jobs even got online, is that fixes were needed, and testers are in short supply.
I had the time, because this was ONE week of holiday I had for . The good accident happened, a critical typo.
Mass Storage fell flat.
I am lucky because it got the detectives out. And that typo then got guys to look at stuff and tell us about it, what actually revealed things that had been there for quite a while.

All these things/fixes are in 7.07.
Those detectives, they could be testers.
It was not my intention to make such a mess (e.g. a comma kils DriverPacks.)
But, you know, it were not the first time guys tried to fix it and got "backfire."
It may sound boastful, but I tried to fix a few as a return of favour, and think I done more than a few.

don't shoot the girl, the pianist loves her.

Hi
was this with method 1?

I know this is seemingly off topic, but I want to have fast ways to check bugs when I make changes to an INF or INI.
Anybody can condiser me a dolt, but a forum which says we cannot have quick exchange of "forumwide related" tidbits in a topic where peers are active, is not a friendly forum.

Hi
the wait was long.
After looking at what was needed and doublechecking..
(them inis are like little snakes in the grass)
And fter checks for overlap, I did eventually wind up doing exactly the same.
(With just a descriptive foldername added).
I used the Dell620sigmatel driver which was in REQUESTS on FTP for a good while,  and end result is exactly what Fragbert has offered for so long.

Thanks for your patience.

hi
suppose you still needed a floppy because there is no good txtmode driver, then OemPreinstall=Yes says you cannot use the floppy.

I can find the file easily enough..

but, after a slipstream... when I put VMS in that search for TXT dialog box, and let it look for VMS (which ought be in txtsetup.SIF because slipstream added VMSCSI to it.) then it won't show me that txtsetup.sif has that bit of txt..

strange.

Hi
I found VM-SCSI in MassStorage, so I'll update it.

dupe post,