[Tutorial] New way to do 250s

The only other thing I did different was on the usb mac was to up both numbers at the end so if the mac ended as 23 i changed the end of the usb mac to 34
 
ive been putting this in just after the dhcp_settings in the tut and keeping the original cmreg config ...its been going slow but on now for 3 days

cd \non
cd doc
enable force_cfgfile false
write

--------------------------------------------
like this ........

cd \
cd n\d
enable bpi false
enable force_cfgfile true
dhcp_settings ************your mac here in caps

cd \non
cd doc
enable force_cfgfile false
write

cd \
cd n
write
cd \
reset
 
have tried your suggestion mate still no joy...
cheers

Whatever I have done differently from the tut seems to be working. Running 20 meg for last 6 hours or so no problems.
 
Whatever I have done differently from the tut seems to be working. Running 20 meg for last 6 hours or so no problems.


doubt u would have done anything different mate as it has worked on 1 mac and not others which leads me to think i need a new swop buddy for macs.
 
I've since tried 2 more modems to replace one that a friend has and both gone off within 5 mins. The DW DHCP thing reports the macs as valid with configs so I don't know what's going wrong. I've tried 11 macs with configs and only 2 have stayed on the rest have gone off within 5-10 mins.
 
Well are you sure the modem you had, had the original ambit firmware on it in the first place?
 
Hi all
Just read though this post but has the tut been updated with any tweeks...
got my 232 cable and my new 255 and going to give it a bash fingers crossed

just read the tut but confused with this part
type mac_address 2 (followed by your good mac ie aa:bb:cc:dd:ee:ff +1) (enter)
is the +1 for the usb mac as I have a 255 do I need to type it
 
Last edited:
When i type in type cd n\h (enter) i get ....

Instance: Console Thread (0x80749064)

Specified subtable ('n') doesn't exist! Can't change to it...

Active Command Table: CM DOCSIS HAL Commands (cm_hal)

CM-App -> cm_hal


What am i doing wrong???
 
Hi all
Just read though this post but has the tut been updated with any tweeks...
got my 232 cable and my new 255 and going to give it a bash fingers crossed
just read the tut but confused with this part
type mac_address 2 (followed by your good mac ie aa:bb:cc:dd:ee:ff +1) (enter)
is the +1 for the usb mac as I have a 255 do I need to type it

It goes like this:

MAC = 00:00:00:00:00:01 <--- obviously this needs to be a working MAC ;)
USB MAC - 00:00:00:00:00:02 <--- +1 from your working MAC

:)
 
It goes like this:
MAC = 00:00:00:00:00:01 <--- obviously this needs to be a working MAC ;)
USB MAC - 00:00:00:00:00:02 <--- +1 from your working MAC
:)

heres a trivial one then lol

if nic mac is .... 00:00:00:00:00:FF

does USB one become... 00:00:00:00:01:00

?
 
i keep getting console is disabled by vender im pressing p in 2 seconds????
 
its reading it after its finished then it tells me console is disabled by vender
 
Someone's been reading my other posts ;) lol
I believe thats right as FF would be the highest?
:)

yeh mate FF is max for a single byte, the next hex value would be 100

thats see how many are confused now lol
 
like i said, it'll be the connections on the lead. mine did the same as th connector on mine is dodgy and sometimes comes out, when it comes out i get the disabled by vendor, i put the lead back on properly with the dodgy lead back in place and it works. just because it reads it doesnt mean its connected properly, im telling you this from my experience of the disable by vendor problem and whenever i get it i know to check my lead, and its always that my lead istnt connected properly.

also you are powering it up after you input the settings in hyper? that sometimes gives the disabled error aswell.
 
Last edited by a moderator:
I had problems with this as well. I made sure the cables where connected correct, and also, restart hyperterminal as well, as it didnt work for me, and i was going crazy trying to get it to work hehe, i was making sure Hyperterminal was on top, still didnt work, so i restarted hyperterminal , and it worked straight away
 
Back
Top