problem in timeline T39 in ryan 1.3.1
problem in timeline T39 in ryan 1.3.1
my setup screen is stucked for more then 1 hr, so being tired i restart my PC, again the same.
currently i intregated 1.3.1 normally manually.
t39 hangs more then a hour
i have nothing intregated in my xp except ver 1.3.1 and addons
this wont fix the problem but it will give you and idea as towhat is causing the problem Click On Me
Don't sweat petty things....or pet sweaty things
I doubt it's hung permanently. A hang at T39 is to be expected, but an hour does seem awful long. Did you integrate over a clean CD?
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
http://www.ryanvm.net/forum/viewtopic.php?t=2357
My longest hang was 27 minutes on a crappy 600 mhz pc with a 4 x cdrom
, so one hour sounds like somehing is really wrong,
oh btw correct me if im wrong ryan but technically the install doesnt hang at t-39 its just that its signing the cats or signing the files defined in the cats i think.

oh btw correct me if im wrong ryan but technically the install doesnt hang at t-39 its just that its signing the cats or signing the files defined in the cats i think.
Don't sweat petty things....or pet sweaty things
it does take me about 10min to get through t39 stage now. i have bash's DP (method2) and ryan 1.3.1 along with nlite
comp is sempron @ 2ghz and 1ghz.
probably it's not bad idea to burn your UA cd again with different media and at slow speed. (if you notice that comp has reading your current cd) .. happened to me couple times with my memorex .. after using taiyo cdr .. problem went away
comp is sempron @ 2ghz and 1ghz.
probably it's not bad idea to burn your UA cd again with different media and at slow speed. (if you notice that comp has reading your current cd) .. happened to me couple times with my memorex .. after using taiyo cdr .. problem went away
its a known issue, the install will hang at t-39
ive been reduced to quoting myself because of my excesive lazyness. 
hahahadgelwin wrote:My longest hang was 27 minutes on a crappy 600 mhz pc with a 4 x cdrom, so one hour sounds like somehing is really wrong,
oh btw correct me if im wrong ryan but technically the install doesnt hang at t-39 its just that its signing the cats or signing the files defined in the cats i think.


Don't sweat petty things....or pet sweaty things
Allways use a freshly slipstreamed SP2 disk or a real SP2 disk with no hotfixes integrated. From my experiances and others it is best to start fresh. If you don't then problems may occur when it tries to install the hotfixes twice. I think that is the issue because I was having the same issues and I used the shift F10 trick and found out that there were multiple hotfixes that were hung.
I reported this in another topic but i had the same issue last night.
Please can you list your hardware if you have problems.
The chipset and what type of drive ( sata or ide ) I think are very important.
And if you had to use the f6 to add sata drivers or if you slipped in sata drivers so you dont have to f6 where you normaly would.
My Hardware.
Abit VT7, Via Chipset and sata drive with sata drivers slipped in using this http://www.msfn.org/board/index.php?sho ... 34440&st=0 method and not the bashrat pack.
Please can you list your hardware if you have problems.
The chipset and what type of drive ( sata or ide ) I think are very important.
And if you had to use the f6 to add sata drivers or if you slipped in sata drivers so you dont have to f6 where you normaly would.
My Hardware.
Abit VT7, Via Chipset and sata drive with sata drivers slipped in using this http://www.msfn.org/board/index.php?sho ... 34440&st=0 method and not the bashrat pack.
Last edited by Paul_365 on Sat Aug 27, 2005 7:35 am, edited 1 time in total.
Its not the speed of the drive thats in question, its weather the T39 Delay is exagerated because the install is on a Via chipset or is using a sata drive or drivers.
Installing to a Virtual PC is not a valid test for this, as your install on your VM or VPC should be the same as mine is providing our source disks are the same.
The Problem is only diagnoseable (real word?) when we install to real hardware and expose the install to real hardware.
Installing to a Virtual PC is not a valid test for this, as your install on your VM or VPC should be the same as mine is providing our source disks are the same.
The Problem is only diagnoseable (real word?) when we install to real hardware and expose the install to real hardware.